route incoming traffic (WAN1) on specific port to be forwarded through WAN2 to another site. Possible?
-
Is it possible to route incoming traffic on WAN1 port 12345 out on WAN2 port 12345 to another site ?
WAN1 -> LAN would have been standard NAT/port forward but I assume it doesn't apply here because in this case it needs to be forward to another host on the internet.
I searched a bit but did not find anything that apply.
-
@seanr22a
Yes. You may have to add a static route for the destination to use WAN2 gateway. Also you need a firewall rule to allow that traffic.Should the forwarded packets get the WAN2 IP as source address?
If so, you have to add an outbound NAT rule for it.
If not, you possibly run into asymmetric routing issues. On your pfSense you can activate the sloppy state type in the filter rule to avoid issues, but maybe packets are dropped by internet routers. You may have to try it out. -
I'm not as good at this as I whish but I try to understand your suggestion ....
Setup a standard NAT for that port pointing at the other site internet address
Setup a static route to make pfsense understand where to send the traffic
Setup a outbound NAT (I've never done that so I have to figure that out)and finaly the firewall rule: when creating the NAT it automatically creates the fire wall rule for incoming traffic. I'm not sure about the outbound NAT, does it create a rule automatic or do I need to create myself ?
Now I have a lot of reading to do figuring this out :) Thanks !
-
@seanr22a said in route incoming traffic (WAN1) on specific port to be forwarded through WAN2 to another site. Possible?:
Setup a standard NAT for that port pointing at the other site internet address
Yes, presuming the traffic is addressed to WAN1 IP. (In theory it may also be routed to you.)
Setup a outbound NAT (I've never done that so I have to figure that out)
So your Outbound NAT may still work in automatic mode. You have to set it to hybrid mode first and save that.
Then add a rule:
interface: WAN2
source: any
destination: <the destination IP of the forwarding>
translation: interface addressThe outbound traffic doesn't need any additional rule.
-
I give it a try tomorrow, thanks !