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

    Is there any way to hand off a prefix to another pfsense instance?

    Scheduled Pinned Locked Moved IPv6
    16 Posts 5 Posters 3.9k 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.
    • T
      tenortim
      last edited by

      Looks like the following code starting at line 1217 in file etc/inc/services.inc in origin/master is responsible:

      
                              /* prefix length > 0? We can add dhcp6 prefix delegation server */
                              if ($pdlen > 2) {
                                      $pdlenmax = $pdlen;
                                      $pdlenhalf = $pdlenmax -1;
                                      $pdlenmin = (64 - ceil($pdlenhalf / 4));
                                      $dhcpdv6cfg[$ifname]['prefixrange'] = array();
                                      $dhcpdv6cfg[$ifname]['prefixrange']['prefixlength'] = $pdlenmin;
      
      

      …

      This is in the "fake out" code for track6 interfaces. It ought to be relatively simple to make the values configurable.

      1 Reply Last reply Reply Quote 0
      • H
        hda
        last edited by

        @tenortim:

        …
        WAN setup isn't using advanced and simply requests a /60 along with the checkbox for "Send an IPv6 prefix hint ..." checked.
        ...

        To configure all things to your liking you have to use [Interfaces: WAN DHCP6 -Client- conf. Advanced] on the 1st pfSense in order to be able to manage the DHCP6 Server on that 1st pfSense.

        The method "Track Interface" is a default consumer non-professional solution. You would like to work with your quasi-Static (by dhcp6c) /60 from ISP and with your Static LAN config on 1st pfSense and 2nd pfSense.

        1 Reply Last reply Reply Quote 0
        • T
          tenortim
          last edited by

          Hi hda,
          the problem with overriding the file by hand is that that only works for a static IPv6 allocation. That's not what Comcast hand out (though it does seem pretty stable). The code that I quoted is  the beginning of code in pfSense today that sets some of the variables that cause PD to happen. If you have at least a /60, it will set up some prefixes to hand out.
          After restarting everything, I got a /63 handed out to my 2nd-level gateway.

          The only things that concern me are:

          • this functionality doesn't seem to be documented

          • the subnet sizes are hardcoded based on the original delegation

          For the most simplistic case using track interface, ISTM that we should assign one /64 to LAN, and set up delegations for /64 for the remaining address range (so in my /60 case, we'd offer up to 15x /64 prefixes) on the basis that it's unlikely that anyone will have more than two tiers (perhaps I should say "even more unlikely than somebody having more than one  ;)")

          Is there any interest in me working on the code to make this configurable i.e. to add a couple of nerd knobs for "Track interface" along the lines of

          • Enable Prefix Delegation

          • Prefix subnet size

          ?

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

            @cmb:

            Though because the DHCPv6 screen is hidden where you're using track interface (today at least), that's more convoluted.

            Just thought I'd point out Feature 3029… someone has provided a pull request for it. There are lots that would love to set custom DHCPv6 and RADVD settings with a track interface LAN, if'it's something that is really feasible.

            The S in IOT stands for Security

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

              Yeah that's a priority to get in for 2.3.

              1 Reply Last reply Reply Quote 0
              • I
                Inq
                last edited by

                Hate digging up old topics, but is this feature still on track to be included in 2.3 ? If not i've better start saving some bucks in hope that i can bribe someone working for my isp (gunning for a static /56 ).

                The problem with making something idiot proof is that the world keeps making better idiots.

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

                  It would be great if Chris would provide an update… given that 2.3 is in beta now and apparently major features aren't being added/changed, I'm getting the feeling that this won't make the 2.3 release, and the can gets kicked down the road a little more.

                  Unless it's something being tested outside of the beta snapshots, and will be merged all at once before RC... which I doubt...

                  The S in IOT stands for Security

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

                    Well, a glimmer of hope that this will make it to 2.3… :) The Redmine feature request has been assigned, and has a target version of 2.3.

                    I'll be happy to give it some testing when all is said and done!

                    The S in IOT stands for Security

                    1 Reply Last reply Reply Quote 0
                    • I
                      Inq
                      last edited by

                      YAY! merged:
                      https://redmine.pfsense.org/issues/3029#change-25320

                      The problem with making something idiot proof is that the world keeps making better idiots.

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

                        Yep… time to give this some testing when I get home tonight!!

                        The S in IOT stands for Security

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