NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Solved
Feedback for R7000 New firmware 1.0.9.18
Hi All,
Please post here for any update/issue related to the latest firmware 1.0.9.18.
You should review this and maybe revert back to this recommended version of FW:
Alfikwrote:I've looked here again after a while and I can't belive the problem is still not solved....
Since I've flashed Tomato a few weeks ago I've forgotten that I have a router- it's working perfectly getting dust because i do not touch it at all :-)...
Parental control works perfectly, 0 drops, strong signal - save your time and do a similar thing!
Well less than 1 hour with firmware R7000-V1.0.9.20_1.2.28 and down from 28 devices attached to 15. Turned off 5 ghz and guest again to see if that stabilizes it like the prior release(s)
aabshire wrote:Well less than 1 hour with firmware R7000-V1.0.9.20_1.2.28 and down from 28 devices attached to 15. Turned off 5 ghz and guest again to see if that stabilizes it like the prior release(s)
Same here - Nest stopped communicating as did my network wifi printer. Switched off 5ghz and rebooted and everything is back again. So V1.0.9.20 isn't the solution.
- Please tell me if you still are able to ping the devices. Do they still reply on a ping? In my case I always get a reply. No communication possible but I still reply on a ping.
It had it occur again after I had turned of the 5ghz radio, noticed I have the SSID broadcast still checked for 5 ghz & guest. Turned that off and so far so good. Strange
Had the "No Internet" pop up on my laptop and my android loss connection. @ around 16:46 or so. Checked the log and found this: (looks like DHCP refresh).
[DHCP IP: (192.168.0.107)] to MAC address 88:DE:A9:10:A2:BD, Saturday, Dec 23,2017 16:48:05
[DHCP IP: (192.168.0.109)] to MAC address 08:05:81:3C:C6:A5, Saturday, Dec 23,2017 16:48:04
[DHCP IP: (192.168.0.152)] to MAC address 48:D6:D5:F3:90:02, Saturday, Dec 23,2017 16:48:00
[DHCP IP: (192.168.0.105)] to MAC address 10:F1:F2:81:FF:A6, Saturday, Dec 23,2017 16:47:59
[DoS attack: FIN Scan] attack packets in last 20 sec from ip [159.127.42.140], Saturday, Dec 23,2017 16:46:06
[DoS attack: ACK Scan] attack packets in last 20 sec from ip [159.127.42.140], Saturday, Dec 23,2017 16:45:58
[DoS attack: FIN Scan] attack packets in last 20 sec from ip [205.180.87.140], Saturday, Dec 23,2017 16:45:46
[DoS attack: ACK Scan] attack packets in last 20 sec from ip [205.180.87.140], Saturday, Dec 23,2017 16:45:37I just logged on to my router to see how many devices I have connected. I last rebooted 2 hours ago. My 2.4GHz devices have dropped off again.
When I try to ping one of the devices, I get "Destination host unreachable" rather than "Request timed out". I don't recall if that's the message you get when you try to ping something on the same subnet or not, but I don't recall seeing it before. Maybe the ARP table is getting corrupted? Is there a way to SSH in to the routers to see the table? It doesn't appear to be listening on port 22.
I don't see anything in the logs that stands out. I've clear my logs and am going to reboot the router again. I'm going to keep a continuous ping going to one of my 2.4GHz devices so I can hopefully catch when it drops.
Very frustrating. I hate to buy another router, but I can't keep losing my devices. If I have to buy another one, I can't see me getting another Netgear.