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

    "IPv6 Prefix ID" values being ignored for LAN interface when track interface enabled - pfSense 2.5.0

    Scheduled Pinned Locked Moved IPv6
    7 Posts 3 Posters 1.1k 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
      foo
      last edited by

      I have a /48 allocated by my ISP. In pfSense I normally have the IPv6 addresses for the LAN interfaces set to track interface. However when I specify the /64 prefix ID to use in the "IPv6 Prefix ID" field (any hex value between 0000 to ffff) the LAN interface doesn't change from using the first available /64 prefix from the /48 prefix. I have tried with several pfSense VMs and the behaviour is always the same.

      Am I doing something wrong here or is this a bug in pfSense (using version 2.5.0)?

      JKnottJ DerelictD 2 Replies Last reply Reply Quote 0
      • JKnottJ
        JKnott @foo
        last edited by

        @foo said in "IPv6 Prefix ID" values being ignored for LAN interface when track interface enabled - pfSense 2.5.0:

        Am I doing something wrong here or is this a bug in pfSense (using version 2.5.0)?

        It works for me. I have a different prefix ID on 3 different interfaces. I'm also running 2.5.0.

        PfSense running on Qotom mini PC
        i5 CPU, 4 GB memory, 32 GB SSD & 4 Intel Gb Ethernet ports.
        UniFi AC-Lite access point

        I haven't lost my mind. It's around here...somewhere...

        1 Reply Last reply Reply Quote 0
        • DerelictD
          Derelict LAYER 8 Netgate @foo
          last edited by

          @foo You have to save WAN after changing the track interface prefix id. They are set when WAN is configured, not when the inside interface is changed.

          Chattanooga, Tennessee, USA
          A comprehensive network diagram is worth 10,000 words and 15 conference calls.
          DO NOT set a source address/port in a port forward or firewall rule unless you KNOW you need it!
          Do Not Chat For Help! NO_WAN_EGRESS(TM)

          JKnottJ 1 Reply Last reply Reply Quote 0
          • JKnottJ
            JKnott @Derelict
            last edited by

            @derelict

            I don't recall ever having to do that.

            Hang on a minute and I'll try another one.

            ....

            I just added IPv6 & prefix ID to another interface for a total of four.

            PfSense running on Qotom mini PC
            i5 CPU, 4 GB memory, 32 GB SSD & 4 Intel Gb Ethernet ports.
            UniFi AC-Lite access point

            I haven't lost my mind. It's around here...somewhere...

            DerelictD 1 Reply Last reply Reply Quote 0
            • DerelictD
              Derelict LAYER 8 Netgate @JKnott
              last edited by

              @jknott Well, that's the way it is.

              Chattanooga, Tennessee, USA
              A comprehensive network diagram is worth 10,000 words and 15 conference calls.
              DO NOT set a source address/port in a port forward or firewall rule unless you KNOW you need it!
              Do Not Chat For Help! NO_WAN_EGRESS(TM)

              JKnottJ 1 Reply Last reply Reply Quote 0
              • JKnottJ
                JKnott @Derelict
                last edited by

                @derelict

                Not here. I even rebooted after setting, to make sure it stuck. I have never had to reboot after setting the prefix ID.

                Here's a screen shot of my interface list. The one marked Cisco didn't even have IPv6 enabled until this morning. I then enabled IPv6 and assigned prefix ID 7. I verified it was configured. I then rebooted to ensure it stayed. Maybe you should try again.

                ac496eb8-93ec-4f48-a086-290ad942ad25-image.png

                PfSense running on Qotom mini PC
                i5 CPU, 4 GB memory, 32 GB SSD & 4 Intel Gb Ethernet ports.
                UniFi AC-Lite access point

                I haven't lost my mind. It's around here...somewhere...

                DerelictD 1 Reply Last reply Reply Quote 0
                • DerelictD
                  Derelict LAYER 8 Netgate @JKnott
                  last edited by

                  @jknott I didn't say reboot. I said save WAN again. Your workflow might be triggering a dhcp6c refresh, but, in general, when you make changes to inside interfaces set to "track interface" you have to save WAN again to pick them up. The dhcp6c client is the mechanism that sets all of the interface addresses. That happens when dhcp6c receives the PD. That happens on WAN. pfSense itself does not do any of that work.

                  Chattanooga, Tennessee, USA
                  A comprehensive network diagram is worth 10,000 words and 15 conference calls.
                  DO NOT set a source address/port in a port forward or firewall rule unless you KNOW you need it!
                  Do Not Chat For Help! NO_WAN_EGRESS(TM)

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