I need to migrate a linux machine to some kind of router distribution, I've chosen pfSense for this. The problem is that the WAN configuration used on the linux machine is really crappy, however this can't be changed right now. Current configuration:
auto eth2 iface eth2 inet static address 184.108.40.206 netmask 255.255.255.255 network 220.127.116.11 broadcast 18.104.22.168 up route add -host 22.214.171.124 eth2 || true up route add default gw 126.96.36.199 eth2
The crappy thing on this is that it routes from eth0 to eth2, eth0 is a 188.8.131.52/24 subnet and eth2 uses 184.108.40.206, so an IP out of the subnet of eth0, as next hop. I tried getting this configuration to work using pfSense, therefore:
// pfSense WAN configuration static IP: 220.127.116.11/24 gateway: 18.104.22.168
This seems to work, however I had to use a /24 net, while on the original linux configuration, there is a /32 on the WAN side. Is this any problem? What's the practical difference between this? I couldn't use /32 on the pfSense WAN, as pfSense expects the gateway to be in the subnet of the WAN IP.
My current configuration now looks like this:
// pfSense WAN configuration static IP: 123.456.789.1/29 gateway: 123.456.789.4 // pfSense LAN configuration static IP: 123.456.789.1/24 - NAT is disabled
When using this configuration I can't access the web interface anymore, it works again when I reset the WAN IP - anyone knows how to get the routing working / access the webinterafce with this configuration? I know this config sucks, but as WAN and LAN are different interfaces, shouldn't pfSense be able to distinguish between them?