OPNsense Forum

Archive => 19.1 Legacy Series => Topic started by: katamadone [CH] on March 11, 2019, 02:19:41 pm

Title: [SOLVED] OUTBOUND NAT - not working with predefinded "network names"
Post by: 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:
(https://i.ibb.co/YbtMnPS/image.png)

tcpdump on destination system - timestamp 13:46:31.840143:
(https://i.ibb.co/4sqfrS0/2019-03-11-13-58-57-m-Remote-NG-conf-Cons-xml-vdi-black.jpg)

working
**********
NAT changed to
(https://i.ibb.co/FxpmJMB/image.png)

tcpdump on destination system - timestamp 13:51:13:082851:
(https://i.ibb.co/CzkDwJs/2019-03-11-13-58-45-m-Remote-NG-conf-Cons-xml-vdi-black.jpg)

Title: Re: OUTBOUND NAT - not working with predefinded "network names"
Post by: katamadone [CH] on March 12, 2019, 10:28:15 pm

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

Title: Re: OUTBOUND NAT - not working with predefinded "network names"
Post by: katamadone [CH] 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

Title: Re: OUTBOUND NAT - not working with predefinded "network names"
Post by: katamadone [CH] on March 14, 2019, 08:59:29 pm

solved with patches.
Thanks for the fast changes!

Title: Re: [SOLVED] OUTBOUND NAT - not working with predefinded "network names"
Post by: franco 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