OPNsense Forum

Archive => 18.7 Legacy Series => Topic started by: tetzschner on November 05, 2018, 04:19:28 pm

Title: NAT redirect port problem after upgrade
Post by: tetzschner on November 05, 2018, 04:19:28 pm

Hi

After upgrading upgrading to 18.7.6 the NAT port redirect is not working.

I've got a few rules, where I forward port 15432 (from WAN) to port 5432 to a PC on LAN. Been working until latest upgrade. When checking live-log I can see that it is hitting a deny-rule, because it's NOT doing the port-forward. Opnsense is forwarding to 192.168.0.111:15432 instead of 192.168.0.111:5432... why?

Has anyone else got this problem?

Title: Re: NAT redirect port problem after upgrade
Post by: Ciprian on November 07, 2018, 02:45:14 pm

Same here, and for me it was the fact I use aliases: in the NAT rule I changed from using an alias port for NAT to using that particular ”other” (ephemeral) NAT port, and it worked.

Reading FW logs I concluded it must be a bug which changes the internal destination (NAT) port set in the port alias with the external destination port (for which I also have an alias, but I didn't check further if not using an alias for destination port would make a difference).

It only happens for rules which have a destination port <> of NAT port