fvs318n - Internet working only for wifi users

it was working few min. ago. system must went down. I would suggest to try alter.

The support website is functional again, and I was able to download firmware 4.2.0-14, thanks :)

My problem (DNS through the FVS318N impossible sometimes) did not reapper since the ugrade; but then again, it always was an intermittent effect, so I'll have to monitor this for a while.

The web interface of the FVS318N does not respond on https at the moment, I hope that goes away after a reboot or https works on VLAN 1.

Regards from sweating Austria, Christoph Lechleitner

Sometime interface may not work until the router is fully up. I would leave for few min after power cycle / hard reset etc.

I traced the web interface down to a certificate problem:
The self signed certificate used by the FVS318N resp. firmware 4.2.0-14 must contain some error.
Google Chrome (22.0.1229.8 dev) says: Fehler 2 (net::ERR_FAILED): Unknown Error
Firefox (14.0.1) says: sec_error_reused_issuer_and_serial
GnuTLS says: Fatal error: Error in the certificate
OpenSSL s_client is satisfied.
IE8 also calls the certificate invalid, but allows to use the interface anyway.

And, worst of all, my DNS problem is back :mad:

So, upgrading to 4.2.0-14 forces me to start a windows VM just to access the Webinterface :mad:, and I still cannot perform DNS queries reliably :(

iteg wrote:
Firefox (14.0.1) says: sec_error_reused_issuer_and_serial

I solved this by removing any netgear server ceritifcates in FF's list of known certificates.

I found out solution on DNS problem.

Just quite easy:
Problem is based on fact that when client directly use some external DNS servers, it query DNS servers by UDP protocol. Seems DNS flood protection prevents proper DNS system functioning. Software upgrade its not solution, at least for me it wasn't. I am running 4.2.0-14 release.

So go to:

1. Security/Attack Checks
2. Uncheck "Block UDP flood"

I have spent a lot of hours on this issue. Now its works perfectly and i am happy with my Netgear :)

Have a nice Netgear :)

Wow, this sounds quite reasonable, I'll try that here and report back in a couple days or so.

Thanks for hanging on and for sharing :)

So this thread is a little old already but since I had a similar issue and solved it, thought I'd post the info...

Downgrading the firmware was not necessary...and I doubt that's the issue anyway. However, one byproduct of changing firmware (in either direction) is that you reset everything. That said, if you saved settings and reloaded you might still have the original problem...the one I'm about to explain.

For me, I had played around a bit, checking all the settings, and found the Lan Groups. This gave a nice inventory of all devices on the system. I renamed several of the "unknowns" as I kept a nice list of devices and mac addresses in an Excel file. All nice.

Then I found the button at the bottom of that screen that said "Save Bindings". Of course, why not click that? Got a message that that too was successful. Then, I remembered an IP address I wanted to change and, being in maintenance mindset, I changed it.

Suddenly (well, not suddenly enough to realize the issue) I was having trouble accessing the Internet. It worked earlier. My wireless laptop was working fine; the wired desktop was not!?!

CUT TO THE ISSUE...when you save the binding, it associates the IP address with the mac address. Then, after changing an IP address of the "bound' computer, the firewall blocks access. (This is, actually, a good thing.) Note that bindings can be saved from the Lan Groups (Network Config->LAN Setup->LAN Groups) but are not editable from here...edit these setting at (Security->Asddress Filter->IP Mac Bindings). Once I found this (sorry, had to read the manual), I simply deleted all the bindings and INSTANTLY had Internet access on the desktop.

I hope this helps someone else. Love the device!
TJ

Hello,

Have the exact same problems as mentioned above.

I have also drilled it down to a UDP FW-block-issue - found this thread later, so I am quite sure.

I agree that the option : Security | Firewall | Attack Checks | Block UDP flood is the 'magic bullet'.

However, in my findings, disabling it does _not_ solve my problems, it just makes it 'better'.

Enabling it and setting it to max (999) makes it much, much better - but still not perfect.

My intuition on what I see is that.

Enabling it with default 50 - worst ever DNS/UDP experience.
Disabling it is better than enabling with 50 - bad DNS/UDP experience.
Enabling it with 999 - OK DNS/UDP experience, but it still drops once in a while.

So.... what the ... is going on. I believe they have a few lines of code which hardcodes the UDP flood to something like 200, even if it is disabled?

That would fit with my experience.

Hope this can help someone before they throw it out, I was close to :-)

FW = 4.3.0-19 - and I _have_ made a hard-reset + manual configuration.

Brgds.
Jugger

I had this problem a while back, using dnsmasq internally and traced it to the LAN ping flood protection as well. When DNS traffic gets over a certain level, the FVS318N decides it's a packet storm and just kills DNS lookup. Clients on LAN experienced this as a long timeout looking up websites, they would often kick over to looking up sites directly via external DNS servers but it could take many seconds. Unchecking the prevent storms options solved the problem,

Darren