ISP Gives Multiple IPV6 DP /64

Networking & Firewalls
1

Hello,

My ISP assigns Multiple /64 so on my pfsense i just can get the lan to work no other interface works and i understand that this is the way its suppose to work and some people that are stuck with one /64 don’t have many options, however my situation is a little different as i can have as many /64 as i want (Until 256 /64) so in reality they give me a /56 but as i`m a residential client I’m not allowed to get a /56 or /60.
Is there a way a can get /64 to my vlans / vpns etc?

As Residential client i Dont get Bridge Mode and no Static Ip.

Thanks

2

I’m assuming that your ISP sends out IPV6 addresses via DHCP6. It would be helpful for you to provide the sections of the dhcp logs from pfsense, particularly those from dhcp6c (on console: grep dhcp6c /var/log/dhcpd.log ). That will show exactly what you’re getting from the ISP. For privacy, you can x out most of the address.
Otherwise, I don’t think there’s enough info available to help you. Do you get multiple “IA_PD prefix:” lines in the dhcp6c logs?

3

Hello,
Thank you for replying.

According to their support i have been assign a DP of /56 and they use SLAAC to send addresses to clients.
As i couldn’t get a /56 or even a /60 to work a start to look for answers online and found a chat where there was i guy that use to work at my isp and he confirm that they do ended assign /56 but they don’t allow residential clients to have bigger than /64 (So just one subnet). but he also confirmed that is possible to have many /64 (up to 256)
I have tested just that ans in fact i can get multiple /64s like:

1 device 2001:xxxx:xxxx:xx01:aaaa:aaaa:aaaa:aaaa/64
2 device 2001:xxxx:xxxx:xx02:aaaa:aaaa:aaaa:aaaa/64
3 device 2001:xxxx:xxxx:xx03:aaaa:aaaa:aaaa:aaaa/64
4 device 2001:xxxx:xxxx:xx04:aaaa:aaaa:aaaa:aaaa/64

The clients connected to this routers get valid ipv6 and connect to the internet and also pass the tests on the ipv6 test sites.

Thank you.

Mar 2 06:46:00 kea-dhcp6 38076 INFO [kea-dhcp6.dhcp6.0xf2c9ec12000] DHCP6_STARTED Kea DHCPv6 server version 2.4.0 started
Mar 2 06:46:00 kea-dhcp6 38076 WARN [kea-dhcp6.dhcp6.0xf2c9ec12000] DHCP6_MULTI_THREADING_INFO enabled: yes, number of threads: 4, queue size: 64
Mar 2 06:46:00 kea-dhcp6 38076 INFO [kea-dhcp6.dhcpsrv.0xf2c9ec12000] DHCPSRV_CFGMGR_USE_ALLOCATOR using the iterative allocator for IA_PD leases in subnet 2001:xxxx:xxxx:xx01::/64
Mar 2 06:46:00 kea-dhcp6 38076 INFO [kea-dhcp6.dhcpsrv.0xf2c9ec12000] DHCPSRV_CFGMGR_USE_ALLOCATOR using the iterative allocator for IA_TA leases in subnet 2001:xxxx:xxxx:xx01::/64
Mar 2 06:46:00 kea-dhcp6 38076 INFO [kea-dhcp6.dhcpsrv.0xf2c9ec12000] DHCPSRV_CFGMGR_USE_ALLOCATOR using the iterative allocator for IA_NA leases in subnet 2001:xxxx:xxxx:xx01::/64
Mar 2 06:46:00 kea-dhcp6 38076 INFO [kea-dhcp6.dhcp6.0xf2c9ec12000] DHCP6_USING_SERVERID server is using server-id 00:01:00:87:2d:2c:62:68:20:90:27:e0:14:6e and stores in the file /var/db/kea/kea-dhcp6-serverid
Mar 2 06:46:00 kea-dhcp6 38076 INFO [kea-dhcp6.dhcpsrv.0xf2c9ec12000] DHCPSRV_MEMFILE_LFC_SETUP setting up the Lease File Cleanup interval to 3600 sec
Mar 2 06:46:00 kea-dhcp6 38076 INFO [kea-dhcp6.dhcpsrv.0xf2c9ec12000] DHCPSRV_MEMFILE_BUILD_EXTENDED_INFO_TABLES6 building extended info tables saw 7 leases, extended info sanity checks modified 0 / updated 0 leases and 0 leases were entered into tables
Mar 2 06:46:00 kea-dhcp6 38076 WARN [kea-dhcp6.dhcpsrv.0xf2c9ec12000] DHCPSRV_LEASE_SANITY_FAIL The lease 2001:xxxx:xxxx:xx02::103 with subnet-id 1 failed subnet-id checks (the lease IP address did not belong to a configured subnet).
Mar 2 06:46:00 kea-dhcp6 38076 WARN [kea-dhcp6.dhcpsrv.0xf2c9ec12000] DHCPSRV_LEASE_SANITY_FAIL The lease 2001:xxxx:xxxx:xx02::101 with subnet-id 1 failed subnet-id checks (the lease IP address did not belong to a configured subnet).
Mar 2 06:46:00 kea-dhcp6 38076 WARN [kea-dhcp6.dhcpsrv.0xf2c9ec12000] DHCPSRV_LEASE_SANITY_FAIL The lease 2001:xxxx:xxxx:xx02::105 with subnet-id 1 failed subnet-id checks (the lease IP address did not belong to a configured subnet).
Mar 2 06:46:00 kea-dhcp6 38076 WARN [kea-dhcp6.dhcpsrv.0xf2c9ec12000] DHCPSRV_LEASE_SANITY_FAIL The lease 2001:xxxx:xxxx:xx02::102 with subnet-id 1 failed subnet-id checks (the lease IP address did not belong to a configured subnet).
Mar 2 06:46:00 kea-dhcp6 38076 WARN [kea-dhcp6.dhcpsrv.0xf2c9ec12000] DHCPSRV_LEASE_SANITY_FAIL The lease 2001:xxxx:xxxx:xx02::104 with subnet-id 1 failed subnet-id checks (the lease IP address did not belong to a configured subnet).
Mar 2 06:46:00 kea-dhcp6 38076 WARN [kea-dhcp6.dhcpsrv.0xf2c9ec12000] DHCPSRV_LEASE_SANITY_FAIL The lease 2001:xxxx:xxxx:xx02::100 with subnet-id 1 failed subnet-id checks (the lease IP address did not belong to a configured subnet).
Mar 2 06:46:00 kea-dhcp6 38076 WARN [kea-dhcp6.dhcpsrv.0xf2c9ec12000] DHCPSRV_LEASE_SANITY_FAIL The lease 2001:xxxx:xxxx:xx02::103 with subnet-id 1 failed subnet-id checks (the lease IP address did not belong to a configured subnet).
4

This is beyond me, but I think that your ISP is abusing SLAAC. I don’t think that there’s a clean way to do what you’re looking for. It might be possible to hack something together with a command line script.