multiple WAN to multiple LAN

pille99

hello all
i just found description with multiple WAN/LAN about HA butnot what i am looking for

i have 4 WAN IPs

WAN1 x.x.x.239
WAN2 x.x.x.240
WAN3 x.x.x.245
WAN4 x.x.x.246
all use the same gw 193

and 4 LAN
LAN1 192.168.175.0 - GW 254
LAN2 172.16.102.0 - gw 254
LAN3 172.16.199.0 - gw 254
LAN4 10.10.10.0 - gw 254

i want to configure like all traffic incoming from WAN1 should go to LAN1 (and only to LAN1) outbound traffik from LAN1 should go ONLY to WAN1. and so on.

from my point of view - i need to configure each single WAN as an OWN network with own gateway
but if i only configure the WAN Interfaces, WAN1 worked, WAN2 gets me an error (IP address to the WAN2 Interface)
IPv4 address x.x.x.240/32 is being used by or overlaps with: WAN1(x.x.x.239/32)

no high availibility option is needed (or backup wan)

like if i install 4 seperate pfsense.

is that practially ?
thx for hints

viragomann

@pille99
Since you have multiple WAN IPs on a single line, you have to add all to a single interface on pfSense.
Configure WAN1 on the WAN interface and specify the gateway. The other IPs are to be added in Firewall > Virtual IPs as type IP alias to the WAN interface.

For the upstream traffic to get the desired source IP you have to configure the outbound NAT properly.
Switch the outbound NAT into the hybrid mode. So by default pfSense uses WAN1. For the other IPs add rules to override this behavior.
E.g. for LAN2:
interface: WAN
source: LAN2 net
dest: any
translation: select WAN2 IP from the drop down
save it.

pille99

@viragomann
hello, thx, will do like you advised
just one question left

i have multiple networks configured on the ESX, means right now, one NIC and the ISP pointing all IPs to that NIC, in the ESX i configured multiple vSwitche like
vSwitch0 -> WAN0 -> LAN0
vSwitch1 ->WAN1 ->LAN1
and so on

what you are saying:
only one vSwitch, point one IP Adress to the NIC and the other as Virtual IP in addition to the NIC - right ?

right now - its like they are multiple Networks there (virtually but it shouldnt matter for IPSense)

for me it doesnt matter how - it just neex to work and i dont want 5 gateways/Firewalls to be managing. still your suggestion is the best way doing it ?
thx once more and greetings

pille99

@pille99
hello again.
what i completly forgot to mention. the external IP is bound to a MAC. so, the esx has the interfaces with MAC configured and working. as i have seen, the mac address can only be entered at the interface page.