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

    Out of subnet routing… (Failover IP setup)

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

      My provider put me up with a somewhat unusual, but otherwise functional routing config known as a failover IP…

      I have an ESXi with pfSense on it (amongst other things, obviously), and two IP's (I'll be using different IP's, but for the sake of discussion, the setup is working identically):

      Main IP (on ESXi mgmt)
      195.195.195.195/24
      Def GW:
      195.195.195.1

      Failover IP (on pfSense VM WAN NIC):
      195.195.110.111/32  (!!!!)
      No default gateway for this IP…

      To make it work from the pfSense I had to manually perform:
      route add -net 195.195.195.0/24 -link -iface em0
      route add default 195.195.195.1

      This works fine, I can access the pfSense WebGUI, it can access the internet, etc.

      However there are a few challenges I do not know how to solve:

      1. Getting the above two routes to stick (so they don't get deleted on every reload)
      2. Getting pfSense to accept 195.195.195.1 as a valid gateway, because the UI keeps saying it's not in any interface's network

      Any suggestions appreciated!

      1 Reply Last reply Reply Quote 0
      • F
        FearNaBoinne
        last edited by

        After more searching (I already searched before posting here) I pretty much found most of the answer here:
        https://forum.pfsense.org/index.php?topic=79141.msg431581#msg431581

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

          you can manually add your gateway for the interface then edit the gateway and under advanced settings check "use non-local gateway" (pfsense 2.4.2)

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