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

    -SOLVED- Dual Wan, failover, not working properly

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

      SOLUTION:x

      This isn't a pfsense problem I tried to test failover functionality by connecting two routers to my main LAN on the WAN port of each router and then I connected both routers LANs to each WAN1 and WAN2 on the pfsense, failover doesnt' work with this configuration, I think it has to do with the fact that WAN1 which is connected to router1 can actually ping router2 because they're basicly on the same network and thus rendering failover useless.

      After connecting two actual ISPs to each WAN1 and WAN2 failover worked properly.

      Hi, I'm going to detail the steps I took in case something is wrong:

      1. Config both wan nics to dhcp
      2. Created a gateway group name "FAILOVER" consisting of both gateways/interfaces WAN1 and WAN2
      3. Changed default gateway to FAILOVER from the routing menu.
      4. Modified the firewall LAN rule to use FAILOVER gateway

      Everything should be working perfectly with this config as far as I know, but,

      Even though the gateway group seems to be working ok, I have to manually disconnect the LAN UTP cable for computers on the other end of the switch to actually "pick up" the change.

      This has never happened before with previous pfsense versions, I'm using latest.

      I hope someone can help me with this as I'm at total loss.

      Here's a video:
      https://www.youtube.com/embed/LqUXoETTa7w

      Thanks

      1 Reply Last reply Reply Quote 0
      • dotdashD
        dotdash
        last edited by

        Did you change the monitor IP for the gateway to something outside your network?

        1 Reply Last reply Reply Quote 0
        • R
          Robert2000
          last edited by Robert2000

          Just uploaded a video, no, the monitor IP is default. Also, I'm not sure why both gateways show up as online, shouldn't one of them stay in "pending" since they're not on the same tier? I did try using different monitor IP such as google dns servers, but that didn't fix the problem.

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