NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
New V4.6.3.16
Hi all, Installed yesterday the new beta firmware V4.6.3.16. Got some improvements in the wireless connections but totally broke my lan wired stability. I have been quiet and reading the feedback bu...
Similar issue on my RBR750 after the firmware upgrade to 4.6.3.16.
I can not make a comparison with previous firmwares, because I have this device for a very short time.
But I use the same configuration that I've been using for 2 years with an RBK20 without any problem.
Satellite connected by cable to the router.
the problem is that the devices connected via wireless to the satellite, lose connectivity for a few moments.
Does not happen to devices connected to the router, but only to those connected to the satellite.
I have obviously tried all the suggestions read in the community, such as turn off the modem, do the factory reset, reconfigure the system by connecting the satellites via wifi and only then connect them with the cable .... tried everything. the problem persists.
The router is in "Router Mode" (as I always had my old RBK20).
As I said before... I don't know if this problem appeared with the last firmware... but surely now the system is unusable.
64 bytes from 142.250.184.100: icmp_seq=452 ttl=114 time=19.749 ms 64 bytes from 142.250.184.100: icmp_seq=453 ttl=114 time=17.717 ms 64 bytes from 142.250.184.100: icmp_seq=454 ttl=114 time=20.004 ms 64 bytes from 142.250.184.100: icmp_seq=455 ttl=114 time=13.123 ms 64 bytes from 142.250.184.100: icmp_seq=456 ttl=114 time=19.693 ms 64 bytes from 142.250.184.100: icmp_seq=457 ttl=114 time=20.294 ms 64 bytes from 142.250.184.100: icmp_seq=458 ttl=114 time=17.920 ms 64 bytes from 142.250.184.100: icmp_seq=459 ttl=114 time=13.614 ms Request timeout for icmp_seq 460 ping: sendto: No route to host Request timeout for icmp_seq 461 ping: sendto: No route to host Request timeout for icmp_seq 462 ping: sendto: No route to host Request timeout for icmp_seq 463 ping: sendto: No route to host Request timeout for icmp_seq 464 ping: sendto: No route to host Request timeout for icmp_seq 465 Request timeout for icmp_seq 466 64 bytes from 142.250.184.100: icmp_seq=467 ttl=114 time=199.435 ms 64 bytes from 142.250.184.100: icmp_seq=468 ttl=114 time=125.238 ms 64 bytes from 142.250.184.100: icmp_seq=469 ttl=114 time=12.153 ms 64 bytes from 142.250.184.100: icmp_seq=470 ttl=114 time=45.545 ms 64 bytes from 142.250.184.100: icmp_seq=471 ttl=114 time=11.689 ms 64 bytes from 142.250.184.100: icmp_seq=472 ttl=114 time=144.667 ms 64 bytes from 142.250.184.100: icmp_seq=473 ttl=114 time=116.345 ms 64 bytes from 142.250.184.100: icmp_seq=474 ttl=114 time=153.378 ms 64 bytes from 142.250.184.100: icmp_seq=475 ttl=114 time=73.604 ms 64 bytes from 142.250.184.100: icmp_seq=476 ttl=114 time=19.745 ms 64 bytes from 142.250.184.100: icmp_seq=477 ttl=114 time=14.055 ms 64 bytes from 142.250.184.100: icmp_seq=478 ttl=114 time=11.431 ms 64 bytes from 142.250.184.100: icmp_seq=479 ttl=114 time=11.672 ms 64 bytes from 142.250.184.100: icmp_seq=480 ttl=114 time=30.086 ms
this is what happens during a ping to google.com.
Same if i ping the router directly
64 bytes from 192.168.1.1: icmp_seq=71 ttl=64 time=3.872 ms 64 bytes from 192.168.1.1: icmp_seq=72 ttl=64 time=3.673 ms 64 bytes from 192.168.1.1: icmp_seq=73 ttl=64 time=8.920 ms 64 bytes from 192.168.1.1: icmp_seq=74 ttl=64 time=11.616 ms ping: sendto: No route to host Request timeout for icmp_seq 75 ping: sendto: No route to host Request timeout for icmp_seq 76 ping: sendto: No route to host Request timeout for icmp_seq 77 ping: sendto: No route to host Request timeout for icmp_seq 78 ping: sendto: No route to host Request timeout for icmp_seq 79 ping: sendto: No route to host Request timeout for icmp_seq 80 Request timeout for icmp_seq 81 Request timeout for icmp_seq 82 64 bytes from 192.168.1.1: icmp_seq=83 ttl=64 time=39.530 ms 64 bytes from 192.168.1.1: icmp_seq=84 ttl=64 time=134.120 ms 64 bytes from 192.168.1.1: icmp_seq=85 ttl=64 time=92.442 ms 64 bytes from 192.168.1.1: icmp_seq=86 ttl=64 time=91.720 ms
At the moment I have downgraded to V3.2.18.1_1.4.14.I have blocked the urls for the update, (the only drawback is that in the Orbi app it shows me the device OFFLINE even though it is not). Now everything works without any instability.
I still have some time to decide whether to return RBK753, I'll wait if there are updates about working firmware, otherwise... bye bye Netgear. I can't risk keeping a device that can't be updated.