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

    Are multiple PDs (IPv6 /64s) possible?

    Scheduled Pinned Locked Moved IPv6
    5 Posts 3 Posters 1.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.
    • S
      securityguy
      last edited by

      Rogers has started handing out IPv6 via DHCP. I'm getting a /128 for the WAN and a /64 for my primary LAN and it works fine. However, attempts to get a /62, /60, etc, etc. all fail. I'm looking for a /64 for my second LAN.

      I'm told that Rogers will only provide /64s, but it may be possible to obtain more than one.

      Is this possible with pfSense? Any hints, help, or suggestions?

      Thanks!

      1 Reply Last reply Reply Quote 0
      • C
        cmb
        last edited by

        You'll need an additional NIC plugged into your cable modem in that case, as it'll have to issue a DHCP6 request from another interface. You're probably limited to a single IPv4 IP, so need to set the second to IPv4 "none".

        1 Reply Last reply Reply Quote 0
        • MikeV7896M
          MikeV7896
          last edited by

          @cmb:

          You'll need an additional NIC plugged into your cable modem in that case, as it'll have to issue a DHCP6 request from another interface. You're probably limited to a single IPv4 IP, so need to set the second to IPv4 "none".

          Would that even work? I was under the impression that the DUID for DHCPv6 should be the same for a whole system, regardless of what interface is used to make the request. If the same DUID is presented on a different interface, wouldn't it just receive the same address/prefix and change the ISP's routing to go to the new interface instead?

          https://tools.ietf.org/html/rfc3315#page-19
          The DUID is
            designed to be unique across all DHCP clients and servers, and stable
            for any specific client or server - that is, the DUID used by a
            client or server SHOULD NOT change over time if at all possible; for
            example, a device's DUID should not change as a result of a change in
            the device's network hardware.

          The S in IOT stands for Security

          1 Reply Last reply Reply Quote 0
          • C
            cmb
            last edited by

            Ah, yeah you might be right. It depends on the behavior of the provider in that case. It's worth a shot, but take care since it might well break everything. :)

            1 Reply Last reply Reply Quote 0
            • S
              securityguy
              last edited by

              Thanks for the info – much appreciated!

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