Netgate Discussion Forum
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Search
    • Register
    • Login

    Dual WAN IP routing

    Scheduled Pinned Locked Moved Routing and Multi WAN
    7 Posts 2 Posters 901 Views
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • M
      Miesje
      last edited by

      Dear All,

      I'm strubbeling for with a problem wich I can't resolve with the solutions on the forums so far.
      The thing I want, is actualy not so difficult in my opion.
      See image.

      Dual_WAN.png

      DMZ = 192.168.74.0/24
      LAN = 192.168.70.0/24

      So I have created NAT rules to let the traffic in:
      NAT Rules
      NAT_Rules.png

      OUTBOUND Rules
      I have disabled the outbout rules from DMZ to WAN01.
      Enabled also not workingOutBound_Rules.png

      WAN02 Rules
      WAN02_Rules.png

      DMZ Rules
      DMZ_Rules.png

      Logs
      The traffic is there but the website not.
      Logs.png

      The Host DMZ03 does go outside with WAN02 as IP, which is correct.
      The traffic seems to go to the correct host.
      What I'm I missing to get it to work.
      Any help would be appreciated.

      V 1 Reply Last reply Reply Quote 0
      • V
        viragomann @Miesje
        last edited by

        @miesje

        Which pfSense version are you running?

        Which WAN connection is the default gateway on?

        1 Reply Last reply Reply Quote 0
        • M
          Miesje
          last edited by

          The default gateway is WAN01

          2.5.1-RELEASE (amd64)
          built on Mon Apr 12 07:50:14 EDT 2021
          FreeBSD 12.2-STABLE

          V 1 Reply Last reply Reply Quote 0
          • V
            viragomann @Miesje
            last edited by

            @miesje
            This version has a bug causing replies going to the default gateway, regardless on which interface the requests was coming in.

            You can do a rollback to 2.5.0 or go with 2.5.2 RC.

            1 Reply Last reply Reply Quote 0
            • M
              Miesje
              last edited by Miesje

              I red something about that but I was not sure if it would affect my situation.
              I will try the RC candidate because the 2.50 will fail my IPSEC traffic.

              Will let you no if it is resolves.
              Thanks for taking the time to look at my problem.

              Regards,
              Miesje

              1 Reply Last reply Reply Quote 0
              • M
                Miesje
                last edited by Miesje

                I have turned to 2.5.2 Rc and it is working now.
                I had to remove the dhcp gateway WAN02 from the WAN02 rule, to default.

                61e39bf5-45d0-423e-bf1a-a23ac46ef7e2-image.png

                Thanks again for the help.

                V 1 Reply Last reply Reply Quote 0
                • V
                  viragomann @Miesje
                  last edited by

                  @miesje said in Dual WAN IP routing:

                  I had to remove the dhcp gateway WAN02 from the WAN02 rule, to default.

                  Didn't notice the gateway setting before. No, the gateway option in a filter rule is only meant for policy routing and that is mostly not wanted on incoming traffic.

                  1 Reply Last reply Reply Quote 0
                  • First post
                    Last post
                  Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.