RV260W Wifi stops working after some time
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-22-2019 07:35 AM
We recently purchased a Cisco RV260W wifi router. We implemented and the router is working well, but:
After a few days of working, Wifi stops responding. We can still see the SSID on the network, but the router wifi first starts behaving flaky and then after a bit longer, stops working altogether.
We reboot and the router wifi starts working again.
We are now having to reboot about once a week.
Anyone else with this problem? Any solutions?
- Labels:
-
LAN Switching
-
Other Routing
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-29-2021 08:53 AM
Sir, if I knew who you were I would buy you a bottle of Pappy and a Wagyu Steak! Your solution nailed it! Totally fixed my issue. Thank you for taking the time to post ... CISCO OWES YOU !
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-07-2021 01:38 PM
You are welcome. I am a bourbon fan. You can never find Weller or Pappy in Tennessee.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-02-2023 12:03 PM
El problema persiste, no?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-03-2023 05:55 AM
However, since I've scheduled a daily reboot, the problem appears with less
frequency .. let's say, it appears once a month.
Should I stop the daily reboot?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-03-2020 11:41 PM
DHCP but same result.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-03-2020 06:22 PM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-03-2020 11:46 PM
radios)?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-06-2020 10:22 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-06-2020 10:44 AM
have the same instability.
I have tried to put all my wireless devices in static DHCP and that seems
to work much better... but not near perfect yet...
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-03-2020 11:40 PM
No that is not even enough. You need to either reboot or turn it off/on on
the back of the device.
I'm thinking of setting a Philips Hue plug in before the power to the
router to reboot automatically at night... but this is far out :-(
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-21-2020 08:19 AM
I have the same problem with wired network. It just stops working. Each 1-2 days.
Cable is connected but no DHCP and I can't even reach router by "admin" ip (192.168.1.1 by default).
Only reboot helps.
#cisco ^^^ ?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-28-2020 03:26 AM
I have the same problem Version FW 1.0.00.17, i have try to do all your consideration with disactivating wmm..&&&..but the issue still here. Can somebody look also to the logs-->Status Statistics-->View logs-->
notice>kernel: [ 2544.263171] RADIO 2.4G SSID xxxx 7c:89:xx:xx:xx:xx disconnected
2020-04-27T22:07:22+01:00 <notice>kernel: [ 2544.261839] RADIO 5G SSID xxxx 7c:89:xx:xx:xx:xx reconnected
Do you have the same messages? THX
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-28-2020 10:22 AM
Inserted USB flash to collect debug logs shows nothing.
...
2020-04-28T19:29:45+03:00 <notice>nas: Last message 'Driver DISASSOC Mess' repeated 1 times, supressed by syslog-ng on router5654B1
2020-04-28T19:29:45+03:00 <notice>nas: EAPOL key message from B4:18:D1:71:27:08
2020-04-28T19:34:45+03:00 <notice>nas: Last message 'EAPOL key message fr' repeated 1 times, supressed by syslog-ng on router5654B1 2020-04-28T19:42:46+03:00 <info>kernel: [ 82.465040] eth2: pfe_eth_open
2020-04-28T19:42:46+03:00 <info>kernel: [ 82.465734] hif_process_client_req: register client_id 1
2020-04-28T19:42:46+03:00 <info>kernel: [ 82.465747] pfe_hif_client_register
...
Router stopped work at 2020-04-28T19:40:XX
Start from 19:42 it's logs after reboot by pressing reset button.
Tested on 1.0.0.15 and 1.0.0.17 - same. DHCP stops work and I can't reach router admin Web UI. But I still can reach devices in my local network which has static IP (I mean one Windows 10 PC which does not use DHCP and has IP address manual configured like 192.168.1.2/255.255.255.0).
Also all already opened socket connections (in different software on Windows and Ubuntu) still can send and receive packages to/from "internet" (I mean remote devices over WAN).
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-30-2020 01:26 AM
THX for the answer, the error code of the logfile shoult cisco tell us to verify that. i will compare the logs when the next wifi stop appear. BR, as2020
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-24-2020 11:06 AM
I've noticed that instead of rebooting you can also toggle the WiFi button the back and it resolves the issue, the button must power down the WiFi chip so that it reboots.
Much quicker than rebooting the entire unit, as it's a total slow dog to start up.
100% disappointed with this purchase, if the problems had manifested soon enough I would have sent it back.
