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

    PFSense Not Working with DHCPV6 or Stateless on tracking interface

    IPv6
    10
    48
    13.7k
    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.
    • B
      bimmerdriver
      last edited by

      I'm one of the people who has been testing these features since marjohn56 started to develop them. I'm on Telus and there are other Telus users who have also been using these features. I started a thread in www.dslreports.com/forum/telus about it.

      1 Reply Last reply Reply Quote 0
      • C
        chrcoluk
        last edited by

        I can confirm the changes in 2.4b by marjohn work wonders, on sky UK, it works with perfection now.

        pfSense CE 2.7.2

        1 Reply Last reply Reply Quote 0
        • ?
          Guest
          last edited by

          yes I'm also running @marjohn56 patch on Sky in the UK and its so stable its becoming a little dull now LOL

          And my logs are ALL SO QUIET

          1 Reply Last reply Reply Quote 0
          • M
            moscato359
            last edited by

            Comcast has now assigned me a static IPv6, which has "resolved" my issue, in theory

            I still think unmanaged RA + Tracking interface should work.

            What would be a good way to collect information on why its not working?

            1 Reply Last reply Reply Quote 0
            • B
              bimmerdriver
              last edited by

              @moscato359:

              Comcast has now assigned me a static IPv6, which has "resolved" my issue, in theory

              I still think unmanaged RA + Tracking interface should work.

              What would be a good way to collect information on why its not working?

              Tracking interface refers to the ISP. Unmanaged RA refers to your LAN. Try using assisted.

              1 Reply Last reply Reply Quote 0
              • M
                moscato359
                last edited by

                Tracking for v6 sets the IP to something based off the IP used on the tracked interface

                2604:301a:936:eb00::xxxx when tracked goes to 2604:301a:936:ebe0::xxxx

                I altered my IP, as to not expose it to the forum.

                If I have tracking on, and enable RA, RA doesn't assign my windows boxes IPs.
                If I take the same exact totally unaltered IP that tracking gives me, and make it static, RA works.

                That screams bug to me.

                Assisted doesn't make a difference. I've also tried it. It works exactly like unmanaged for IP assignment, from what I can tell.

                I just want to make sure this is bug before I report it to the bugtracker

                1 Reply Last reply Reply Quote 0
                • ?
                  Guest
                  last edited by

                  All I can tell you is that I have no problems, and as RA is quite a major part of V6 on the LAN I would have assumed others would be screaming if it did not work for them.

                  1 Reply Last reply Reply Quote 0
                  • B
                    bimmerdriver
                    last edited by

                    @moscato359:

                    Tracking for v6 sets the IP to something based off the IP used on the tracked interface

                    2604:301a:936:eb00::xxxx when tracked goes to 2604:301a:936:ebe0::xxxx

                    I altered my IP, as to not expose it to the forum.

                    If I have tracking on, and enable RA, RA doesn't assign my windows boxes IPs.
                    If I take the same exact totally unaltered IP that tracking gives me, and make it static, RA works.

                    That screams bug to me.

                    Assisted doesn't make a difference. I've also tried it. It works exactly like unmanaged for IP assignment, from what I can tell.

                    I just want to make sure this is bug before I report it to the bugtracker

                    I will vouch for Martin that tracking is working just fine. pfSense takes the prefix assigned by the edge router, concatenates the 8 bit "IPv6 Prefix ID" (not a great name, IMO) and makes a /64 (i.e., prefix + ID/64). I imagine if the prefix was smaller than /56, pfsense would pad the bits between the prefix and the ID (i.e., prefix + padding + ID/64) to make up for the difference. All addresses allocated by SLAAC or dhcpv6 will use that prefix, but you have to set the range properly (e.g., ::1000 to ::2000 or whatever).

                    If you use assisted, you will get both SLAAC and dhcpv6 addresses. This is required if you have windows and android devices. Windows uses both, but android only supports SLAAC.

                    Note, if you are using windows 10, dhcpv6 got broken in the anniversary update and still hasn't been fixed.

                    If it's still not working, please post screen captures.

                    1 Reply Last reply Reply Quote 1
                    • P
                      phil1234
                      last edited by

                      HI there. I am new to this, but I think I have the same error, so instead of openining a new thread, I post into this discussion, hope this fits and is ok.
                      pfsense 2.3.3 on a fritbox 6490.
                      I also complain that the tracked interface has a different IPV6 subnet than the interface that is tracking, but share the idea that it must be me, otherwise more people would complain :)
                      So I have my router (fritzbox) that receives an IPV6  xxxx:xxxx:a59f:8700::/56.
                      Behind it, I have pfsense with WAN, LAN and DMZ.

                      WAN 1000baseT <full-duplex>192.168.178.22
                      xxxx:xxxx:a59f:8700:20c:29ff:fe84:d9cf

                      LAN 1000baseT <full-duplex>DMZ 1000baseT <full-duplex>10.254.0.1
                      xxxx:xxxx:a59f:87ff:20c:29ff:fe08:cca

                      As you can see, the DMZ does has 87FF, not 8700 like the WAN. That is bad as I think that makes it impossible for the devices in that DMZ to receive a 8700 address, which is needed for portforwarding. Fritzbox will not forward 87FF… if I change the prefix ID in the option tracked interface, it gives me more options, but I cannot get it to become 00.

                      my wan setting is set to DHCP6/64 with that hint-checkbox.
                      my dmz setting is set to track interfacfe WAN prefix ID: 0.

                      PS: Oh and I tried DHCP relay to the WAN-Gateway (FE80::.. Fritzbox) which didn't work either. ANd cannot use static as I've been told it willchange often.</full-duplex></full-duplex></full-duplex>

                      1 Reply Last reply Reply Quote 0
                      • B
                        bimmerdriver
                        last edited by

                        @phil1234:

                        HI there. I am new to this, but I think I have the same error, so instead of openining a new thread, I post into this discussion, hope this fits and is ok.
                        pfsense 2.3.3 on a fritbox 6490.
                        I also complain that the tracked interface has a different IPV6 subnet than the interface that is tracking, but share the idea that it must be me, otherwise more people would complain :)
                        So I have my router (fritzbox) that receives an IPV6  xxxx:xxxx:a59f:8700::/56.
                        Behind it, I have pfsense with WAN, LAN and DMZ.

                        WAN 1000baseT <full-duplex>192.168.178.22
                        xxxx:xxxx:a59f:8700:20c:29ff:fe84:d9cf

                        LAN 1000baseT <full-duplex>DMZ 1000baseT <full-duplex>10.254.0.1
                        xxxx:xxxx:a59f:87ff:20c:29ff:fe08:cca

                        As you can see, the DMZ does has 87FF, not 8700 like the WAN. That is bad as I think that makes it impossible for the devices in that DMZ to receive a 8700 address, which is needed for portforwarding. Fritzbox will not forward 87FF… if I change the prefix ID in the option tracked interface, it gives me more options, but I cannot get it to become 00.

                        my wan setting is set to DHCP6/64 with that hint-checkbox.
                        my dmz setting is set to track interfacfe WAN prefix ID: 0.

                        PS: Oh and I tried DHCP relay to the WAN-Gateway (FE80::.. Fritzbox) which didn't work either. ANd cannot use static as I've been told it willchange often.</full-duplex></full-duplex></full-duplex>

                        A picture of your connectivity would be helpful. If you're connecting a pfsense to another router, the port should either be bridged through to the ISP edge router or the router pfsense is connected to must be able to delegate a prefix.

                        Please provide screen captures of your LAN, WAN and dhcpv6 settings.

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