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

How exactly does the trigger work in Multi-WAN?

Scheduled Pinned Locked Moved Routing and Multi WAN
5 Posts 4 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.
  • T
    tomsawyer2k5
    last edited by Sep 21, 2012, 6:00 PM

    At my office my primary internet connection just went down, but it is not switching over to the secondary internet connection.  I set the trigger level to "Packet Loss or High Latency" and I was able to see it in action when I disconnected the ethernet wire of the primary internet connection or unplug its modem.  But this time its simply an internet outage in my area.

    So my question is: Is the pfSense device checking the latency and/or packet loss between itself and the modem of the primary internet connection or is it actually checking for internet connectivity?

    1 Reply Last reply Reply Quote 0
    • H
      hagfelds
      last edited by Sep 21, 2012, 7:30 PM

      The gateway (router), unless you specify anything else as the route's Monitor IP.

      1 Reply Last reply Reply Quote 0
      • T
        tomsawyer2k5
        last edited by Sep 21, 2012, 10:08 PM

        Well that sucks because it's not serving the purpose I wanted it to.  Is there a way I can set it up to ping an URL, like google.com, every minute to check for packet loss or something, and to have a set number of retries if it fails?  Or any other method similar to this that anyone knows of would be appreciated.

        1 Reply Last reply Reply Quote 0
        • H
          heper
          last edited by Sep 22, 2012, 9:48 AM

          like hagfelds already mentioned, you can specify a monitor ip for each gateway. This can be any pingable public ip

          goto system–>routing-->gateways-->edit gateway[e]–>monitor ip-->save

          1 Reply Last reply Reply Quote 0
          • D
            darnitol
            last edited by Oct 11, 2012, 3:11 PM

            You also need to specify the failover group as the gateway under Advanced in your LAN's default allow rule.  I've forgotten to do this several times and wondered why failover isn't working until I fixed the rule!


            When it rains, it pours.

            1 Reply Last reply Reply Quote 0
            • First post
              Last post
            Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.
              This community forum collects and processes your personal information.
              consent.not_received