Author Topic: [SOLVED] OUTBOUND NAT - not working with predefinded "network names" (Read 4627 times)

katamadone [CH] · « **on:** March 11, 2019, 02:19:41 pm »

Hi there,

We use OPNsense as a virtual HA Appliance and just discovered a Problem:
When we would like to create an outbound NAT with the predefined Network Names it does not rewrite the packets. So

not working
**********
NAT defined like:

tcpdump on destination system - timestamp 13:46:31.840143:

working
**********
NAT changed to

tcpdump on destination system - timestamp 13:51:13:082851:

katamadone [CH] · « **Reply #1 on:** March 12, 2019, 10:28:15 pm »

submitted an issue on: https://github.com/opnsense/core/issues/3321

katamadone [CH] · « **Reply #2 on:** March 14, 2019, 07:38:17 am »

updated the issue
manual defined alias seems to work, but network names created by the interface setup are not working

katamadone [CH] · « **Reply #3 on:** March 14, 2019, 08:59:29 pm »

solved with patches.
Thanks for the fast changes!

franco · « **Reply #4 on:** March 15, 2019, 07:14:20 am »

Thanks for the reports, the fixes should land in 19.1.5 in about 1-2 weeks.

Cheers,
Franco

Author Topic: [SOLVED] OUTBOUND NAT - not working with predefinded "network names" (Read 4627 times)

katamadone [CH]

[SOLVED] OUTBOUND NAT - not working with predefinded "network names"

katamadone [CH]

Re: OUTBOUND NAT - not working with predefinded "network names"

katamadone [CH]

Re: OUTBOUND NAT - not working with predefinded "network names"

katamadone [CH]

Re: OUTBOUND NAT - not working with predefinded "network names"

franco

Re: [SOLVED] OUTBOUND NAT - not working with predefinded "network names"