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

      @lamboalpha Static IPv6 and no DNS?

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

        @lamboalpha

        Set up ULA the way I described in the link and it will work. Does that equipment have to be reachable from the outside? If so, you need a consistent prefix from your ISP. Otherwise, ULA should work fine. With SLAAC, addresses can be based on MAC addresses.

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

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

          I set the following for v6: WAN: SLAAC, LAN: Track Interface . Firewall: Virtual IP fd00... I disabled DHCP IPv6 and left RA enabled with fd00... the subnet. I also added the virtual IP address.
          The devices on the LAN are obtaining a IP address. However, there is no IPv6 connectivity for the router nor LAN devices (as tested by ping each interface for connectivity). I have to enable DHCP6 on the WAN for just the router to have IPv6 connectivity. I am missing something...

          @JKnott and other, thanks for the assistance.

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

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

            I set the following for v6: WAN: SLAAC, LAN: Track Interface . Firewall: Virtual IP fd00... I disabled DHCP IPv6 and left RA enabled with fd00... the subnet. I also added the virtual IP address.

            Normally, the WAN is set to DHCP6 and the LAN SLAAC.

            Get things working properly without ULA first. Then add ULA as per my instructions. I suspect you're getting things mixed up.

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

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

              @jknott Corrected, but still no IPv6 connectivity for the base configuration (no ULA). I have to have track interface and RA enabled to get IPv6 to work. RA is not possible with SLACC.

              160effbb-d187-4514-a360-afdd6a7583ac-image.png

              52336fc1-f935-4664-b526-05fd7df81aac-image.png

              a6bb3a8c-5db3-40aa-8a30-6fd4b4de34ee-image.png

              58807f91-3ca0-45f2-ba78-ff65181707de-image.png

              5f7197cb-e45b-4bb6-a43d-d0e0396e4e5c-image.png

              b3d1f2df-fbc9-4561-845b-2b8ad72c5c49-image.png

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

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

                RA is not possible with SLACC.

                It most certainly is. That's how it works. A router advertisement tells the network what the prefix is and the client provides the suffix. Maybe you can show your Router Advertisement page.

                BTW, why are you blocking out your IPv4 addresses? They're RFC1918 private addresses, which means they're meaningless outside of your LAN.

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

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

                  @jknott pfSense will not let me enable RA with SLAAC enabled on the LAN. The RA was included with the previous post. There is nothing else below the error (for the Services/DHCPv6 Server & RA page).

                  If I try to enable RA prior to selecting SLAAC, I get the following error.
                  3d499615-3225-4cb8-bca1-a343d0214c2a-image.png

                  You are right on the LAN IPv4 address, but I don't need to share it.

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

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

                    pfSense will not let me enable RA with SLAAC enabled on the LAN.

                    No. You should do what it says if you already stuck... change RA first or disable it or disable IPv6 first.

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

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

                      the application requires the servers have a static IP address. The applications are not on the pfSense box.

                      So what is this application... and where are they?

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

                        @lamboalpha

                        Change the IPv6 Configuration Type to track interface.

                        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
                        • L
                          lamboalpha
                          last edited by

                          @jknott Ok, the LAN interface has a IPv6 address. But, there is no IPv6 on the LAN. I only enabled RA, but no DHCPv6. What step do I need to next? I have not used IPv6 before and apparently need to study up on it. I thinking I would need some type of NAT or NPt, but I don't know how to setup this up on pfSense when the WAN has a dynamic IPv6 assignment. It seems like a simple ask but hard to do.

                          @Bob-Dig I said static, I should have said reserved and assigned by DHCP. There is DNS on the network, but some servers need/should have a static IP address, e.g. like the local DNS or network equipment or servers. For example: the DNS server was changing IPv6 address due to the ISP was causing issues, the system would have to fallback to IPv4 when doing DNS lookups. IPv6 had preference.

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

                            @lamboalpha

                            Can you post screen captures of your WAN, LAN and Router Advertisement pages?

                            You do not need NAT, etc.. I would expect your ISP provides a /56 prefix, which provides 256 /64 prefixes, though some ISPs provide a different size. You use the /64s for each LAN or VLAN.

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

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

                              @jknott a96ade86-b496-4949-b0ca-3d0459c2d030-image.png 2035e6cc-2c5a-4713-b948-477ab0501f88-image.png fb40accc-5067-436a-aace-645ebf3ec777-image.png 876106e4-24e0-48e2-85a8-6704d2ec759b-image.png 63d39771-0cdf-43d8-9681-21c8bf7f3125-image.png 7502b164-7071-4f9a-89ca-27823bc52c4a-image.png 8d75a796-570c-4840-bbd6-b2cc4d467cb8-image.png

                              JKnottJ Bob.DigB 2 Replies Last reply Reply Quote 0
                              • JKnottJ
                                JKnott @lamboalpha
                                last edited by

                                @lamboalpha

                                Change DHCPv6 Prefix Delegation size to whatever your ISP provides. Many, including mine, provide a /56, so 56 would go in that box.

                                Also, for Router mode I have Unmanaged - RA Flags.

                                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 @lamboalpha
                                  last edited by

                                  @lamboalpha And don't use /128 for subnet on RA...

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

                                    @JKnott @Bob-Dig Yes, I had the RA subnet wrong. I missed that when I redid all the settings. It is now set to /56, the same as the WAN. It had previously been at 64. JKnott, I changed the Router mode to Managed. When DHCPv6 is enabled, it works with assisted or managed fine.

                                    Still nothing on the LAN is getting an IPv6 address.

                                    Thanks...

                                    JKnottJ Bob.DigB 2 Replies Last reply Reply Quote 0
                                    • JKnottJ
                                      JKnott @lamboalpha
                                      last edited by

                                      @lamboalpha

                                      Assuming your ISP is providing DHCPv6-PD, it should work. Maybe the best thing is to start fresh, as you may have messed up something. Keep it simple and get it working before adding any extras.
                                      You can back up the existing config first, so you can compare.

                                      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 @lamboalpha
                                        last edited by

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

                                        Yes, I had the RA subnet wrong. I missed that when I redid all the settings. It is now set to /56, the same as the WAN. It had previously been at 64.

                                        /64 was right.

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

                                          /64 was right.

                                          That would allow only a single /64 prefix. If the ISP provides a larger prefix, that's what should be used.

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

                                          L 1 Reply Last reply Reply Quote 0
                                          • 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
                                            • First post
                                              Last post
                                            Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.