OPNsense Forum

Archive => 19.1 Legacy Series => Topic started by: osn1803 on March 11, 2019, 08:47:15 pm

Title: 19.1.3: interface bug: NAT->outbound
Post by: osn1803 on March 11, 2019, 08:47:15 pm
Salutations --

It looks like a recent update to the 19.1 series introduced an interface bug.  The web form for entering a custom NAT outbound rule won't accept valid input.  Steps to reproduce:

- install 19.1.
- update to 19.1.3.
- Go Firewall->NAT->outbound.
- Select Hybrid, then Add.
- Source address -> single host or network: 192.168.0.0/16
- translation/target -> WAN address (or whatever alias you used for the WAN interface)
- Save.

That should be all you need, and that worked fine in 18.x and also in a stock install of 19.1.  In 19.1.3, though, the response is: "The following input errors were detected: The field Destination bit count is required."

I think that's not right.  The only workaround I found was to save the configuration, re-install 19.1 from scratch, import the configuration, make the required changes to outbound NAT, and THEN update to 19.1.3.  This worked fine.

Since outbound NAT is an exceedingly rare change, barring a major network re-architecture, this workaround is not a big deal.  Just thought I'd let you know.

Thank you!
Title: Re: 19.1.3: interface bug: NAT->outbound
Post by: osn1803 on March 12, 2019, 04:07:13 am
Gah.  I just realized that this was already reported.  My apologies for the noise.
Title: Re: 19.1.3: interface bug: NAT->outbound
Post by: katamadone [CH] on March 14, 2019, 09:21:16 am
not sure if you referred to my post https://forum.opnsense.org/index.php?topic=12002.0 (https://forum.opnsense.org/index.php?topic=12002.0) but if.. I it's not related so far I can see...

But anyway I think you referred to: https://forum.opnsense.org/index.php?topic=11986.0 (https://forum.opnsense.org/index.php?topic=11986.0)