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

    IPv6 Prefix ID vs DHCPv6 Prefix Delegation size

    Scheduled Pinned Locked Moved IPv6
    5 Posts 3 Posters 2.5k 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.
    • JKnottJ
      JKnott
      last edited by

      I've noticed something curious.  On the WAN side a /48 prefix (65536 /64s) can be selected.  However, on the LAN side, the highest Prefix ID available is ff, which would limit the number of available networks to 256 (/56 prefix), instead of the 65536 available with a /48.  Is there any reason for this discrepancy?

      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
      • MikeV7896M
        MikeV7896
        last edited by

        So are you really going to create over 256 networks from local interfaces or VLANs on your pfSense box? I get the feeling that creating a dropdown list with over 65,000 list items in it would be likely to crash a browser, so they opted to limit the drop-down to a maximum of 256 items. Not to mention the load time of the page as all that HTML is generated and downloaded.

        Now someone needs to get the prefix delegation in the DHCPv6 Server working with Track Interface setups so you could sub-delegate the rest of that /48 to downstream routers.

        The S in IOT stands for Security

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

          I wasn't planning on having over 256 interfaces.  However, since the WAN config allows a /48, but the prefix ID supports no more than a /56, it implies you could get a larger prefix than you could use.  If you can't assign more than 256 prefixes, then perhaps the WAN prefix size should be limited to /56.  It might be useful if each interface could be larger than a /64, for further routing, but I don't see that available.

          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
          • DerelictD
            Derelict LAYER 8 Netgate
            last edited by

            Now someone needs to get the prefix delegation in the DHCPv6 Server working with Track Interface setups so you could sub-delegate the rest of that /48 to downstream routers.

            I would argue that ISPs need to get with the program and statically route /48s like they're supposed to.

            Chattanooga, Tennessee, USA
            A comprehensive network diagram is worth 10,000 words and 15 conference calls.
            DO NOT set a source address/port in a port forward or firewall rule unless you KNOW you need it!
            Do Not Chat For Help! NO_WAN_EGRESS(TM)

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

              I can understand why ISPs might not want to statically assign non-business customer prefixes, as the customers may come and go.  However, through the use of the DUID, the assigned address should not change, at least not for the lifetime of the DUID.

              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.