Bug #4244
closed
outbound nat applied on wrong interface.
0%
Description
When i put a manual outbount-nat-rule on em0, it is applied at traffic leaving from interface em3
In this case i'm using a CiscoVPNclient behind pfSense to connect to a remote site.
The ISAKMP traffic over port 500 is natted by a rule that is present on em0. This makes it use a private ip while em3 is connected to the isp using a public ip. As expected that fails..
A outbound nat rule is also pressent on em3, that however does not perform any natting to the traffic..
Looking at rules.debug and even pfctl -sn | grep em3 doesnt show anything strange..
Updated by Pi Ba almost 11 years ago
To add some more info to this issue, perhaps the traffic is properly natted as em0 is the default route, and that is where this traffic should actually be send to. But traffic is send out through em3 nontheless..
Default route shown by 'netstat -4 -r | grep default' does point to the gateway used by em0.
No pbr rules are present.
Updated by Pi Ba almost 11 years ago
Ignore this one, false alarm sorry. I hacked some rules in the filter.inc that did force a route-to. removing those.. And testing mobile-ipsec again.
Updated by Chris Buechler almost 11 years ago
- Status changed from New to Rejected
there are no such issues, please post to the forum or list for assistance.