WAN Interface IP address - noob config question

[zzkazu]

@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..

[chpalmer]

@zzkazu

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]

Heres the rules I'm using.

WAN on igb2
LAN igb1

[JKnott]

@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.

[bmeeks]

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.

[NogBadTheBad]

@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.

[johnpoz]

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.

[zzkazu]

Thanks for the advice. I have tried a PPPoE configuration.

DSL Modem "Bridged" to
APU2 WAN interface
APU2 LAN interface to
L-SG108PE switch

WAN interface set to PPPoE
LAN Static IP

On LAN side still cant ping out publicly.

DCHP service running and allocating leases
No FW rules running on WAN

[NogBadTheBad]

Try killing the firewall states.

[johnpoz]

And what are you outbound nat rules?

[zzkazu]

Automatic outbound NAT rule generation.

Is that sufficient?

[johnpoz]

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]

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

[zzkazu]

Thanks for the help here, learning lots.

Still can ping and resolve via WAN but not LAN

Only taking a guess but LAN active states seem closed, could that be the issue? I have reset states a couple of times.

using Packet capture (WAN side) cant see any private IP addresses...

thanks

Outbound NAT

[johnpoz]

Where is your default route?

That looks like your wan pinging your gateway.. But I see no default route in your routing table.. So if your client pings 8.8.8.8 why would it get routed out your internet?

Lets see your gateways

[zzkazu]

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

[johnpoz]

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! ;)

[stephenw10]

Yeah, I would recommend always setting the gateway to something specific there.

Steve