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

    Static IPv6 addresses (last 64bits) with dynamic ISP prefix /56

    IPv6
    5
    8
    1.3k
    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.
    • S
      SirSilentBob
      last edited by

      Can anyone please give an EXAMPLE of how to set static ipv6 IP addresses for LAN devices, when you have a dynamic prefix? I'm seeing various posts on this and other forums that say it's possible with pfSense.... but then no one ever tells you HOW or gives an example. The prefix with my isp does not change often, but it does happen with an extended power outage or extended system maintenance, even with DUIDs set, even with "Do not allow PD/address release checked, etc.

      I have a /56 from the ISP, how do I set it so that the last 64 bits stay consistent and prefix changes don't kill devices?

      Yes, I understand that "stateless" to let devices auto-pick their addresses is the "preferred" way but I need some devices to have consistent addresses for some particular settings and my own sanity. I do not want to have to manually look at the IP info on a device over and over again because, it randomly decided it wants to change its IPv6 address for whatever reason. I don't care if it's "trackable" to keep the same ending 64 bits or anything like that. I am trying to keep the same semblance of order that you have on a privately addressed IPv4 network where all your private address assignments can be memorized, and do as much of the the same as possible with IPv6. It's no big worry to remember the first 56 bits, and deal with an occasional change when you know what the last 64 bits are, because they don't change every time the wind blows.

      Do I just put in all zeroes for the first 64 bits of the IPv6 address, or something else? What is the "placeholder value" to use that the system will know to populate with the first half of the address which other than the two characters of the prefix ID that I can set, will also be the ISP's /56?

      Thanks for any help!

      0d6591d6-5556-4ed0-a0a1-295595786c3d-image.png

      Bob.DigB the otherT JKnottJ P 4 Replies Last reply Reply Quote 0
      • Bob.DigB
        Bob.Dig LAYER 8 @SirSilentBob
        last edited by

        @sirsilentbob do

        ::123
        
        1 Reply Last reply Reply Quote 0
        • the otherT
          the other @SirSilentBob
          last edited by

          @sirsilentbob Hey there,
          as mentioned in topics about IPv6 before: do you really need DHCPv6? Keep in mind that i.e. android devices cannot work with dhcpv6 but instead expect SLAAC.
          So in case you do not need dhcpv6 use SLAAC, you can set static ULAs as well (that will then work with android devices as well).

          the other

          pure amateur home user, no business or professional background
          please excuse poor english skills and typpoz :)

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

            @sirsilentbob said in Static IPv6 addresses (last 64bits) with dynamic ISP prefix /56:

            Can anyone please give an EXAMPLE of how to set static ipv6 IP addresses for LAN devices, when you have a dynamic prefix? I'm seeing various posts on this and other forums that say it's possible with pfSense.... but then no one ever tells you HOW or gives an example. The prefix with my isp does not change often, but it does happen with an extended power outage or extended system maintenance, even with DUIDs set, even with "Do not allow PD/address release checked, etc.

            You can use Unique Local Addresses to provide stable LAN 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...

            1 Reply Last reply Reply Quote 1
            • P
              pfadmin @SirSilentBob
              last edited by

              @sirsilentbob This is a thing that no one likes to understand here. No chance. As I remember some service from freebsd gives not the right things back so pfsense can not determine the prefix. I don't understand this, because we humans can read the prefix in interface. Use a fritzbox instead.

              ULA will not work, it is not reachable from internet. Things about slaac and dhcpv6 have nothing to do with the problem. After devices have a new IPv6 no one knows about and so the device is not reachable from internet.

              Still waiting...

              (Or I'm missing some things in between?)

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

                @pfadmin

                Have you set Do not allow PD/Address release on the WAN page?

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

                P 1 Reply Last reply Reply Quote 0
                • P
                  pfadmin @JKnott
                  last edited by

                  @jknott yes, but this is not what we talk about. We need the prefix as an variable value throug all services in pfsense. If the prefix would be always the same, then there is no problem. but it isn't in the real world. sometimes it changes no matter of Do not allow PD/Address release

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

                    @pfadmin

                    Assuming you want access from elsewhere, how would that help? You still have to allow the outside world to know what the address is.

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