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

    IPv6 Track Interface Not Working

    Scheduled Pinned Locked Moved 21.02.2/2.5.1 Snapshots (Retired)
    3 Posts 2 Posters 648 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.
    • G
      g.shaffer
      last edited by

      I thought this issue was a result of the IPv6 Gateway issue (11454) that has been fixed in todays 2.5.1-RC candidate. Because of the IPv6 Gateway issue I had stripped out most of my IPv6 setup except for 1 VLAN network. After updating I tried to restore IPv6 on another of my VLANs using Track Interface, which was how it was setup in 2.4.5-p1. After saving an applying (with no errors reported), other than the Link Local address no IPv6 address is assigned to the interface (verified with ifconfig). I can enable DHCP6 and RA for the interface.

      Looking thru the dhcpd.log I do not see any "Listening on Socket/6/em1.3086/2600:..." or "Sending on Socket/6/em1.3086/2600:..." for the interface.

      Any device I connect to the VLAN does not get an IPv6 address.

      Looking thru the routing table, I do not see similar entries for the newly setup interface compared to the one I left up to test the IPv6 Gateway Issue.

      I setup the IPv6 Track Interface without rebooting. After rebooting, the interface came up with the correct IPv6 setup. In 2.4.5-p1 I was able to make changes to interfaces without having to reboot.

      What Info can I provide to help with this issue?

      1 Reply Last reply Reply Quote 0
      • jimpJ
        jimp Rebel Alliance Developer Netgate
        last edited by

        That's actually kind of expected the way track6 works. What you need to do is save/apply on WAN after you make changes to track6 LAN(s) because otherwise it doesn't know to reconfigure the additional delegated networks.

        At the moment rtsold doesn't let us get a list of delegated networks that the firewall can manage on its own, so we have to re-run it so that it can apply the networks itself. That only happens when the DHCP6 WAN is re-applied, or on boot.

        Remember: Upvote with the 👍 button for any user/post you find to be helpful, informative, or deserving of recognition!

        Need help fast? Netgate Global Support!

        Do not Chat/PM for help!

        G 1 Reply Last reply Reply Quote 1
        • G
          g.shaffer @jimp
          last edited by

          @jimp That worked. Thanks for the feedback.

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