WAN Interface IP address - noob config question
-
pfsense comes default with 192.168.1.1/24 this is not assigned by your other router. You can change it.
Choose something like 192.168.10.1/24 Remember that you have to adjust your DHCP server to match.
-
Thanks for your response.
I changed it to 192.168.5.109, which is within the range of my router (still using this atm), but the WAN IP address gets set to whatever I change the LAN static IP address too.
Cant workout why this is happening as the APU2 has individual NICs (WAN/LAN) and I would have thought router DCHP server should assign separate IP's
-
@zzkazu Managed to set separate IP's via console and seems to be sticking. No access to internet though for devices connected to LAN interface atm.
Assume firewall rules..
-
Check your client IP.
Firewall rules for LAN should say "LAN Net" which would work fine.
If your WAN keeps grabbing the wrong IP Im inclined to believe it has a path from the LAN side somehow. How do you have things wired?
-
-
@zzkazu said in WAN Interface IP address - noob config question:
My setup is
Why do you have a Netgear router and pfSense? That's 2 routers and double NAT.
-
The WAN and LAN are within the same subnet according to the screen shot in the last post by the OP. You can't have WAN and LAN in the same subnet. You are showing both of them in the 192.168.5.0 network. The WAN is 192.168.5.109 and the LAN is 192.168.5.110. That can't work!
Draw a simple diagram of how you have things connected and post back.
-
@JKnott said in WAN Interface IP address - noob config question:
@zzkazu said in WAN Interface IP address - noob config question:
My setup is
Why do you have a Netgear router and pfSense? That's 2 routers and double NAT.
This ^^
Set the pfSense WAN interface to PPPOE and remove the Netgear.
-
You can double nat if you need too - but you can not have the same network on pfsense wan as you do its lan and expect it to route correctly.
-
-
Try killing the firewall states.
-
And what are you outbound nat rules?
-
Automatic outbound NAT rule generation.
Is that sufficient?
-
johnpoz LAYER 8 Global Moderatorlast edited by johnpoz Aug 23, 2019, 10:26 AM Aug 23, 2019, 10:24 AM
let see it please
If you can ping from your public wan, but not from your lan - points to outbound nat not being correct.I would sniff on your wan while your doing your ping from lan test.. Do you see the ping go out with your actual wan IP?
-
stephenw10 Netgate Administratorlast edited by stephenw10 Aug 23, 2019, 2:40 PM Aug 23, 2019, 2:39 PM
Check the state table size on the dashboard also. Something breaking the ruleset can present like this but you would see 0 open states in that case. You have some rules showing open states so it's probably not that. Worth checking though.
Check you have a default route in Diag > Routes.
Steve
-
-
-
Default gateway IPv4 was set to automatic. Setting it to WAN_PPPOE seems to have allowed me to ping public via LAN now..
Seems a bit strange noting I have only one Gateway PPPoE.. ... cheers saved further headaches for me
-
I have seen a bit of strangeness with the automatic gateway selection.. Maybe your pppoe connection is taking awhile to come up.. Not sure.. I don't use those types of connection, and never a lot of experience even with them with pfsense..
We can see if anyone else with more info on the details of how the automatic selection is suppose to work, and how pppoe might come into play with that, etc.
Glad we finally got it sorted! ;)
-
Yeah, I would recommend always setting the gateway to something specific there.
Steve