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

    Tinkering with dhcpv6 to get IPv6 working on LitFibre (UK)

    Scheduled Pinned Locked Moved IPv6
    7 Posts 3 Posters 559 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.
    • F022YF
      F022Y
      last edited by

      Re: Coming back to PFsense but IPv6 doesn't appear to work

      So it's been awhile since i tried getting this working due to changing job and family affairs (not worth the drama) but i got a moment recently to try setup my ISP to a Optiplex 7050 running pfsense 2.7.2.

      To clear up my awful description in my original thread:-

      ISP ont > RJ45 > WAN on Optiplex > LAN on Optiplex > Network switch > Rest of network etc

      ISP is convinced that no funky settings are required to get pfsense to work.

      On ISP router it was set with dhcp on IPv4 and dhcpv6 on IPv6

      The static address i get on IPv4 is done on DHCP reseravtion to their routers MAC so that is solved with pfsense's MAC spoofing in Interfaces>WAN>General Config.

      On the ISP router the device IPv6 address was 2a10:bcc2:xxxxx::xxxx/128 and the IPv6 delegated address was 2a10:bcc2:xxxx:xxxx::/62 so i have set under Interfaces>WAN>DHCP6 Client Config the Prefix delegation size to /62 (I assume this is correct).

      I have enabled the debug and can see the following:-

      f6194278-3df8-4afe-b544-276a5b7e9a5b-image.png

      And that fe80 address matched the IPv6 Gateway that i saw on the ISP router but i assumed that fe80 addresses were like home class c addresses so didn't pay them any mind.

      For the WAN i have tried :-

      2fb36879-bb72-4a5e-91ee-d8a9d7db5894-image.png
      and
      66e68ebc-ccfa-4507-a99f-4d0c1b70d015-image.png

      Under the first my WAN interface seems to get a IPv6 address
      d9895c19-c5eb-48b9-8296-56eea4443f01-image.png
      but https://ipv6-test.com/ tells me it doesn't work.

      Under Track Interface the IPv6 address goes
      5696f824-e88b-4514-96a4-6bfcf2af6689-image.png
      and the IPv6 test fails.

      I wholeheartedly know it's a setting i've missed but i cannot figure it out so thought i'd give it one last shout before i packed it up for good.

      GertjanG 1 Reply Last reply Reply Quote 0
      • U
        Uglybrian
        last edited by

        Hi, I would double check your prefix with your ISP. Maybe try a 64 or a 60 instead of the 62. I would also try the other two popular prefixes of 48 and a 56. You do have rules on your lan allowing ipv6, right?

        1 Reply Last reply Reply Quote 1
        • U
          Uglybrian
          last edited by Uglybrian

          yep looks lick a 62 is correct

          Screenshot from 2024-07-31 14-50-34.png

          See if anything on this thread helps https://forums.overclockers.co.uk/threads/lit-fibre.18955934/page-8#post-36709652

          F022YF 1 Reply Last reply Reply Quote 1
          • GertjanG
            Gertjan @F022Y
            last edited by Gertjan

            @F022Y said in Tinkering with dhcpv6 to get IPv6 working on LitFibre (UK):

            ISP is convinced that no funky settings are required to get pfsense to work.

            Aha !
            That means that when you activate IPv6 on WAN like this :

            c9d8949a-3d59-4b6e-8c39-65d4a1dfdc52-image.png

            and these 'special' settings (== set nothing) :

            38254826-7744-45a0-a11f-53e59b478546-image.png

            then you will get a prefix on every LAN where you've set IPv6 tracking.

            This

            ISP is convinced that no funky settings are required to get pfSense to work.

            yeah ... and then they announce stuff like "/62" which makes them .... if funky isn't the word here, it is very uncommon, non RFC, and totally unique.

            I have enabled the debug and can see the following:-

            8272a79c-9fee-480d-84ca-25428ea03340-image.png

            but you don't obtain a prefix like (same script sequence, with a prefix answer) :

            f3102764-5f85-4034-8855-28d6159d3c44-image.png

            206aa580-e228-4aa9-b85b-33caf05fea32-image.png

            You can't track WAN interfaces ....
            Or maybe you can : the IPv6 for this WAN comes from another WAN ?? Never saw or heard that before.

            Btw : don't feel special.
            My ISP hands over a prefix, just one /64. Even if they say : we have a /56 for you, I only can get one. Totally broken.

            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
            • F022YF
              F022Y @Uglybrian
              last edited by

              @Uglybrian That's a really helpful link thank you, I can see where i've gone wrong i think.

              The wife has told me i can "play" with the router on Sunday so will give it a go and report back.

              @Gertjan I assumed i should see some sort of "response" to the DHCP request but didn't, again not hugely familiar with the IPv6 setup but one of those gotta get my head around it some day kinda things as it's been several years since i had to manage networks with anything more complicated than a VLAN on a /22 subnet crossing an MPLS lol

              1 Reply Last reply Reply Quote 0
              • F022YF
                F022Y
                last edited by F022Y

                I didn't get chance to touch this yesterday but will give it a poke this week

                1 Reply Last reply Reply Quote 0
                • F022YF
                  F022Y
                  last edited by

                  Following the info on the link provided worked so i'm all good to go. Thanks again

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