pfsense suddently blocks all inbound traffic and ping
-
I used to have a perfectly functioning pfSense on a Netgate hardware. Now I upgraded the hardware to a more powerful Netgate, and all inbound traffic is blocked. I cannot even ping from outside the LAN. Also VPN is suddenly down. However everything outbound is fine.
What might be going on?
I disabled all firewall rules with the following rule as the 1st, and it doesn't help.
The WAN is attached to a fiber router which NATs everything to 10.0.0.2. I didn't make any changes there. This is how things look like on the dashboard. Any ideas? Thanks in advance!
-
@aagaag Sounds like you have enabled the “Block Private networks” on your WAN Interface. Since your WAN connects to a private network NAT’ing modem, you would experience just what you are describing,
-
I have had that happen a couple times someone spoofed my IP and used it to NMAP my network over and over until snort blocked my own IP somehow. Unreal. Have you looked at your IPS/IDS logs?
-
Dear all, thank you so much for helping me! The problem is resolved. It turns out that the modem had been set up as DMZ, forwarding everything to a static address corresponding to the MAC of the pfSense device. The new pfSense device has a different MAC, and the modem assigned a new IP to it. Nothing was forwarded to the pfSense, as a consequence.
I have now set up MAC spoofing on pfSense, and everything is now working as it should. I assume that the spoofed MAC is saved in the pfSense config, which will eliminate the issue if the hardware will have to be replaced again.
I hope that this resolution may help others encountering a similar issue!
