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

    Loadbalance offline

    Scheduled Pinned Locked Moved Routing and Multi WAN
    6 Posts 4 Posters 2.8k 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.
    • D
      drvcrash
      last edited by

      is this normal?  it seems to be working fine even though it says offline.
      Capture.JPG
      Capture.JPG_thumb

      1 Reply Last reply Reply Quote 0
      • T
        tommyboy180
        last edited by

        Its not normal. Do your gateways respond to ICMP traffic?

        -Tom Schaefer
        SuperMicro 1U 2X Intel pro/1000 Dual Core Intel 2.2 Ghz - 2 Gig RAM

        Please support pfBlocker | File Browser | Strikeback

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

          yes .  the wierd thing is it working fine. Here is my pool setup maybe i did something wrong

          Capture.JPG
          Capture.JPG_thumb

          1 Reply Last reply Reply Quote 0
          • T
            tommyboy180
            last edited by

            huh. I don't have a clue.

            -Tom Schaefer
            SuperMicro 1U 2X Intel pro/1000 Dual Core Intel 2.2 Ghz - 2 Gig RAM

            Please support pfBlocker | File Browser | Strikeback

            1 Reply Last reply Reply Quote 0
            • GruensFroeschliG
              GruensFroeschli
              last edited by

              Have you tried to have separate monitor IPs when you add your WAN multiple times?

              We do what we must, because we can.

              Asking questions the smart way: http://www.catb.org/esr/faqs/smart-questions.html

              1 Reply Last reply Reply Quote 0
              • I
                Itwerx
                last edited by

                Second messr Gruen, you MUST use different monitor IPs for each WAN link or you will have weird results along the lines of what you're describing.  (Not that I'd know from experience or anything :).
                  Also, as a crucial sanity check, use the diagnostics ping test to the monitor IP with the respective interface selected.  You'll see notes saying that the ping test doesn't work reliably in multi-WAN and this is sort of true, but the key here is that the monitoring system is simply doing a ping as well! 
                  Have seen some very illogical pseudo-failure modes that were resolved by using the diag ping to figure out which monitoring IP was "appropriate", (i.e. worked at all), for each WAN link.  There was no rhyme or reason to what did or didn't work but they were at least consistent and the system is rock solid once you've sussed out the right combination.  And having gone through the process on quite a few of these now I can safely say that it is necessary!  (At least as of v1.2.2).
                  Also a tip - don't use the gateway as your monitor IP on any of them.  Too easy for the ISP to be having routing issues and you can't past their core so the link is functionally down even though you can reach the gateway.  So for each WAN link be sure to pick a (diag-pingable) IP which is outside of your ISPs network.

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