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

    Failover / Loadbalance characteristics

    Scheduled Pinned Locked Moved Routing and Multi WAN
    3 Posts 2 Posters 836 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.
    • V
      vitosmaldino
      last edited by

      Hi all,
      I am evaluating pfSense for use as router / firewall with LoadBalance / FailOver functions with multiple WANs. Initially it seemed not to work, doing more in-depth tests MAYBE I understood how it works. I kindly ask you to confirm or not the following:

      1. when a gateway goes down, the IpAddress (or its emx interface?) located on the same subnet as the gateway is marked as "down"
      2. specific entries are created in the routing table for the IP addresses used for gateways monitoring

      Point 1) seems to exclude the possibility of having more than one gateway on the same subnet because if one of the 2 goes down, the other also becomes unusable, for example:
      WANaddress: 23.11.22.154/28
      GW1: 23.11.22.145
      GW2: 11.23.22.158

      Point 2) seems to oblige a careful selection of the IPs to be used for monitoring because if the gateway to which it is associated goes down, that IPAddress becomes no longer reachable, so for example 8.8.8.8 cannot be used simultaneously as a monitor and as a DNS forwarder

      Thanks for your support.
      V

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

        @vitosmaldino
        edit:
        GW1: 23.11.22.145
        GW2: 23.11.22.158

        S 1 Reply Last reply Reply Quote 0
        • S
          SteveITS Galactic Empire @vitosmaldino
          last edited by

          @vitosmaldino re: point 2, that part is correct. You can use a web site, other DNS (1.1.1.1), basically anything that responds to pings.

          Pre-2.7.2/23.09: Only install packages for your version, or risk breaking it. Select your branch in System/Update/Update Settings.
          When upgrading, allow 10-15 minutes to restart, or more depending on packages and device speed.
          Upvote 👍 helpful posts!

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