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

    Static routes disapearing for monitor ip address

    Scheduled Pinned Locked Moved Routing and Multi WAN
    2 Posts 2 Posters 2.3k 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.
    • C
      cadince
      last edited by

      I've got a multi-wan pfsense setup with 1 load balancer pool, and two failover pools (wan1-wan2 and wan2-wan1).  I've noticed something reported by other users on the site that after a while the monitor pings all start going out the main wan1 interface.

      On the web gui I looked at the routing table and there was no static route for the wan2 monitor address to force traffic out that interface.  Simple enough to add.. and it fixed the problem, for a time.

      Eventually (could be an hour, or a day) the problem resurfaces, and all the ping/monitor traffic goes out the WAN interface, now when I look at my routing tables, that static route I defined has disappeared.  I checked my config, and the route is still in the config - and if I reload the filters it comes back, but then it eventually disappears.  The monitor IP addresses are each in my ISPs network - DNS servers that respond to pings.

      wan1 and wan2 are DHCP.

      (As an aside, to see if it made any difference, If I set wan2 to static, it doesn't help, and in that case i can NEVER get the route to appear in the routing tables to force traffic down that interface.)

      I'm running 1.2.3-RELEASE on an ALIX board.

      I have seen some other posts referencing static routes that disappear… but nobody seems to have resolved the issue
      http://forum.pfsense.org/index.php/topic,19022.0.html
      http://forum.pfsense.org/index.php/topic,2942.0.html

      seems to be causing this guys problem too:
      http://forum.pfsense.org/index.php/topic,23016.0.html
      but I started a new thread cause the root cause is the routes.

      1 Reply Last reply Reply Quote 0
      • E
        eri--
        last edited by

        Try latest code.
        This should fix it for now https://rcs.pfsense.org/projects/pfsense/repos/mainline/commits/315e1253f624c8a348385b85560659c2def02aeb

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