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

    2 LAN with Different Gateway (2WAN) not load balancing

    Scheduled Pinned Locked Moved Routing and Multi WAN
    12 Posts 3 Posters 2.0k 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.
    • K
      kejianshi
      last edited by

      You should be able to cure this a number of ways.  If you want to make everything from LAN1 work on WAN1 and everything on LAN2 work over WAN2 thats easy.

      You just set up manual outbound NAT and set WAN1 for LAN1 and WAN2 for LAN2 and you should be done.

      P.S.  Other than setting up manual outbound NAT you shouldn't have to set up any rules.

      The regular old Pass all on LAN rule should work.

      I don't have 1 set up like this but seems like it should work.

      1 Reply Last reply Reply Quote 0
      • K
        kejianshi
        last edited by

        Just checking - These are different ISPs with different Gateway addresses?  right?

        1 Reply Last reply Reply Quote 0
        • DerelictD
          Derelict LAYER 8 Netgate
          last edited by

          Yeah.  I think you can also leave automatic outbound NAT enabled and just change the gateway on the pass any any rules for LAN1 to WAN1 and LAN2 to WAN2.

          This stuff basically just works.

          Changes will only apply to new states.

          I don't know what your design goals are but I would create two gateway groups, say WAN1FIRST (tier1: wan1, tier2: wan2) and WAN2FIRST (tier1: wan2, tier2: wan1) and set the gateway on LAN1 rules to WAN1FIRST and LAN2 rules to WAN2FIRST.

          Chattanooga, Tennessee, USA
          A comprehensive network diagram is worth 10,000 words and 15 conference calls.
          DO NOT set a source address/port in a port forward or firewall rule unless you KNOW you need it!
          Do Not Chat For Help! NO_WAN_EGRESS(TM)

          1 Reply Last reply Reply Quote 0
          • K
            kejianshi
            last edited by

            That also works if you don't want STRICT separation.

            I could be wrong, but in the event of a WAN outage, all traffic would then pass over whatever is still up?

            1 Reply Last reply Reply Quote 0
            • DerelictD
              Derelict LAYER 8 Netgate
              last edited by

              Yes.  Both LANs would use WAN2 if WAN1 was down and WAN1 if WAN2 was down.  Again, don't know OPs design goals.

              Chattanooga, Tennessee, USA
              A comprehensive network diagram is worth 10,000 words and 15 conference calls.
              DO NOT set a source address/port in a port forward or firewall rule unless you KNOW you need it!
              Do Not Chat For Help! NO_WAN_EGRESS(TM)

              1 Reply Last reply Reply Quote 0
              • D
                Dezireman25
                last edited by

                @kejianshi:

                You should be able to cure this a number of ways.  If you want to make everything from LAN1 work on WAN1 and everything on LAN2 work over WAN2 thats easy.

                You just set up manual outbound NAT and set WAN1 for LAN1 and WAN2 for LAN2 and you should be done.

                P.S.  Other than setting up manual outbound NAT you shouldn't have to set up any rules.

                The regular old Pass all on LAN rule should work.

                I don't have 1 set up like this but seems like it should work.

                Hi Sir thanks for the reply,

                yes i do have a manual NAT outbound to point LAN1 to WAN1 and LAN2 to WAN2 but still didn't work

                and yes again sir these ISPs has different gateways

                1 Reply Last reply Reply Quote 0
                • D
                  Dezireman25
                  last edited by

                  @Derelict:

                  Yeah.  I think you can also leave automatic outbound NAT enabled and just change the gateway on the pass any any rules for LAN1 to WAN1 and LAN2 to WAN2.

                  This stuff basically just works.

                  Changes will only apply to new states.

                  I don't know what your design goals are but I would create two gateway groups, say WAN1FIRST (tier1: wan1, tier2: wan2) and WAN2FIRST (tier1: wan2, tier2: wan1) and set the gateway on LAN1 rules to WAN1FIRST and LAN2 rules to WAN2FIRST.

                  i already have this on my firewall rule
                  LAN 1 to WAN 1
                  LAN 2 to WAN 2

                  but still didn't work.

                  1 Reply Last reply Reply Quote 0
                  • D
                    Dezireman25
                    last edited by

                    @Derelict:

                    Yes.  Both LANs would use WAN2 if WAN1 was down and WAN1 if WAN2 was down.  Again, don't know OPs design goals.

                    my goal is to have a complete separation of internet connection between 2 LAN without load balancing. i want all traffic from LAN 1 will go to WAN 1 and LAN 2 to WAN 2

                    i already did the Manual NAT Outbound and Firewall Rules, but still didn;t work. i dont know why  :( i just noticed that all traffics are going to my default gateway

                    1 Reply Last reply Reply Quote 0
                    • DerelictD
                      Derelict LAYER 8 Netgate
                      last edited by

                      @Dezireman25:

                      i already have this on my firewall rule
                      LAN 1 to WAN 1
                      LAN 2 to WAN 2

                      but still didn't work.

                      But it does work.

                      Care to post the gateways, firewall rules, and outbound nat screenshots?

                      Chattanooga, Tennessee, USA
                      A comprehensive network diagram is worth 10,000 words and 15 conference calls.
                      DO NOT set a source address/port in a port forward or firewall rule unless you KNOW you need it!
                      Do Not Chat For Help! NO_WAN_EGRESS(TM)

                      1 Reply Last reply Reply Quote 0
                      • D
                        Dezireman25
                        last edited by

                        thanks for your reply sir. already done

                        i specify the gateway on my firewall rules…

                        thanks for the help

                        1 Reply Last reply Reply Quote 0
                        • DerelictD
                          Derelict LAYER 8 Netgate
                          last edited by

                          Just trying to find whatever you have configured wrong.  If it was configured right it would be working.  Good luck.

                          Chattanooga, Tennessee, USA
                          A comprehensive network diagram is worth 10,000 words and 15 conference calls.
                          DO NOT set a source address/port in a port forward or firewall rule unless you KNOW you need it!
                          Do Not Chat For Help! NO_WAN_EGRESS(TM)

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