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

    Issue configuring IPv6 with ULA, but works fine with Track Interface.

    Scheduled Pinned Locked Moved IPv6
    36 Posts 3 Posters 5.7k 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.
    • L
      lamboalpha @JKnott
      last edited by

      @jknott Everything works fine the moment I enable DHCPv6 (with PD). I have enabled the IP alias, but just confirming, there is not way with 1:1 or NPt to use the ISP range (which is dynamic) and set the internal network of FD00. Per the ULA comment.

      1348bae5-52b0-4759-9cfb-1aa6d5bfa42f-image.png

      Bob.DigB 1 Reply Last reply Reply Quote 0
      • Bob.DigB
        Bob.Dig LAYER 8 @lamboalpha
        last edited by Bob.Dig

        @lamboalpha said in Issue configuring IPv6 with ULA, but works fine with Track Interface.:

        but just confirming, there is not way with 1:1 or NPt to use the ISP range (which is dynamic) and set the internal network of FD00.

        Maybe there is, haven't tried it yet, because you can use the dynamic ones too (with some caveats).

        One thing one could try is maybe this, make an unused VLAN and give it a dynamic prefix via track interface. Then use that prefix to do NPt with your interface which is using the ULA and see how pfSense respond.

        Screenshot 2022-09-19 090520.png

        In the future it would be nice if pfSense would allow to reserve prefixes just for that cause. Or find another way of fixing the problems when using dynamic prefixes.

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

          @lamboalpha said in Issue configuring IPv6 with ULA, but works fine with Track Interface.:

          but just confirming, there is not way with 1:1 or NPt to use the ISP range (which is dynamic) and set the internal network of FD00. Per the ULA comment.

          Not that I'm aware of. Regardless, NAT is a bad idea on both IPv4 and IPv6. It's needed on IPv4 due to the address shortage, but not IPv6. However, your prefix should not be changing, provided Do not allow PD/Address release is selected, though I know there are some stupid ISPs that don't respect it. I've had the same prefix for a few years and it's survived replacing both the modem and the computer I run pfSense on.

          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...

          Bob.DigB 1 Reply Last reply Reply Quote 0
          • Bob.DigB
            Bob.Dig LAYER 8 @JKnott
            last edited by Bob.Dig

            @jknott said in Issue configuring IPv6 with ULA, but works fine with Track Interface.:

            Do not allow PD/Address release

            I don't have this option anymore or am I blind...

            Screenshot 2022-09-19 151011.png

            JKnottJ 1 Reply Last reply Reply Quote 0
            • JKnottJ
              JKnott @Bob.Dig
              last edited by

              @bob-dig said in Issue configuring IPv6 with ULA, but works fine with Track Interface.:

              or am I blind...

              Yes. It's on the WAN page.

              a05d631a-bdf4-4195-978d-298db1883dfb-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...

              Bob.DigB 1 Reply Last reply Reply Quote 0
              • Bob.DigB
                Bob.Dig LAYER 8 @JKnott
                last edited by

                @jknott Not for me.

                JKnottJ 1 Reply Last reply Reply Quote 0
                • JKnottJ
                  JKnott @Bob.Dig
                  last edited by

                  @bob-dig

                  How old is your version of pfSense? It was added a few years ago. It wasn't there when I started using pfSense around 6.5 years ago, but was added not long afterward. Before then, simply disconnecting/reconnecting the WAN cable was enough to cause a prefix change.

                  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...

                  Bob.DigB 1 Reply Last reply Reply Quote 0
                  • Bob.DigB
                    Bob.Dig LAYER 8 @JKnott
                    last edited by

                    @jknott said in Issue configuring IPv6 with ULA, but works fine with Track Interface.:

                    @bob-dig

                    How old is your version of pfSense?

                    I am on 22.05-RELEASE

                    JKnottJ 1 Reply Last reply Reply Quote 0
                    • JKnottJ
                      JKnott @Bob.Dig
                      last edited by

                      @bob-dig

                      I'm on 2.6.0. I have no experience with 22. Perhaps you should contact the Netgate people about this.

                      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
                      • Bob.DigB
                        Bob.Dig LAYER 8
                        last edited by

                        Maybe @stephenw10 can confirm, that that option (Do not allow PD/Address release) is missing in 22.05-RELEASE.

                        1 Reply Last reply Reply Quote 0
                        • L
                          lamboalpha
                          last edited by

                          It is set on for me per my above post. But, I am on 2.6.0 (which is 22.2 config rev).

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