OPNsense
  • Home
  • Help
  • Search
  • Login
  • Register

  • OPNsense Forum »
  • Archive »
  • 17.7 Legacy Series »
  • 1:1-NAT not intuitive with multi-WAN
« previous next »
  • Print
Pages: [1]

Author Topic: 1:1-NAT not intuitive with multi-WAN  (Read 3337 times)

ChrisH

  • Jr. Member
  • **
  • Posts: 67
  • Karma: 6
    • View Profile
1:1-NAT not intuitive with multi-WAN
« on: September 28, 2017, 03:45:20 pm »
I have an OPNsense VM with several WAN interfaces, because my provider's routing only works correctly if you also have a MAC address for every additional public IP you use.
I have created a 1:1 NAT on WAN2 to forward everything to a single internal IP. This works for connections from the internet to WAN2.
When the internal IP tries to connect to the internet, that fails. I see the packets as PASS in the firewall log, but they don't get anywhere. Traceroutes stop at the OPNsense box.

The final solution was to create a separate firewall rule telling OPNsense to use the WAN2 gateway for all packets originating from the internal IP and going to the internet.

Shouldn't that be more intuitive? I already told OPNsense I want to translate all packets from that IP on the WAN2 interface to the WAN2 address. Can't it pick the correct gateway by itself? Or is there a better way to do this?
Logged

  • Print
Pages: [1]
« previous next »
  • OPNsense Forum »
  • Archive »
  • 17.7 Legacy Series »
  • 1:1-NAT not intuitive with multi-WAN
 

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