OPNsense
  • Home
  • Help
  • Search
  • Login
  • Register

  • OPNsense Forum »
  • Archive »
  • 18.7 Legacy Series »
  • NAT redirect port problem after upgrade
« previous next »
  • Print
Pages: [1]

Author Topic: NAT redirect port problem after upgrade  (Read 1529 times)

tetzschner

  • Newbie
  • *
  • Posts: 2
  • Karma: 0
    • View Profile
NAT redirect port problem after upgrade
« 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?
Logged

hutiucip

  • Sr. Member
  • ****
  • Posts: 284
  • Karma: 49
    • View Profile
Re: NAT redirect port problem after upgrade
« Reply #1 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
Logged

  • Print
Pages: [1]
« previous next »
  • OPNsense Forum »
  • Archive »
  • 18.7 Legacy Series »
  • NAT redirect port problem after upgrade
 

OPNsense is an OSS project © Deciso B.V. 2015 - 2023 All rights reserved
  • SMF 2.0.19 | SMF © 2021, Simple Machines
    Privacy Policy
    | XHTML | RSS | WAP2