Heads Up :
The post you are writing will appear in a public forum. Please ensure all content is appropriate for public consumption. Review the employee guidelines for the community here.
We have configured firewall rules to block "All Traffic (UDP and TCP)" from specific IP address ranges. These rules are not blocking incoming connections to ports 500 and 4500 for these address ranges. How do we block these ports when they should a...
We have also upgraded 6 of the RV-340’s directly from 1.0.03.22 to 1.0.03.27 without upgrade issue. The only problem we have seen with 1.0.03.27 is that there is a constant logging of attempts to reconnect site to site VPN connections when the connec...
We use a local DB for Service Auth Sequence (not RADIUS, LDAP nor ACTIVE DIRECTORY), and have local user accounts configured for remove VPN logins. We use external DNS servers for the router, so the router probably has a local DNS database in RAM, b...
I also have this problem on an RV340 set up for automatic update and install. No link of traffic across between the LAN ports and the connected WAN port after the 1.0.03.24 firmware update. Rolled back to 1.0.03.22 and the device was fine. Have no...
The example IP address shown is in a block of IP addresses from China which are attacking/probing our routers from the WAN side (hundreds of entries in the router logs probing various common listening ports). Yes, we have IPSEC configured (router as ...
How do I export or provide the rule base?If I set up this rule, and place it at priority 1, then how is any connection accepted from this IP rangeDENYAll connections (TCP and UDP) range 1-65535Source Interface: ANYSource - Range - 222.184.0.0 ~ 222.1...
