NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Solved
FVS336GV2 Upgrade from -V4.3.1-18 to v4.3.3-6 connection disconects
Recently Upgraded from V4.3.1-18 to V4.3.3-6. Since upgrade, all rules were wiped when reset, so no rules/services are set. DHCP is working properly. Logs show many Sun Oct 1 07:17:11 2...
Hi Jahare,
Welcome to the community! :)
Let us isolate the problem. Kindly try the steps below:
1. Disconnect the FVS336Gv2 from your existing network. Then, connect a PC directly to your modem. Observe if the internet connection is just fine.
2. If ever the internet connection is just fine when a PC is directly connected to the modem. Kindly connect the modem back to the WAN port of your FVS336Gv2 then try this: on the web-GUI of the FVS336Gv2, go to Security > Firewall > Attack Checks. Then, uncheck the boxes on "Block TCP Flood" and "Block UDP Flood." Then, observe if the same problem occurs. Refer to the image below as reference:
3. Did you perform a factory reset on the FVS336Gv2 after upgrading the firmware from v4.3.1-18 to v4.3.3-6? If not yet, I suggest you to perform a factory reset on the FVS336Gv2 then reconfigure it from scratch in order to start clean using the latest firmware version. Then, observe if same problem occurs.
Regards,
DaneA
NETGEAR Community Team
Hi DaneA,
Thanks for the welcome, Here are some updates.
1) Disconnected from the firewall, Connected a PC directly to cable modem, no issues, no disconnects.
2) Unchecked both the "Block TCP Flood" and "Block UDP Flood" , so far no disconnect/connection resets. Will monitor through the day today and post an update tonight if that is consistant.
3) After I did the firmware, a factory reset was performed, but can try that again if the above #2 does not resolve.
Will keep you posted tonight, or when/if it disconnects today.
Thanks again for the help!
Seems the issue is now resolved.
Re-enabled Block TCP Flood, tested for about an hour no issues.
Re-enabled the Block UDP flood, issue returned.
Changed the UDP flood to 400 instead of 40 connections, and seems fine and stable now.
I assume DNS requests are seen as a UDP request from internal LAN?
Thanks for the awesome assist!
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
