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

    IPv6 broke after reboot 21.02 (Pfatt) works on 2.4.5 though

    Scheduled Pinned Locked Moved IPv6
    3 Posts 2 Posters 571 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.
    • M
      matthewgcampbell
      last edited by matthewgcampbell

      Hello,

      I’m unsure if I should create a bug report on not as I’m running pfatt, but on 21.02 IPv6 seems to not come back after a reboot, this issue was solved on 2.4.5 with “ Use IPv4 connectivity as parent interface” but on 21.02 when you check this it doesn’t seem to fix the issue, with that checked on 2.4.5 it seems to come back after reboot no problem, I’ve done some testing, reinstalling etc. pfsense plus but this issue seems to still occur, it could be a weird quirky issue with netgraph on 21.02, I’m just not sure what to test to create a bug report. Also I’m unsure if anyone is having a similar problem and found a fix

      1 Reply Last reply Reply Quote 0
      • MikeV7896M
        MikeV7896
        last edited by

        A number of people, myself included, have found that with a dynamic IPv6 prefix, the monitor address needs to be manually configured in the Routing settings (System > Routing). The gateway is properly added to the routing table, but for some reason pfSense isn't parsing the gateway address to be monitored.

        If you add the Gateways widget to your dashboard, you'll probably see that it's in "Pending" state without a manually specified monitoring address. Once you add one, it should become "Online". Or you could just check the box to assume that the gateway is always online. If it's your only WAN connection, there's no harm in doing that, since you don't have a fallback if it does go down.

        This happens on 2.5.0 and 21.02 (since they're essentially the same). A bug has already been opened if this is your issue.

        The S in IOT stands for Security

        M 1 Reply Last reply Reply Quote 1
        • M
          matthewgcampbell @MikeV7896
          last edited by matthewgcampbell

          @virgiliomi does re-saving the interface fix the issue? That seems to be the case with me.

          Edit: did some testing and it seems that my interface got corrupted, deleted it and re made it and now its all good, survives reboots, looked in the logs and saw that the dhcp6c precess couldn’t find the interface and then it would quit.

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