WAN to LAN NAT stopped WAN to OPT1 still working.
-
Hi All,
I am sure this is a case of PEBKAC. I have had my pfsense running for a while now. after a reboot the other day it appeared to stop routing to LAN from WAN. but WAN to OPT1 is working perfectly.
is there anything obvious I should be looking for? I can still ping LAN addresses from PFSENSE.
for some info of my network. LAN (172.20.100.X) has it's own windows AD, so DHCP,DNS,gateway are all on thier own. I only need to route WAN-LAN to access things like my webserver and my VOIP phones at external sites. I dont use PFSENSE as a gateway on this network. I use it as a proxy to bypass the corporate line for some services. PRoxy part still works as before.
OPT1 (192.168.2.x) is on it's own VLAN. It does not need routing to/from LAN. PFSENSE is doing DHCP, DNS for this network with PFSENSE as the gateway. It's used as a guest network and to host some services (PDQ machine, Franking Machine etc.). Opt1 routing is working as it did before. so PDQ machine, franking machine are working and can get an outside connection. There is a webserver that is on both networks. It's rule was pointing to it's 172 address and was no longer accessible. I changed the alias to point to the webservers 192 address and it was back online after a filter refresh.
I am not a networking expert and still learning PFsense. I am assuming it's NAT somehow not passing to LAN but I dont know why. 172 network recently got a new gateway on a different address but pfsense dosen't know about other gateways on LAN anyway? Is there a way to clear PFsense ARP cache, maybe that's the issue? Is there something obvious I should be looking for?