RV260W Wifi stops working after some time

[GeraldHolmann6117]

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?

[00u1m0vahcc3Ryn265d7]

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 !

[jtoddv]

You are welcome. I am a bourbon fan.  You can never find Weller or Pappy in Tennessee.   

[Exequiel Santander]

El problema persiste, no?

[uspenna]

Yes.

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?

[JakobSkovgaard73791]

I have tried to disable 5Ghz, put all my wireless devices in the static
DHCP but same result.

[jtoddv]

I was able to resolve my issue finally. After the update to 1.0.00.17, I thought certainly it would resolve the issue. However, it made the issues worse. Instead of having to reboot the router every two or three days, it became a daily recurrence. This is what I did and I have had zero issues in two weeks. I changed the 2.4GHz radio to N-Only. I changed the 5GHz radio to A/N/AC-Mixed. When I did this in the dashboard, all 12 devices reconnected to the wireless without even having to reboot the router. Cisco really should work to resolve this issue with the radios. Please let me know if this works.

[JakobSkovgaard73791]

Thanx I will try that. What did you set the Channel Bandwidth to (on both
radios)?

[jtoddv]

20/40 MHz on 2.4 and 80 MHz on 5. I believe these are the default channel bandwidth.

[JakobSkovgaard73791]

Thank you for your answer. Unfortunately it didn't work for me. I still
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...

[JakobSkovgaard73791]

Hi,
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 :-(

[kelmanse]

I have RV160W (1.0.00.17) and I have the same issue but not only with WIFI.
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 ^^^ ?

[as2020]

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

[kelmanse]

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).

[as2020]

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

[acalv61367]

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.