Outbound NAT not translating when port forward
-
System:
pfsense 2.5.1 MultiWAN- reply-to globally enabled
- WAN1: not relevant, its a double nat residential and it works like a charm, port forward with port redirection and all
- Default Gateway WAN1
(addressing anoimized): - WAN2: 1.2.3.4/30
- GW-WAN2: 1.2.3.1/30
- WAN2 Public address: 5.102.102.102/32 (ISP delivers public address through routing)
Problem:
Local machine: 192.168.1.100- Added rule to egress through WAN2 (works OK)
- Added Outbound NAT for WAN2 to Public IP: 5.102.102.102/32 (Works OK)
- Machine can reach the internet and NAT WORKS OK
- Added Inbound Nat with port redirection over WAN2
- 5.102.102.102:5123 >> 192.168.1.100:6123 (Works and redirects)
- 192.168.1.100:6123>> 5.102.102.102:randomport (DOES NOT WORK)
- Outbount NAT does not work and local IP is not translated.
-
Sounds like your running into the multiwan issue
https://redmine.pfsense.org/issues/11805
I believe it is targeted to be corrected in 2.5.2, I believe there is a RC in the snap server.
-
@johnpoz Thank you for the immediate response!
Not sure if it applies. Seems the bug mentioned says the packets dont egress throuigh the correct WAN.
This is not the case for me as the packets egress correctly, but NAT is not applied.
Asking only if this may be helpful to the bug -
Well what is your outbound nat tab look like. Did you change from automatic to manual or something?
It very well could be the issue in that redmine. I would see if moving to the 2.5.2 RC clears up your issue.
-
@johnpoz changed default gateway to WAN2 and it works like a charm.
When WAN2 is secondary gateway Outbound NAT is manual and packets are directed through the correct WAN2 interface after a port forward, but they are just not being NATed and egress using the private IP through the WAN2 interface.
Reading the bug comments slowly, it has already been reported and people have it working with 2.5.2 RC
Thank you!
