NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
PaulD48
Jan 02, 2017Tutor
FVS318Gv2 Fails after 15-30 minutes following a power failure/reboot
Following a power failure or power down/power up reboot, the unit will operate for anywhere from 15 -30 minutes and then go down:
When it fails, it will respond to a ping, but shows that WAN addresses are unreachable. Access to the unit is also down when this occurs. I cannot access it via the web interface, or via telnet. It simply will not respond.
I found the "GUI reboot" fix on this forum, and used the .reboot command from the telnet CLI. Since the unit rebooted in this fashion, service has remained up for nearly an hour now.
The unit is running Firmware Level 4.3.4-2 (Most current release).
From reading in this forum, it is clear that this issue has been causing nightmares for some time.
Is there/has there been any work from Netgear to resolve this issue?
It is clearly repeatable (at least from my perspective.)
Here are more details that may help:
ISP: Comcast
Modem: Motorola Surfboard SB6121
When firewall is "down", I can connect a PC to the modem and access the internet
Firewall: FVS318Gv2
Firmware: 4.3.4-2
Broadband settings: DHCP from ISP, Interface Speed: Auto, runnning at 1GB up and down.
It's getting to the point where I will begin looking for another Mfr than Netgear. Maybe it's just this model, but a well documented problem like this that has not been addressed is eroding my faith in an otherwise solid company.
5 Replies
- PaulD48Tutor
No - When it fails, it will respond to a ping, but shows that WAN addresses are unreachable. Access to the unit is also down when this occurs. I cannot access it via the web interface, or via telnet. It simply will not respond.
The only system logs available after rebooting are releated to the reboot itself - I tried copying the log into the post, bu I am limited to 20,000 characters.
- PaulD48Tutor
Yes - I have had this issue since I purchased this firewall.
I upgraded the firmware in the hopes that doing so would fix the problem
As part of the upgrade, I did do a factory reset to the device.
Related Content
NETGEAR Academy

Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!