R190,R201,R195 Routers have to reboot often

Our customers are having the same issues. We run 4.6 mostly on the routers. I’ve definitely noticed more issues with the R195s.

The current release is 4.6-R16. My customers and I can’t afford to test a beta. Would you care to note the cause of the issue and what was changed to fix this?

I am also having this issue with the R195W routers. Any idea when the new firmware will be out of bata?

We fixed an important memory leak, and also updated the radio driver with some important fixes. Apart from this this firmware is fully tested and subjected to long duration stress testing. I would request you to load your router with 4.7.1-B3.

ashutosh

As per current plan it should be a 30 days beta. The release candidate is already under test.

thanks
ashutosh

In a effort to resolve some of the issues we’ve had with these routers I have followed instructions from this Thread Based on the first post of the thread. After updating to 4.7.1-B3 should we undo the suggested changes or retain them.
It would also be very helpful if Cambium would post a recommended configuration either in blog form or by sharing a config file. I would also like to see your response with your opinion of those suggested changes by iBound on the mentioned thread.

Hi Gary,
I would suggest that you factory reset the unit after upgrading to 4.7.1-B3 and then configure it as per your needs. It is hard for us to provide a golden configuration that would suite all customers. The default configuration is the best as a general case. The configurations mentioned in the thread, would apply to specific deployment scenarios, so it may help in certain cases only.

For example green field configuration would be helpful in case customer had issues with legacy b/g clients and would have no impact for others.

Apply configuration that you really need.

@ashutoshdatta, I see 4.7-R10 posted in maestro software, can this be loaded to router via Maestro?

I think that is only for R195P

So this beta firmware discussed above is for the r195w, R201P along the others?

No, the Beta is 4.7.1-B3 not 4.7-R10

Hi,

4.7-R10 Is for r195P only
4.7.1-B3 Is BETA release for r190/r200/r201/r195W only (this is not available in cnMaestro and needs to be upgraded from device UI)

@Gary_Boyce I’ve loaded 4.7.1-B3 and have started enabling the features disabled before and will update here.

@ashutoshdatta thanks for letting us know about this.

Especially do not modify the HWNAT/SWNAT configurations, you can still tune the radio config as per your local needs, like the 20MHz channel bandwidth may help in 2.4GHz at times etc. Factory resetting the unit after upgrade to 4.7.1-B3 will bring the NAT config to the desired state.

ashutosh

Hi Gary/iBound ,

Were you able to upgrade to 4.7.1-B3 and did you find improvement in your scenarios ?

thanks
ashutosh

YES! I have had several (maybe 10) routers upgraded since the 14th. I haven’t had any trouble with those routers since. Some of those customers were also complaining about their wifi printers disconnecting often. Since the update to 4.7 they haven’t had anymore trouble with their printers either. I will be rolling out the new firmware to all in the next week or so. Thank you guys!

Hi Gary,

The official release version 4.7.1-R4 is now available on support site and in cnMaestro for you.

thanks
ashutosh

there is always the option to use the scheduler to reboot every night at like 3am, not ever a good solution but works in a pinch

We enable a weekly reboot on sundays at 10am by assigning the unit to an AP Group (template) in cnmaestro and then use the default overrides to configure the device. The reboot day and time is configurable by our helpdesk as a variable field but we mandate it must happen weekly.

Hello All,

Since installing 4.7.2-R10, our large population of R195W residential routers are no longer randomly losing remote access, but have been getting reports of the routers not passing traffic until being rebooted. Devices can connect to the local SSID but report no internet, power cycling the router resolves the issue temporarily.

Is everyone still just going with scheduled reboots on their routers?

Is there anything new in development from a firmware standpoint?