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

    Need help, 2 WAN, 1 LAN, Load Balancer

    Scheduled Pinned Locked Moved Routing and Multi WAN
    16 Posts 8 Posters 11.6k 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.
    • S
      sullrich
      last edited by

      This is now fixed in CVS.  If you are running a full version then issue this command from a shell:

      cvs_sync.sh releng_1

      Next go to System -> Static Routes and create a "Interface Gateway checked" route through the correct WAN interface with the destination being the DNS server/32.  Repeat this for any other DNS servers.

      This will force traffic for the DNS server out the correct interface and will solve this problem during WAN port down times.

      ForcingDNSServrsOutTheCorrectWANInterface.PNG
      ForcingDNSServrsOutTheCorrectWANInterface.PNG_thumb
      ForcingDNSServrsOutTheCorrectWANInterface.PNG_thumb

      1 Reply Last reply Reply Quote 0
      • ?
        Guest
        last edited by

        Hi Scott,

        Just had a look at the static route form and I dont have this option to select the Interface as a gateway there. Is this option been included in the latest snapshot. I am using a full Beta2 version less snapshot.

        Craig Roy

        1 Reply Last reply Reply Quote 0
        • S
          sullrich
          last edited by

          @CraigRoy:

          Hi Scott,

          Just had a look at the static route form and I dont have this option to select the Interface as a gateway there. Is this option been included in the latest snapshot. I am using a full Beta2 version less snapshot.

          Craig Roy

          This is now fixed in CVS.  If you are running a full version then issue this command from a shell:

          cvs_sync.sh releng_1

          1 Reply Last reply Reply Quote 0
          • ?
            Guest
            last edited by

            Thanks Scott,

            I give this a go later tonight after work finishes and I have time to play with it a bit.

            Thanks for all your help.

            Craig Roy

            1 Reply Last reply Reply Quote 0
            • S
              sullrich
              last edited by

              I just realized that this was breaking the routing in certain situations so I have removed it.

              The way to force the gateway correctly for DNS is to put in the next hop router to force the traffic out the correct pipe.

              Sorry about that!

              1 Reply Last reply Reply Quote 0
              • N
                namezero
                last edited by

                @sullrich:

                The way to force the gateway correctly for DNS is to put in the next hop router to force the traffic out the correct pipe.

                May you explain in more detail?

                What's "next hop router" in your situatioin?
                e.g. if WAN-1 ISP gateway is 111.111.111.1, will that be your next hop router?
                What about WAN #2's gateway? What should we do about it?

                After one figured out what's their "next hop router", where should they put "next hop router" info in pfsense? e.g. on which configuration page, under what options? Thank you.

                1 Reply Last reply Reply Quote 0
                • S
                  sullrich
                  last edited by

                  Whatever the gateway is of that interface.

                  For example if your wan is fxp0 do:

                  route get default fxp0

                  Then use the gateway listed as the next hop gateway.

                  1 Reply Last reply Reply Quote 0
                  • G
                    gfeng
                    last edited by

                    :(
                    why your lan is 168.254.1.0/24,your nat is configured for 192.168.1.0/24
                    can somebody explain the reason,is is right? ::)

                    1 Reply Last reply Reply Quote 0
                    • A
                      aerodss
                      last edited by

                      @gfeng:

                      :(
                      why your lan is 168.254.1.0/24,your nat is configured for 192.168.1.0/24
                      can somebody explain the reason,is is right? ::)

                      Actually it's a copy/paste error it should be LAN (source) (169.254.1.0/24)

                      Sorry about that

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

                        I have the ultimate live-cd version (1.0-RC1) but in this version don't are the new option "USE INTERFACE AS GATEWAY".
                        I Don't HD and need this option for solve DNS PROBLEM and other bug fixed.

                        That I can do?

                        Can't compile new live-cd without this bug?

                        Tks friends

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