NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Solved
N450/CG3000Dv2 WiFi drop and Interface Lockup
Last week Time Warner Cable pushed firmware V3.01.06 to my N450 modem/router. Since the update, i can't go more than 24 hours without having to pull the power because WiFi drops ALL devices. After ...
I did a factory reset and have not been loosing connection for a few days. In the genie menu there is a place to backup your settings. After the reset you can restore the settings from the file you saved. The only thing it didn't restore was the user and password to access the router. The default is admin for user and password for password. Then you can sign in and change that. Still can't usb port to work.
I know... Charging $159 to fix a problem with a $70 router is just insane.
Sounds like the same problem I've been having, only more severe. I posted about it here:
My connection is still usable and my WiFi still works, but takes several tries to log in to the web interface at 192.168.0.1, and every 15 to 20 seconds, I see a lag spike in which pings take 2000ms or more. I see it in the ping times on the LAN, no need to ping a site on the Internet. And I see all ping times get longer as the hours pass. Starts at 3ms after a fresh reboot, then decays to 16ms after 6 hours, 22ms after 12 hours, and 30ms after 24 hours of operation. Been going on for 2 to 3 weeks now. Interestingly, the diagnostics page, when I ping in the other direction from 192.168.0.1 to my PC, reports better ping times, but still not as good as they should be. This sure smells like a bug in the firmware, and I wanted to find out when it was last updated. My N450 is currently running 3.01.06.
I would revert to a previous version of the firmware if I could, but seems the N450 is programmed not to provide any means for the owner to do so. So far, I have not found any info on exactly when the firmware was last updated. That is totally unacceptable, Netgear. And charging us money, big money, for tech support? We're trying to help you guys figure out a problem you created. If anything, you should pay us!
I can work around the problem for now by rebooting the router every few hours, using the reboot button in Advanced Home in the web interface. Or if unable to log in, I can just power cycle the device. Takes me offline for half a minute, but restores ping times and performance to acceptable levels, for a few hours.
Here's the latest sample, pinging on a wire, after letting it stay up for 24 hours:
64 bytes from 192.168.0.1: icmp_seq=3 ttl=64 time=1021 ms
64 bytes from 192.168.0.1: icmp_seq=4 ttl=64 time=388 ms
64 bytes from 192.168.0.1: icmp_seq=5 ttl=64 time=237 ms
64 bytes from 192.168.0.1: icmp_seq=6 ttl=64 time=76.1 ms
64 bytes from 192.168.0.1: icmp_seq=7 ttl=64 time=35.5 ms
64 bytes from 192.168.0.1: icmp_seq=8 ttl=64 time=31.7 ms
64 bytes from 192.168.0.1: icmp_seq=9 ttl=64 time=378 ms
64 bytes from 192.168.0.1: icmp_seq=10 ttl=64 time=31.4 ms
64 bytes from 192.168.0.1: icmp_seq=11 ttl=64 time=227 ms
64 bytes from 192.168.0.1: icmp_seq=12 ttl=64 time=33.7 ms
64 bytes from 192.168.0.1: icmp_seq=13 ttl=64 time=387 ms
64 bytes from 192.168.0.1: icmp_seq=14 ttl=64 time=30.9 ms
64 bytes from 192.168.0.1: icmp_seq=15 ttl=64 time=31.4 ms
64 bytes from 192.168.0.1: icmp_seq=16 ttl=64 time=33.5 ms
64 bytes from 192.168.0.1: icmp_seq=17 ttl=64 time=71.5 ms
64 bytes from 192.168.0.1: icmp_seq=18 ttl=64 time=33.9 ms
64 bytes from 192.168.0.1: icmp_seq=19 ttl=64 time=5193 ms
64 bytes from 192.168.0.1: icmp_seq=20 ttl=64 time=4191 ms
64 bytes from 192.168.0.1: icmp_seq=21 ttl=64 time=3190 ms
64 bytes from 192.168.0.1: icmp_seq=22 ttl=64 time=2183 ms
64 bytes from 192.168.0.1: icmp_seq=23 ttl=64 time=1182 ms
64 bytes from 192.168.0.1: icmp_seq=24 ttl=64 time=183 ms
64 bytes from 192.168.0.1: icmp_seq=25 ttl=64 time=477 ms
64 bytes from 192.168.0.1: icmp_seq=26 ttl=64 time=131 ms
64 bytes from 192.168.0.1: icmp_seq=27 ttl=64 time=188 ms
64 bytes from 192.168.0.1: icmp_seq=28 ttl=64 time=33.1 ms
64 bytes from 192.168.0.1: icmp_seq=29 ttl=64 time=439 ms
64 bytes from 192.168.0.1: icmp_seq=30 ttl=64 time=99.7 ms
64 bytes from 192.168.0.1: icmp_seq=31 ttl=64 time=482 ms
64 bytes from 192.168.0.1: icmp_seq=32 ttl=64 time=31.6 ms
64 bytes from 192.168.0.1: icmp_seq=33 ttl=64 time=372 ms
64 bytes from 192.168.0.1: icmp_seq=34 ttl=64 time=31.7 ms
64 bytes from 192.168.0.1: icmp_seq=35 ttl=64 time=187 ms
64 bytes from 192.168.0.1: icmp_seq=36 ttl=64 time=62.5 ms
64 bytes from 192.168.0.1: icmp_seq=37 ttl=64 time=237 ms
64 bytes from 192.168.0.1: icmp_seq=38 ttl=64 time=81.8 ms
64 bytes from 192.168.0.1: icmp_seq=39 ttl=64 time=5344 ms
64 bytes from 192.168.0.1: icmp_seq=40 ttl=64 time=4648 ms
64 bytes from 192.168.0.1: icmp_seq=41 ttl=64 time=3655 ms
64 bytes from 192.168.0.1: icmp_seq=42 ttl=64 time=2665 ms
64 bytes from 192.168.0.1: icmp_seq=43 ttl=64 time=2043 ms
64 bytes from 192.168.0.1: icmp_seq=44 ttl=64 time=1051 ms
64 bytes from 192.168.0.1: icmp_seq=45 ttl=64 time=58.7 ms
64 bytes from 192.168.0.1: icmp_seq=46 ttl=64 time=243 ms
64 bytes from 192.168.0.1: icmp_seq=47 ttl=64 time=225 ms
64 bytes from 192.168.0.1: icmp_seq=48 ttl=64 time=30.9 ms
64 bytes from 192.168.0.1: icmp_seq=49 ttl=64 time=259 ms
64 bytes from 192.168.0.1: icmp_seq=50 ttl=64 time=43.4 ms
64 bytes from 192.168.0.1: icmp_seq=51 ttl=64 time=49.5 ms
64 bytes from 192.168.0.1: icmp_seq=52 ttl=64 time=38.9 ms
64 bytes from 192.168.0.1: icmp_seq=53 ttl=64 time=32.4 ms
64 bytes from 192.168.0.1: icmp_seq=54 ttl=64 time=46.7 ms
64 bytes from 192.168.0.1: icmp_seq=55 ttl=64 time=251 ms
64 bytes from 192.168.0.1: icmp_seq=56 ttl=64 time=33.6 ms
64 bytes from 192.168.0.1: icmp_seq=57 ttl=64 time=248 ms
64 bytes from 192.168.0.1: icmp_seq=58 ttl=64 time=31.9 ms
64 bytes from 192.168.0.1: icmp_seq=59 ttl=64 time=30.8 ms
64 bytes from 192.168.0.1: icmp_seq=60 ttl=64 time=5251 ms
64 bytes from 192.168.0.1: icmp_seq=61 ttl=64 time=4250 ms
64 bytes from 192.168.0.1: icmp_seq=62 ttl=64 time=3249 ms
64 bytes from 192.168.0.1: icmp_seq=63 ttl=64 time=2248 ms
64 bytes from 192.168.0.1: icmp_seq=64 ttl=64 time=1247 ms
64 bytes from 192.168.0.1: icmp_seq=65 ttl=64 time=246 ms
64 bytes from 192.168.0.1: icmp_seq=66 ttl=64 time=255 ms
64 bytes from 192.168.0.1: icmp_seq=67 ttl=64 time=154 ms
64 bytes from 192.168.0.1: icmp_seq=68 ttl=64 time=39.0 ms
64 bytes from 192.168.0.1: icmp_seq=69 ttl=64 time=97.3 ms
64 bytes from 192.168.0.1: icmp_seq=70 ttl=64 time=33.6 ms
64 bytes from 192.168.0.1: icmp_seq=71 ttl=64 time=72.9 ms
64 bytes from 192.168.0.1: icmp_seq=72 ttl=64 time=31.4 ms
64 bytes from 192.168.0.1: icmp_seq=73 ttl=64 time=149 ms
64 bytes from 192.168.0.1: icmp_seq=74 ttl=64 time=31.5 ms
64 bytes from 192.168.0.1: icmp_seq=75 ttl=64 time=50.8 ms
64 bytes from 192.168.0.1: icmp_seq=76 ttl=64 time=47.0 ms
64 bytes from 192.168.0.1: icmp_seq=77 ttl=64 time=205 ms
64 bytes from 192.168.0.1: icmp_seq=78 ttl=64 time=36.9 ms
64 bytes from 192.168.0.1: icmp_seq=79 ttl=64 time=93.2 ms
64 bytes from 192.168.0.1: icmp_seq=80 ttl=64 time=5740 ms
64 bytes from 192.168.0.1: icmp_seq=81 ttl=64 time=4740 ms
64 bytes from 192.168.0.1: icmp_seq=82 ttl=64 time=3741 ms
64 bytes from 192.168.0.1: icmp_seq=83 ttl=64 time=2745 ms
64 bytes from 192.168.0.1: icmp_seq=84 ttl=64 time=1744 ms
64 bytes from 192.168.0.1: icmp_seq=85 ttl=64 time=744 ms
64 bytes from 192.168.0.1: icmp_seq=86 ttl=64 time=679 ms
64 bytes from 192.168.0.1: icmp_seq=87 ttl=64 time=402 ms
^C
--- 192.168.0.1 ping statistics ---
87 packets transmitted, 85 received, 2% packet loss, time 86225ms
rtt min/avg/max/mdev = 30.845/957.651/5740.519/1556.881 ms, pipe 6
Pinging 192.168.0.4 with 64 of data:[In progress]
Reply from 192.168.0.4: bytes = 64, time = 35 ms
Reply from 192.168.0.4: bytes = 64, time = 9 ms
Reply from 192.168.0.4: bytes = 64, time = 32 ms
Reply from 192.168.0.4: bytes = 64, time = 133 ms
Reply from 192.168.0.4: bytes = 64, time = 35 ms
Reply from 192.168.0.4: bytes = 64, time = 32 ms
Reply from 192.168.0.4: bytes = 64, time = 9 ms
Reply from 192.168.0.4: bytes = 64, time = 32 ms
Reply from 192.168.0.4: bytes = 64, time = 32 ms
Reply from 192.168.0.4: bytes = 64, time = 11 ms
Reply from 192.168.0.4: bytes = 64, time = 34 ms
Reply from 192.168.0.4: bytes = 64, time = 46 ms
Reply from 192.168.0.4: bytes = 64, time = 21 ms
Reply from 192.168.0.4: bytes = 64, time = 9 ms
Finished 60 pings from the diagnosic page. Notice that the conclusion says 0/60 replies received. Yep, buggy firmware.
Pinging 192.168.0.4 with 64 of data:[Complete]
Reply from 192.168.0.4: bytes = 64, time = 35 ms
Reply from 192.168.0.4: bytes = 64, time = 9 ms
Reply from 192.168.0.4: bytes = 64, time = 32 ms
Reply from 192.168.0.4: bytes = 64, time = 133 ms
Reply from 192.168.0.4: bytes = 64, time = 35 ms
Reply from 192.168.0.4: bytes = 64, time = 32 ms
Reply from 192.168.0.4: bytes = 64, time = 9 ms
Reply from 192.168.0.4: bytes = 64, time = 32 ms
Reply from 192.168.0.4: bytes = 64, time = 32 ms
Reply from 192.168.0.4: bytes = 64, time = 11 ms
Reply from 192.168.0.4: bytes = 64, time = 34 ms
Reply from 192.168.0.4: bytes = 64, time = 46 ms
Reply from 192.168.0.4: bytes = 64, time = 21 ms
Reply from 192.168.0.4: bytes = 64, time = 9 ms
Reply from 192.168.0.4: bytes = 64, time = 7 ms
Reply from 192.168.0.4: bytes = 64, time = 1 ms
Reply from 192.168.0.4: bytes = 64, time = 1 ms
Reply from 192.168.0.4: bytes = 64, time = 18 ms
Reply from 192.168.0.4: bytes = 64, time = 2 ms
Reply from 192.168.0.4: bytes = 64, time = 2 ms
Reply from 192.168.0.4: bytes = 64, time = 2 ms
Reply from 192.168.0.4: bytes = 64, time = 2 ms
Reply from 192.168.0.4: bytes = 64, time = 259 ms
Reply from 192.168.0.4: bytes = 64, time <1 ms
Reply from 192.168.0.4: bytes = 64, time = 2 ms
Reply from 192.168.0.4: bytes = 64, time = 33 ms
Reply from 192.168.0.4: bytes = 64, time = 12 ms
Reply from 192.168.0.4: bytes = 64, time = 10 ms
Reply from 192.168.0.4: bytes = 64, time = 10 ms
Reply from 192.168.0.4: bytes = 64, time = 28 ms
Reply from 192.168.0.4: bytes = 64, time = 12 ms
Reply from 192.168.0.4: bytes = 64, time = 9 ms
Reply from 192.168.0.4: bytes = 64, time = 24 ms
Reply from 192.168.0.4: bytes = 64, time = 24 ms
Reply from 192.168.0.4: bytes = 64, time = 25 ms
Reply from 192.168.0.4: bytes = 64, time = 24 ms
Reply from 192.168.0.4: bytes = 64, time = 8 ms
Reply from 192.168.0.4: bytes = 64, time = 45 ms
Reply from 192.168.0.4: bytes = 64, time = 42 ms
Reply from 192.168.0.4: bytes = 64, time = 34 ms
Reply from 192.168.0.4: bytes = 64, time = 32 ms
Reply from 192.168.0.4: bytes = 64, time = 17 ms
Reply from 192.168.0.4: bytes = 64, time = 32 ms
Reply from 192.168.0.4: bytes = 64, time = 78 ms
Reply from 192.168.0.4: bytes = 64, time = 65 ms
Reply from 192.168.0.4: bytes = 64, time = 17 ms
Reply from 192.168.0.4: bytes = 64, time = 18 ms
Reply from 192.168.0.4: bytes = 64, time = 17 ms
Reply from 192.168.0.4: bytes = 64, time = 19 ms
Reply from 192.168.0.4: bytes = 64, time = 34 ms
Reply from 192.168.0.4: bytes = 64, time = 33 ms
Reply from 192.168.0.4: bytes = 64, time = 415 ms
Reply from 192.168.0.4: bytes = 64, time = 32 ms
Reply from 192.168.0.4: bytes = 64, time = 17 ms
Reply from 192.168.0.4: bytes = 64, time = 17 ms
Reply from 192.168.0.4: bytes = 64, time = 32 ms
Reply from 192.168.0.4: bytes = 64, time = 2 ms
Reply from 192.168.0.4: bytes = 64, time = 17 ms
Reply from 192.168.0.4: bytes = 64, time = 3 ms
Reply from 192.168.0.4: bytes = 64, time = 19 ms
0/60 replies received.
min time=0 ms, max time=0 ms, avg time=N/A ms