ER7212PC does NOT block WAN traffic by default when NO-NAT is enabled on WAN port
Hi,
I was under the impression that the ER7212PC (like all routers) blocks inbound traffic on the WAN port by default, and that only ports opened via Port Forwarding would be accessible externally.
However, I recently discovered that my entire network was exposed to the public Internet, which led to numerous viruses, trojans, and eventually continuous DDoS attacks.
After investigating, I found that when my PC was connected to the same subnet as the ER7212PC’s WAN port, I could not only access the router’s management console but also reach all servers across all VLANs defined on the ER7212PC gateway/switch.
This was a serious and alarming discovery. I’m unsure if this is a bug in firmware version 1.3.1, or if it is by design behavior when NAT is disabled on the WAN port for all VLANs.
As a workaround, I created a firewall ACL rule to block all inbound traffic on the WAN interface and then added specific rules to allow only the necessary Port Forwarding traffic.
My question is:
• Is it really necessary to manually create a “deny all” ACL rule on the WAN when NAT is disabled?
• Shouldn’t the router automatically block inbound WAN traffic by default, even without NAT?
• Or is this a known bug in firmware 1.3.1?
Would appreciate any clarification or advice, and whether such behaviour is documented in ER7212PC manual or not
Thanks!