NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
atiktepika
Jul 04, 2012Aspirant
fvs318n - Internet working only for wifi users
Hi there, Afters some attempts trying to get everything to work with my new fvs318n vpn firewall I do find a very odd internet access problem. For some reason my wireless devices do not have any...
tropic
Aug 04, 2012Aspirant
I've found that restoring config files on Netgear's ProSafe line of firewalls can be problematic, but restoring the config from a recent firmware to an older one often creates problems no matter the vendor. It isn't a bad idea to set to factory defaults and enter your configuration manually.
I have a pretty simple setup (3 VLANs, 2 WAPs, 12 DHCP reservations), and I can get everything working initially with any of the FVS318N firmwares... but a power cycle can kill it. Firewall rules connected to groups stop working correctly, UPnP dies, etc. Like you mentioned, taking an entire minute to enter a single DHCP reservation is really frustrating when troubleshooting.
For me the intermittent DNS issues seem to stem from this: if the firewall itself queries the external name server (DNS proxy checked), there's no problem, whereas a DNS query from a LAN device to an external server never makes the round trip. Even when the firewall is acting up, you can still ping external devices by name or ip address from the firewall's Diagnostic screen. So perhaps you're right when you say the unit's internal firewall logic is screwed. I've been able to avoid some bugginess by not using the Default VLAN... but it's a shame that you cannot delete it completely and free VLAN ID #1 for use with a fresh profile.
Anyway, I've settled on firmware 4.0.1-67 until Netgear provides a decent upgrade. It has its own quirks, but it doesn't fold under heavy BitTorrent use like more recent firmwares.
I have a pretty simple setup (3 VLANs, 2 WAPs, 12 DHCP reservations), and I can get everything working initially with any of the FVS318N firmwares... but a power cycle can kill it. Firewall rules connected to groups stop working correctly, UPnP dies, etc. Like you mentioned, taking an entire minute to enter a single DHCP reservation is really frustrating when troubleshooting.
For me the intermittent DNS issues seem to stem from this: if the firewall itself queries the external name server (DNS proxy checked), there's no problem, whereas a DNS query from a LAN device to an external server never makes the round trip. Even when the firewall is acting up, you can still ping external devices by name or ip address from the firewall's Diagnostic screen. So perhaps you're right when you say the unit's internal firewall logic is screwed. I've been able to avoid some bugginess by not using the Default VLAN... but it's a shame that you cannot delete it completely and free VLAN ID #1 for use with a fresh profile.
Anyway, I've settled on firmware 4.0.1-67 until Netgear provides a decent upgrade. It has its own quirks, but it doesn't fold under heavy BitTorrent use like more recent firmwares.
Related Content
NETGEAR Academy

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