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

    [solved] WAN gets IPv6 but LAN can't

    Scheduled Pinned Locked Moved IPv6
    solved
    43 Posts 7 Posters 4.0k 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.
    • crazypotato142C
      crazypotato142
      last edited by

      How can I check the prefix pFsense gets, or be sure it gets or not?

      patient0P 1 Reply Last reply Reply Quote 0
      • patient0P
        patient0 @crazypotato142
        last edited by

        @crazypotato142 check the logs in Status / System Logs / DHCP and search for "dhcp6c". Additionally you can enable debug mode: check System / Advanced / Networking: DHCP6 Debug.

        crazypotato142C 1 Reply Last reply Reply Quote 0
        • crazypotato142C
          crazypotato142 @patient0
          last edited by

          @patient0
          Can't see anything related to a prefix. I think it's confirmed it doesn't get any.

          I've seen "transmit failed: Can't assign requested address" in the logs. I've been looking for it on the internet since then.

          1 Reply Last reply Reply Quote 0
          • NeganN
            Negan
            last edited by Negan

            I never seen it mentioned here but have you enabled Allow ipv6 ?

            System/Advanced/Networking- ipv6 Options -Allow IPV6
            
            crazypotato142C 1 Reply Last reply Reply Quote 0
            • crazypotato142C
              crazypotato142 @Negan
              last edited by

              @Negan
              It's checked. Thank you for the mention.
              I mean, it says it only blocks traffic tho. pF still gotta provide IPv6 to LAN on both checked and unchecked.

              GertjanG 1 Reply Last reply Reply Quote 0
              • GertjanG
                Gertjan @crazypotato142
                last edited by

                @crazypotato142

                This :

                12a5bc36-2eb1-4e38-ad6d-80a908bb3950-image.png

                is that pfSense 2.8.0 ?
                Or do you use the "ISC DHCP" setup instead of the newer 'kea dhcp' ?

                aa58e3ec-a2dc-4ca2-b246-636e1fb5ebae-image.png

                means the DHCP PLAN server doesn't gave a IPv6 /64 prefix for your LAN.

                Normally, you should see this :

                7be39d34-566d-42ba-8e0c-c8baa09ca39c-image.png

                that said, I don't use SLAAC, so maybe I'm wrong.

                No "help me" PM's please. Use the forum, the community will thank you.
                Edit : and where are the logs ??

                crazypotato142C 1 Reply Last reply Reply Quote 0
                • crazypotato142C
                  crazypotato142 @Gertjan
                  last edited by

                  @Gertjan

                  is that pfSense 2.8.0 ?
                  Or do you use the "ISC DHCP" setup instead of the newer 'kea dhcp' ?

                  It's CE 2.7.0
                  ISC it should be because I don't have the option "DHCP backend" on Advanced>Networking tab and on services it says "dhcpd"

                  that said, I don't use SLAAC, so maybe I'm wrong.
                  I don't have the IP after "WAN/0"

                  I asked to my ISP and they approved that I get the prefix from their end. Seems like my end is the problem. I'll try to upgrade or clean install to 2.8.0 today.

                  GertjanG 1 Reply Last reply Reply Quote 0
                  • GertjanG
                    Gertjan @crazypotato142
                    last edited by

                    @crazypotato142

                    Reminder :
                    The DHCP log will show dhcp6c (DHCP v6 Client process) activity when you check this one :

                    44cb2139-547f-48c1-8c61-ce22927cd932-image.png

                    No "help me" PM's please. Use the forum, the community will thank you.
                    Edit : and where are the logs ??

                    crazypotato142C 1 Reply Last reply Reply Quote 0
                    • crazypotato142C
                      crazypotato142 @Gertjan
                      last edited by

                      @Gertjan
                      It's checked. The logs above are from dhcp6c

                      GertjanG 1 Reply Last reply Reply Quote 0
                      • GertjanG
                        Gertjan @crazypotato142
                        last edited by

                        @crazypotato142 said in WAN gets IPv6 but LAN can't:

                        @Gertjan
                        .....The logs above are from dhcp6c

                        Euh .... where ?

                        No "help me" PM's please. Use the forum, the community will thank you.
                        Edit : and where are the logs ??

                        1 Reply Last reply Reply Quote 0
                        • crazypotato142C
                          crazypotato142 @crazypotato142
                          last edited by

                          @Gertjan said in WAN gets IPv6 but LAN can't:

                          @crazypotato142 said in WAN gets IPv6 but LAN can't:

                          @Gertjan
                          .....The logs above are from dhcp6c

                          Euh .... where ?

                          @crazypotato142 said in WAN gets IPv6 but LAN can't:

                          I have these warnings on my logs

                          @crazypotato142 said in WAN gets IPv6 but LAN can't:

                          I've seen "transmit failed: Can't assign requested address" in the logs. I've been looking for it on the internet since then.

                          1 Reply Last reply Reply Quote 0
                          • E
                            eagle61 @crazypotato142
                            last edited by eagle61

                            @crazypotato142 said in WAN gets IPv6 but LAN can't:

                            But I moved to a pFsense & custom router on AP mode setup and I wasn't able to get IPv6 anymore, because pfSense can't get an IPv6 on LAN so other devices can't get over DHCPv6 either.

                            From your first screen picture you sen here i can see you only have a fe80:-IPv6-Adress on WAN. With that you can't get any LAN-IPv6. You will need regular IPv6 on WAN first. One like 2001:...

                            I guss your custom router on AP mode setup does not deliver an IPv6-Adress and/or IPv6-Prefix to your pfsense. That needs to be fixed beforehand all other setups.

                            Please read:

                            • IPv6 for generic DSL dialup and
                            • IPv6 behind an AVM Fritz!Box

                            Both Documents are from OPNsense Documentation, but helped me very much to configure my pfsense with IPv6 prefix delegation.

                            crazypotato142C 1 Reply Last reply Reply Quote 0
                            • crazypotato142C
                              crazypotato142 @eagle61
                              last edited by

                              @eagle61
                              I thought the same at first but people here told me it is fine to have a link local there. It's confusing now.

                              My setup is ONT -> pF on x64 mini PC -> AP.

                              I don't think it's about the AP, because pF can't even provide an IP address to its own LAN interface. AP is the step when LAN interface gets one.

                              E 1 Reply Last reply Reply Quote 0
                              • E
                                eagle61 @crazypotato142
                                last edited by eagle61

                                @crazypotato142 said in WAN gets IPv6 but LAN can't:

                                My setup is ONT -> pF on x64 mini PC

                                No, first step is WAN-Intertface needs a IPv6-Adress. Please read IPv6 for generic DSL dialup linked before. Your WAN-Interface (Interfaces -> WAN) is pppoe0 (means IPv4 Configuration Type = PPPoE) and IPv6 Configuration Type = DHCP6 you need to mark also:

                                • Use IPv4 connectivity as parent interface
                                • Request only an IPv6 prefix
                                • Send IPv6 prefix hint
                                • DHCPv6 Prefix Delegation size = depending on what your ISP is offering you. Try /56 but might be also /60, /62, even /64 might be possible. You have to check that out.

                                That is how it works here on a Fiber ONT with my ISP.,

                                Note: and i did not think you was talking about a WiFi-AP, but was talking about the Access Point on Internet, like DSL-Modem, Fiber-ONT:or Cable-Modem..Yoi nieed first from that defice, means from ISP a IPv6 to make it working.And your photos show you have only fe80 on WAN-PPPoE. So that can't work with just fe80

                                EDIT: hiere is my WAN Config with running IPv6
                                Bildschirmfoto_2025-06-10_18-04-37.png

                                crazypotato142C Bob.DigB 2 Replies Last reply Reply Quote 0
                                • crazypotato142C
                                  crazypotato142 @eagle61
                                  last edited by

                                  @eagle61
                                  Alright. I finally got my IPv6 back. 🙌
                                  41d18f8a-fa1f-4c95-bb83-157195a9425f-image.png

                                  First I updated it to 2.7.2 from 2.7.0. When I installed pF I thought I installed the version 2.7.2 because even on updates page 2.7.2 was selected. I used the command "certctl rehash" and it finally got fixed, let me update to 2.7.2.

                                  When the update was done, it was all the same. Later I updated it to 2.8.0 from the update page again, which made the link-local IP's disappear from the Interfaces wigdet after the update.

                                  I went back to WAN interface settings and selected the checkmark to request IPv6 prefix thru IPv4 connectivity. And finally it got the prefix, both LAN and WAN had IP's, and all my devices connected to internet.

                                  So it was pF itself since the beginning. Thank you everyone!

                                  E 1 Reply Last reply Reply Quote 1
                                  • E
                                    eagle61 @crazypotato142
                                    last edited by eagle61

                                    @crazypotato142
                                    May i ask what DHCPv6 Prefix Delegation size you are now request for? If in any case possible and supported by your ISP it shall not be /64, but /62 /60 or even better /56

                                    With a DHCPv6 Prefix Delegation size of only /64 your pfsense can't delegate prefixes for LAN and other local Networks.

                                    crazypotato142C 1 Reply Last reply Reply Quote 0
                                    • crazypotato142C
                                      crazypotato142 @eagle61
                                      last edited by

                                      @eagle61
                                      My ISP provides only /64.

                                      Made it sure, it doesn't work with other prefixes selected.

                                      E 1 Reply Last reply Reply Quote 0
                                      • E
                                        eagle61 @crazypotato142
                                        last edited by

                                        @crazypotato142
                                        This means that your ISP is unfortunately very stingy.

                                        With a /60 prefix you would be able to provide 16 /64 subnets, my ISP provides a /56 prefix so i am able to crate 256 /64 subnets with my pfsense.

                                        crazypotato142C 1 Reply Last reply Reply Quote 0
                                        • crazypotato142C
                                          crazypotato142 @eagle61
                                          last edited by

                                          @eagle61

                                          This means that your ISP is unfortunately very stingy.

                                          I know. Tho my ISP provides symmetric gigabit internet & static IP for only €15 so I'll ignore that. :D Also they are the only ISP provides IPv6 for home users right now.

                                          @eagle61

                                          With a /60 prefix you would be able to provide 16 /64 subnets, my ISP provides a /56 prefix so i am able to crate 256 /64 subnets with my pfsense.

                                          Sounds good. I'm not planning to have any subnets for home yet so it doesn't seem like a problem for now. Thank you anyway. 🙏

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

                                            @eagle61 said in WAN gets IPv6 but LAN can't:

                                            No, first step is WAN-Intertface needs a IPv6-Adress.

                                            Technically it doesn't. There are some ISP around the globe, which will give you only a prefix and not a WAN-address. In the other Sense, you can configure your WAN to use one /64 of that prefix, don't know how this is done in pfSense.

                                            @crazypotato142 You could use NPt to give many interfaces the capability to have IPv6 outbound. You would use ULAs in your LANs and then NAT everything with that one /64 you got.

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