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?

[Georg Pauwen]

Good advice. A while back, another user experienced no problems anymore after changing the 2.4GHz radio to N-Only, and changing the 5GHz radio to A/N/AC-Mixed. You might want to give that a try as well...

[uspenna]

Hi Georg,
I can try that, but I saw another user, at the forum/list, saying the
procedure did not work for him ..
I think it worked because, when you change the wifi configuration, the
router has to reboot the wifi portion ..

[uspenna]

I understand you are just trying to help with some suggestions. Don't take
the below observations personally.
If the device has the features of 2.4 and 5 GHz, and it is in the manual
and configuration option that I can use both, so disabling one of them is
not a solution, at least not for me. Because 2.4GHz reaches a longer
distance than 5GHz, and 5GHz, for those devices closer to the router, are
faster than 2.4GHz.
Besides, *the wired devices are also suffering*. I can see it right now on
my PC. It is happening at this exact moment.
Thanks.

[uspenna]

I have the router model below:
Router model: RV260W-A-K9
Firmware version: 1.0.01.01 (it is the latest available for it)

I have to reboot/reinitialize my router every week because of a Wi-Fi issue with the RV260W model that was being discussed here.

The solution Cisco suggests is to rebot/reinitialize the router. Ok then.

I was thinking of using the SNMP (snmpset, from my Linux PC) to order/ask the router to reboot.

However I could not find which OID to use in order to get the router rebooted/initialized.

Besides, I found an article, in the forum, that tells me to run, this command *at the router* (for another model of router ..):
snmp-server system-shutdown
but RV260W has no console output and I have no way to set that command.

Then, at the snmp client side, you've should ran this command:
snmpset -v 2c -c my_community_name my.router.ip.address .1.3.6.1.4.1.9.2.9.9.0 i 2

which would mean:
iso.org.dod.internet.private.enterprises.cisco.local.lts.tsMsgSend.0
(.1.3.6.1.4.1.9.2.9.9.0)

to value 2 (integer), and the system will reload.

But there is no such OID in the RV260W. In fact, I could not identify any OID that should me led to a close thinking of reboot/reinitialize option ..

Any suggestions? Should I buy a timer lamp in order to reboot the router?
Thanks.

P.S.: I have installed the MIB and I'm able to run snmpset or snmpget/snmpwalk commands succesfully from my Linux PC.

[abigali]

You may try running the Internet Connection troubleshooter which can also helps you fix the problems with internet connection.

[uspenna]

Abigali, I have *no problem* with Internet connection.
The problem is with the Wi-Fi portion. Cisco knows the problem and the
solution pointed by them is to reboot the router .. or turn off and on the
Wi-Fi, when the problem occurs.
I'd like a way to reboot the router using SNMP. That's all.
Thanks anyway.

[abigali]

Hello Uspenna,
You can also check this, Reloading a Cisco router using SNMP - https://community.cisco.com/t5/network-management/reloading-a-cisco-router-using-snmp/td-p/1224717
Thanks & Regards...

[uspenna]

Hi, thanks for the link.

However I've already seen it and it did not worked .. but I've just posted
a message there with my doubts, maybe someone could help.

There is also this link:
https://community.cisco.com/t5/small-business-routers/snmp/td-p/4124843
(and I've posted the same message/doubts there)

Thanks again.

[Dmb21]

I had this problem as well.  After restarting a ton, I noticed it reverted the wifi name to ciscob.  I left it like that and haven't had a problem since.  Might have been something else, but worth a try if you're having consistent wifi issues.