Geekzone: technology news, blogs, forums
Guest
Welcome Guest.
You haven't logged in yet. If you don't have an account you can register now.


Forums › LAN (ethernet/Wifi/routers/Bluetooth) › pfsense - what IPv6 configuration type should I be using for my lan interface?
andicniko

10 posts

Wannabe Geek
+1 received by user: 1


#289821 30-Sep-2021 22:55
Send private message

Hello. I recently obtained a static IPv6 prefix from my ISP (2degrees).

 

On the WAN side, the static prefix is obtained the same way I used to get the dynamic prefix - using the DHCPv6 IPv6 configuration type. Same delegation size of /56, same settings, just a static prefix. So far so good.

 

On the LAN side, I currently have the IPv6 configuration type set to "track interface", tracking the WAN. This is left over from before, and is working OK. But I'm unsure if this is still right/useful now that I have a static prefix?

 

The only real issue is I can't give interface itself a static IPv6 address (which means, for example, I can't point to that address as a gateway or DNS etc).

 

Question 1: Does "track interface" just mean the LAN uses whatever prefix the WAN obtains, or is there more to it?

 

Question 2: Can I use "static IPv6" for the LAN's configuration type without any issue? Should I?

 

For example, if I know my static prefix will always be 1000:1000:1000:1000::/56, is it OK to just give the LAN interface a static IPv6 of 1000:1000:1000:1000::1/56? Or should that be /64?

 

When I try this, it seems to stop the DHCPv6 functioning and my clients stop getting addresses within the range I specify (::1000 to ::2000). I see a few addresses outside of that, and none within.

 

Maybe I just need to wait longer for clients to grab new addresses (it took ages for statically mapped addresses to actually take...).

 

And I could just be seeing SLAAC or temporary IPv6 addresses (which I understand would be outside of my specified range).


Create new topic

This is a filtered page: currently showing replies marked as answers. Click here to see full discussion.

andicniko

10 posts

Wannabe Geek
+1 received by user: 1


  #2788738 3-Oct-2021 19:45
Send private message

OK after trying various settings, and trawling many forums... I have DHCPv6 working! Many thanks to everyone for helping.

 

I'll include my working pfsense settings in full below, in case it helps someone in the future. The two things that solved my issues are underlined - both seem to be necessary.

 

pfsense settings for 2degrees fibre:

 

  • Note: Settings work on pfsense 2.5.2-RELEASE (amd64). Any settings that aren't mentioned are left as default.
  • Interfaces / WAN

     

    • General Configuration

       

      • IPv4 Configuration Type = PPPoE
      • IPv6 Configuration Type = DHCP6
      • MTU = 1508

         

        • Note: I am on 2degrees fibre in Wellington, on Chorus' network, which I understand is provisioned differently to other places. Your MTU may vary!
    • DHCP6 Client Configuration

       

      • Use IPv4 connectivity as parent interface = TRUE
      • Request only an IPv6 prefix = TRUE
      • DHCPv6 Prefix Delegation size = 56
      • Do not wait for a RA = TRUE
    • PPPoE Configuration

       

      • Username = [the username you use to log in to 2degrees broadband]@snap.net.nz
      • Password = [the password you use to log in to 2degrees broadband]
  • Interfaces / VLANs

     

    • Note: Create a VLAN, it seems the setup wizard won't ask you/do this for you.
    • Parent Interface = [select the interface you used for WAN, e.g. igb0]
    • VLAN Tag = 10
  • Interfaces / PPPs

     

    • Note: Edit your PPPoE interface created by the set up wizard, and set it to use the VLAN you just created.
    • Link Interface(s) = [e.g. igb0.10]
  • Interfaces / Interface Assignments

     

    • Note: Check (and if needed edit) your WAN interface to use the PPPoE/VLAN you edited/created above. 
    • WAN = [e.g. PPPOE0(igb0.10) - [your username]@snap.net.nz]
  • Interfaces LAN

     

    • General Configuration

       

      • IPv4 Configuration Type = Static IPv4
      • IPv6 Configuration Type = Static IPv6 [or Track interface, if you don't want to bother with static IPv6]
      • MTU = 1500

         

        • Note: I am on 2degrees fibre in Wellington, on Chorus' network, which I understand is provisioned differently to other places. Your MTU may vary!
    • Static IPv4 Configuration

       

      • IPv4 Address = [e.g. 192.168.1.1/24]
    • Static IPv6 Configuration (only if IPv6 Configuration Type = Static IPv6)

       

      • IPv6 address = [e.g. 1111:2222:3333:4444::1/64]

         

        • Note: This assumes your prefix is 1111:2222:3333:4444 and is static. You have to specifically ask 2dgrees for static IPv6 (otherwise they will assume you just want static IPv4).
      • Use IPv4 connectivity as parent interface = FALSE

         

        • Note: This is the default. I am only mentioning it because this is the one setting I am not sure about - things still work whether it is set to TRUE or FALSE for me, but I haven't read anything to indicate this is needed.
    • Track IPv6 Interface (only if IPv6 Configuration Type = Track interface)

       

      • IPv6 Interface = WAN
      • IPv6 Prefix ID = 0 [or other, not 2degrees provides a generous /56 prefix delegation]
  • THE END (if IPv6 Configuration Type = Track interface)
  • Services / DHCPv6 Server & RA / LAN / DHCPv6 Server

     

    • DHCPv6 Options

       

      • Range = [your desired IPv6 range in full, e.g. 1111:2222:3333:4444::5000 to 1111:2222:3333:4444::6000]

         

        • Note: DO NOT omit the prefix when stating the range. This is one of the issues that seemed to prevent my DHCPv6 server working properly (if the LAN interface is set to IPv6 Configuration Type = Static IPv6). By default, the range is stated excluding the prefix, e.g. ::5000 to ::6000. I'm not sure why this should matter, because the subnet field is already populated and aware of 1111:2222:3333:4444, and omitting the prefix does no harm when the LAN interface is set to IPv6 Configuration Type = Track interface.
      • Note: I had some trouble keeping the "Provide DNS servers to DHCPv6 clients" checkbox ticked. It is ticked by default, but seemed to untick by itself when changing and saving settings on this page. When ticking it again and saving, it would just disappear. However, it was ticked after navigating to another page and coming back. So I didn't have an issue in the end.
    • Services / DHCPv6 Server & RA / LAN / Router Advertisements

       

      • Subnets = [your IPv6 prefix 1111:2222:3333:4444::/64]

         

        • Note: DO NOT leave this blank. This is one of the issues that seemed to prevent my DHCPv6 server working properly (if the LAN interface is set to IPv6 Configuration Type = Static IPv6). By default this is blank, and it does no harm leaving it blank when the LAN interface is set to IPv6 Configuration Type = Track interface. I'm not sure why this should matter.
    • THE END.

I really hope that helps someone and is easy to find. In the end a reddit post from earlier this year happened to explain the underlined info (maybe one day Kage159 will see this and find out they helped?).

Create new topic








Geekzone Live »

Try automatic live updates from Geekzone directly in your browser, without refreshing the page, with Geekzone Live now.


Updates »

Are you subscribed to our RSS feed? You can download the latest headlines and summaries from our stories directly to your computer or smartphone by using a feed reader.








RSS feeds
Main feed
Forums feed
Copyright
©2002-2026 Geekzone®
Site features
Geekzone BI dashboard
Geekzone Badges
Geekzone Status Page

 

Site Information
Subscribe to Geekzone
Privacy Statement
Forum Usage Guidelines (FUG)
Advertising
Trademark and copyright