LAN can't connect to WAN on new install
-
@KOM:
I'm not sure if pfSense knows about your gateway. Since you have it set to DHCP, the Gateway field is blank as it's expecting to get it from your DHCP server.
If I were you, I would punt DHCP and give your WAN port a static IP address, and then define your gateway.
I tried setting the the WAN to static then added a gateway (used ip of my router). Still no luck.
-
Post a shot of Firewall->NAT->Outbound please.
-
-
There are no NAT rules for your LAN network. Why not use automatic?
-
If you must use manual, something like this should get you going:
Interface: WAN_RE0
Source: 192.168.10.0/24
Source Port: *
Destination: *
Destination Port: *
NAT Address: WAN_RE0 address
NAT Port: *
Static Port: No -
If you must use manual, something like this should get you going: …
Woo hoo. That did the trick.
Out of curiosity – what did I just do? (in layman's terms).
-
Well, first thing is you took the default configuration, set it to manual NAT, and broke your network. I have no idea why you want NAT rules for loopback addresses. The default, automatic NAT rules work in probably 99.9% of "newb" install situations.
Second, you told pfSense that traffic heading out WAN_RE0 with a source address in 192.168.10.0/24 should have the source address dynamically NAPT translated using the interface address of WAN_RE0.
-
loopbacks are set for pfsense internal services to get to the internet. They are created automatically when you switch to manual. No idea why you switched to manual outbound NAT. So far your setup doesn't need it. Automatic outbound nat would work well.
-
I didn't know that about the loopback NAT. Thanks.
-
I'll just add that your LAN firewall rule is set to allow only IPv4 TCP/UDP traffic which doesn't include ICMP (ping). You need to add a further rules to allow ICMP or change the existing rule to any IPv4 protocol.
Steve
