NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Rules
3 Topicsfvs336gv3 inbound rules not working
I have an fvs336gv3, firmware 4.3.5-3. I have defined 9 inbound lan-wan rules similar to the following: Service Name Filter LAN Server IP Address LAN Users WAN Users QOS Profile Destination Bandwidth Profile Log ssh-tcp-207 ALLOW always 192.168.2.207 Any NONE WAN1 NONE Always These rules worked fine until recently, then abruptly stopped allowing any through traffic. I updated the firmware to 4.3.5-3 in hopes that would fix the problem, but there has been no change. All inbound traffic is still blocked. Everything I have tried (rules disable-enable, power cycling, rebooting) to correct this problem has had no successful results. Does anyone have any ideas or specific knowledge that I might try to correct this problem? Thanks in advance. 4.3.5-3Solved5.3KViews0likes4CommentsPreventing circumvention of OpenDNS with firewall rules
Hi, I am attempting to set up my FVS318Gv2 Firewall so it will block all DNS queries that are not from OpenDNS. I was using this article for reference. To do this, I created a list of outbound rules. The first two I have block all DNS for UDP and TCP. The next four allow DNS on OpenDNS IPs. According to the manual, this is the correct order "you should place the most strict rules at the top" My hope was that the allow rules would override the block rules. According to OpenDNS's Documentation: "The first rule trumps the second rule, so anything requests to OpenDNS are allowed but any DNS requests to any other IP are blocked." I've tried adding these in the reverse order and using port 53 instead of the built in services but whatever I try blocks all DNS requests. Am I adding these rules wrong? What else could I try? Here is a screenshot of my configuration (The block rules are disabled so people can use the internet, but were enabled for my setup) Thank you! -JoelSolved5.3KViews0likes5CommentsSRX 5308 - Protocol binding does not work
I have two WANs up and running and selected NAT and Load balancing with weighted LB. I defined a protocol binding for FTP for WAN2 but it routes through WAN1? The default outbound policy is "block always" and i only have one policy that allows all trafic and NAT IP is set to AUTO. Why is it not working? The only way to get outgoing traffic for specific service to specific WAN port is to define an outbound policy for each and define NAT IP accordingly, for example WAN2. If I understand correct the protocol binding should work without any outbound policies? Firmware: 4.3.3-65.8KViews0likes5Comments