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

    25.07 RC - no default gateway being set if default route is set to a gateway group and the Tier 1 member interface is down

    Scheduled Pinned Locked Moved Plus 25.07 Develoment Snapshots
    4 Posts 3 Posters 98 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.
    • luckman212L
      luckman212 LAYER 8
      last edited by luckman212

      adding here from https://redmine.pfsense.org/issues/16331 for more discussion and eyes:

      On my home 6100 that I factory erased and formatted with a fresh 25.07RC via Netgate installer (25.07.r.20250715.1733) I am having a bad situation occur where the default route (0.0.0.0/0) gets removed if the link drops (no carrier) on my WAN. This includes during operation, or at boot-time. The default route is not replaced by anything, thus breaking just about everything.

      I thought it might have been because I have a S2S Wireguard tunnel that uses Policy Based Routing and has a Peer with "Allowed IPs" set to 0.0.0.0/0 but I tried disabling that peer and the behavior continued. I have tried rebooting a few times to be sure this wasn't a one-off.

      If I manually go to System > Routing and choose a specific V4 gateway (my Tier2) then things start to work again.

      Similarly, if I ssh in and type

      route add default <ip_of_my_tier2_gw>
      

      That gets things working temporarily as well.

      My setup is:

      • FIOS via a 10Gtek SFP+ adapter on ix0 as Tier1 (DHCP+DHCP6)
      • a Teltonika RUTX11 as my Tier2 WAN on ix2 (RJ45)
      • LAN on ix1 (another SFP+ to a Unifi 10G switch)

      Packages installed currently are:

      • acme
      • arping
      • aws-wizard
      • Backup
      • Cron
      • Filer
      • iperf
      • ipsec-profile-wizard
      • mDNS-Bridge
      • Netgate_Firmware_Upgrade
      • Nexus
      • pfBlockerNG
      • Shellcmd
      • softflowd
      • sudo
      • System_Patches
      • Tailscale
      • WireGuard

      I have a couple of status_output.tgz debug archives collected before and immediately after a reboot. Happy to send those off to whoever @netgate to help troubleshoot this, or any other sort of troubleshooting. I'm surprised nobody else has hit this during the beta testing.

      1 Reply Last reply Reply Quote 0
      • M
        marcosm Netgate
        last edited by

        I use a gateway group as the default gateway for both IPv4 and IPv6 and it works as expected - igb0 is tier 1 and igb1 is tier 2:

        # netstat -rn | grep default
        default            192.168.1.254      UGS            igb1
        default                           fe80::da21:daff:fe19:dbb0%igb1 UG            igb1
        
        # ifconfig igb0 | grep status
        	status: no carrier
        

        You can share the files/logs here for review:
        https://nc.netgate.com/nextcloud/s/Dj3ZbjQstNB52e7

        luckman212L 1 Reply Last reply Reply Quote 0
        • stephenw10S
          stephenw10 Netgate Administrator
          last edited by

          Mmm, I'm failing to duplicate that here too.

          What do you see logged when the tier 1 gateway goes down?

          1 Reply Last reply Reply Quote 0
          • luckman212L
            luckman212 LAYER 8 @marcosm
            last edited by

            @marcosm Thanks somehow I didn't get the reply notification so I just saw this.

            I uploaded 2 tgz archives, one from before a reboot and one right after a fresh reboot.

            07b546f4-013f-4980-a7a7-6e7f4d047acf-image.png

            I will run some additional tests now and capture more logs.

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