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

    IPv6 not assigning to LAN device - ISP Hyperoptic UK

    Scheduled Pinned Locked Moved IPv6
    26 Posts 6 Posters 3.6k 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.
    • D
      digitalberg @samleemc
      last edited by digitalberg

      @samleemc Sure, please click on the below instructions. I hope this helps.

      Setup Cloudflare Teams in pfSense

      Another benefit of using Cloudflare in pfSense is that our DNS queries are on DoT, DoH, and WARP :)

      If you need further support, PM me, and we can do a remote session :)

      Regards,

      1 Reply Last reply Reply Quote 0
      • D
        digitalberg @samleemc
        last edited by digitalberg

        @samleemc Hi Sam, I connected Hyperoptic IPv6 to my pfSense box without HO support.

        Please elaborate on your HO settings and configuration so we can pinpoint the issue.

        p.s My HO IPv6 worked without spoofing the MAC address in the pfSense.

        Have a nice weekend!
        815e6d3c-2f28-44c9-92b3-8836503b4cab-Screenshot 2022-11-18 at 21.22.50.png Screenshot 2022-11-18 at 21.22.50

        S 1 Reply Last reply Reply Quote 0
        • S
          samleemc @digitalberg
          last edited by

          @digitalberg Amazing! How did you get it to work?

          Those are my setting related to IPv6

          ee427a8b-7b00-41e9-8e9d-0d3014a439a4-image.png

          318475b0-129a-4ab7-8f68-3feff7eebab6-image.png

          d0fe04ce-5085-4afa-a03a-81dc3291f6ce-image.png

          I have 3 physical LAN ports in the machine, and I have setup a bridge "LAN" to join them together as below

          57b23734-1f5b-4508-b171-6e80536296f2-image.png

          Then each LAN is set to track the WAN interface for IPv6
          4495d9a6-7179-4494-a851-acf76a45c9d4-image.png

          d4bab4b3-ef71-463d-9969-1187f8268c9e-image.png

          All LAN are pretty much the same.

          As for the DHCPv6 and RA, I have turned off the DHCPv6 and enable RA as below
          396e76d5-5b85-4d10-bc99-08a97054d2c1-image.png

          034254f4-74d2-48d9-816c-4f0f4f65300d-image.png

          I think that's pretty much all the setting related to IPv6.

          Any difference from yours?

          Sam

          S 1 Reply Last reply Reply Quote 0
          • S
            samleemc @samleemc
            last edited by

            pfsense version is
            97f4960c-0429-447f-b8d3-2a8d679f0652-image.png

            D 1 Reply Last reply Reply Quote 0
            • D
              digitalberg @samleemc
              last edited by digitalberg

              @samleemc
              Your LANs are on the bridge, and the IPv6 configuration type is "track interface." This is the best setting, so DCHPv6 automatically assigns the client's network, but I can see some tweaking is required on your end.

              As you can see, I did not configure MAC spoofing!

              If the below settings don't work, I would tell you to start from scratch and use one LAN without bridging the LANs to see if works.

              My pfSense version: 2.6.0-RELEASE (amd64)

              a656dbd6-14d3-4abf-b8b8-1648eac969d7-Screenshot 2022-11-19 at 22.02.54.png
              b6e8796c-f6d1-4112-9807-9f7552c8ab7b-Screenshot 2022-11-19 at 22.05.25.png

              WAN:
              c5b09aa3-e53e-4303-8ee5-7dac9ba76835-Screenshot 2022-11-19 at 22.06.14.png
              a26880bf-0a0e-46eb-a371-4dd098a00883-Screenshot 2022-11-19 at 22.06.47.png

              LAN:
              9fc0c077-ec8b-491f-aa32-3d20259b8107-Screenshot 2022-11-19 at 22.08.00.png
              bac05659-2a18-45c2-bb66-7c522f02b113-Screenshot 2022-11-19 at 22.08.10.png

              DCHPv6:
              0e9b53c0-4933-462e-b9ab-381d299d249a-Screenshot 2022-11-19 at 22.10.34.png
              1b20cf8b-e84c-4956-9921-f0b779b94011-Screenshot 2022-11-19 at 22.10.47.png

              Rules tab:
              This rule is for the LAN and includes an HO IPv6 gateway, so traffic will be routed through the HO gateway.

              17ec913c-e064-428b-b8fc-28c7db9a9118-Screenshot 2022-11-19 at 22.18.12.png
              a18ce043-681e-4656-ae19-d2506fc7a13a-Screenshot 2022-11-19 at 22.18.55.png
              bc7f427e-d486-46b3-add5-dbcf3baa63cd-Screenshot 2022-11-19 at 22.19.11.png

              DNS:
              The DNS is also important for the HO connection. you can setup Hyperoptic DNS however, i have setup Cloudflare:
              b7448875-ce7c-4496-9e8c-7555bd37e892-Screenshot 2022-11-19 at 22.24.02.png
              405b8324-d507-4c26-8a76-bfbeca867c72-Screenshot 2022-11-19 at 22.24.27.png

              HyperOptic Gateway up and running:
              7d6036dd-a61b-46c0-9b4d-5f9dd317f2dd-Screenshot 2022-11-19 at 22.25.41.png

              I would recommend having sleeping pills once everything is set up. LOL, i meant to first restart the pfsense and disconnect all the clients devices and leave the pfSense for 1-2 untouched so pfSense can talk to HO to get IPv6 etc.

              S 1 Reply Last reply Reply Quote 0
              • S
                samleemc @digitalberg
                last edited by

                @digitalberg

                I followed your setting above, but still no luck.

                Btw, are you using the community version or the pfsense+ version?

                Sam

                1 Reply Last reply Reply Quote 0
                • A
                  a3sx
                  last edited by a3sx

                  Iv moved to pfsense+ 22.05 and wanted to setup Hyperoptic ivp6 and have been banging me head against the wall trying to get it working. I finaly managed to get it working and maybe what i did works for you.

                  I followed all the guides online about how others have got Hyperoptic ipv6 working and no matter what the gateway would always show as pending. I noticed that when i setup dhcp6 on the WAN interface the ipv6 link local address was removed from the WAN interface. I added the ipv6 link local address manually to the WAN interface and magicly the gateway came online and im getting ipv6 connectivity.

                  1. Find out what the ipv6 link local is for the WAN address Status->Interfaces (i had to disabled dhcp6 on WAN and reboot for it to show up again on mine)
                  2. Setup WAN dhcp6 like the other guides online for hyperoptic
                  3. Add the link local back to WAN Firewall->Virtual IPs->Add pick "IP alias" as the type and WAN as the interface, use the link local you got earlier for the address.

                  Im using static ips on my LAN interface for IPV6 and havent tested if track interface works this way as well. You also wont get an IPV6 address on WAN with Hyperoptic but its easy enough to assign WAN an IPV6 address staticly using a virtual ip once you know what your IPV6 /56 is

                  S 1 Reply Last reply Reply Quote 0
                  • S
                    samleemc @a3sx
                    last edited by

                    @a3sx

                    Hi, tried following your steps, but still no luck for me :( IPv6 doesn't seem to like me at all.

                    Can you help to have a look if I am setting it up correctly?

                    4bf0ddba-c0c7-466f-8686-465f0e6cf925-image.png

                    S JKnottJ 2 Replies Last reply Reply Quote 0
                    • S
                      samleemc @samleemc
                      last edited by

                      it actually work magically after a reboot! Thanks!!!!!

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

                        @samleemc

                        You might try changing the subnet mask to /64. A /56 is what you'd get from your ISP.

                        Here's one I set up here:

                        fe20dc63-a479-4812-ad97-ccdb1dc714f2-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...

                        1 Reply Last reply Reply Quote 0
                        • D
                          dongennl
                          last edited by

                          Thanks for all the input; I think I'm nearly there but it is still not routing any traffic over IPv6.
                          I set up as above, including the virtual IP as a3sx, and finally the WAN_DHCP6 has come up and is green (it wouldn't without the virtual IP). Amazing, never worked before. I took the address from configuring 'none' on WAN ip6 and seeing the loopback address after reboot (where does this come from??) it starts fe80::

                          My devices on the LAN are getting IP6 addresses and I can see leases on 'DHCPv6 Leases' status screen.
                          My devices are getting IPv6 addresses starting with 2002:89dc... etc, could this be based on my delegated prefix? (Where do I see the prefix I got?)

                          Yet when I open browser and do an IPv6 test all IPv6 tests fail. If I ping 'google.com' over ipv6 on diagnostics on the webUI it fails as well.

                          Feels like it's close but there is still something wrong.
                          Pfsense+ 23.01

                          If somebody would be able to look at my screenshare I'd send them money for a beer in the pub!

                          thanks B

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