How can i request a ipv6 prefix?

kasimir · July 10, 2020, 10:25pm

How can i request a ipv6 prefix from the Router to delegate for the internal Lan?
The PC is assigned an IPv6 on the external interface, but how do I get an IPv6 prefix for the internal interface?
According to my ISP, the router should be able to prefix delegation.

For the network configuration i use wicked.

Thanks for helping

tsu2 · July 10, 2020, 10:48pm

When you connect to a network, a number of automatic network configurations are performed, and a few relate to IPv6 configuration (and auto configuration).

One is Steless Address Autoconfguration (SLAAC).
This means that every device automatically generates an IPv6 address based on the network prefix obtained from the router or other devices in the network.
If your ISP wishes to do so when you were on the outside of your network, DHCP may be used to assign another address which can be used.

In fact, the last time I looked at my machine, it had approximately 4 different IPv6 addresses for different reasons.
Any of the addresses can be used.

You can read up more on SLAAC for yourself,
And perform the following to display all your network interfaces and addresses assigned to each of them

ip addr

Probably easiest way to identify your network prefix is to compare your IPvv6 addresses to addresses of other devices on your network.

TSU

kasimir · July 10, 2020, 11:08pm

Thx tsu2,

my problem is i don’t have IPv6 in the internal Lan.
My structure is as follows:
Router (from ISP) ------ (eth1) PC (br0) ----- internal Network

At the eth1 interface I have Global Unicast adresses. At br0 I have only Unique Local Unicast adresse.
For the br0 I need now a seperate prefix from the Route.

How do I get it?

tsu2 · July 11, 2020, 5:52am

You should first determine if your Gateway router can be configured to forward IPv6.
If not and you <really> want an IPv6 address that works from behind your Gateway router, then you’ll need a tunnel broker.
AFAIK they’re all free.

https://www.google.com/search?q=ipv6+tunnel+brokers

Or, go back to your previous configuration which is to place your machine in front of your Router and if you want this machine to communicate with other machines in your network, will have to architect how that works (many possible solutions depending on actual situation and need).

TSU

arvidjaar · July 11, 2020, 8:05am

The first step is to find out whether your Router can delegate prefix in the first place.

IPv6 prefix delegation is designed to be used by your ISP router. I.e. your router (requesting router per standard) requests prefixes from your ISP, and then distributes them downstream (i.e. to your PC on your diagram) using normal RA mechanism. That is likely what your ISP means. Are you sure your Router is capable to function as prefix delegating router (quoting standard again) subdividing further prefix it gets?

Assuming it is, the simplest way would be to use NetworkManager on PC; it supports prefix delegation via “ipv6.method=shared” address configuration on downstream interface.

kasimir · July 11, 2020, 10:51am

Yes, according to the provider of which the router is, it should work.
I’m supposed to get a / 56 prefix. End devices on the router get a / 64 prefix. Routers behind the ISP router should be able to receive prefixes e.g. /62 or /60.

Work NetworkManager headless too? Thought NetworkManager only works in the desktop, that’s why I used Wicked.

arvidjaar · July 11, 2020, 12:29pm

Yes, of course.

Thought NetworkManager only works in the desktop, that’s why I used Wicked.

NetworkManger is server that manages interfaces according to defined connection profiles. Desktop component allows you to edit connections and request activation of specific connection profile on specific interface, but actual job is done by server. To manage connections (and NetworkManager in general) without GUI you can use nmcli or nmtui.

kasimir · July 11, 2020, 12:48pm

Ok, that was new to me. I’ll give it a try.
Many thanks

arvidjaar · July 11, 2020, 3:28pm

Out of curiosity, what router is it (manufacturer, model)? Do you have link to user interface documentation?

kasimir · July 11, 2020, 9:02pm

The Route is a Connect Box from my ISP Vodafone. Here is the link to the user guide, but there is no Prefix Delegation in it:
https://www.unitymedia.de/content/dam/dcomm-unitymedia-de/hilfe---service/pdf/Connect/Connect-Box-Interaktives-Benutzerhandbuch.pdf

I have only one statement from the ISP after a request for prefix delegation

Theoretisch bekommt die Connect Box von WAN Seite eine IP-Adresse für sich selbst. Dann fordert sie ein Präfix an, welches auf diese Adresse geroutet wird. Beispielsweise würde auf die Adresse ::1300:0:0:0:1 das Präfix ::4200:0:0:0:0/56 geroutet – man sieht, dass zwischen den beiden kein Zusammenhang besteht. Die Connect Box nimmt jetzt das zugeteilte Präfix und teilt es auf – sie benötigt ein /64 für ihre LAN-Seite, z.B. ::4200:0:0:0:0/64 – das heißt, alle Clients direkt an der Connect Box können eine Adresse in diesem Bereich bekommen. Man kann aber aus diesem LAN-Bereich keine weitere Präfixe verteilen, weil das Netz bereits die minimale Größe für ein Ethernet Interface erreicht hat. Daher stellt die Connectbox aus dem übrigen Bereich Ihres eigenen Präfixes Subnetze bereit, welche für Prefix-Delegation verwendet werden können. Beispielsweise könnte ein Router im LAN der Connectbox die Adresse ::4200:0:0:0:1 bekommen und das Präfix ::4280:0:0:0:0/62. Der nächste Router mit der Adresse ::4200:0:0:0:2 bekommt möglicherweise das Präfix ::42A0:0:0:0:0/60. In jedem Fall sind die Präfixe unterschiedlich voneinander und unterschiedlich vom LAN-Präfix der Connectbox. Falls Du weitere Fragen hast, melde Dich gern jederzeit wieder bei uns. Ich wünsche Dir einen angenehmen Tag.

I didn’t get any further with the NetworkManger and found that some things didn’t work properly in this constellation. (DNS, Firewalld, …)
Will ask my provider again if this router really supports prefix delegation.

Maybe someone has an idea how I could check if the router distributes prefixes?

arvidjaar · July 12, 2020, 7:51am

a) tcpdump/wireshark/tshark
b) you could try to request prefix explicitly:

bor@bor-Latitude-E5450:~$ sudo dhclient -6 -P -d -v --no-pid  wlan0
Internet Systems Consortium DHCP Client 4.3.5
Copyright 2004-2016 Internet Systems Consortium.
All rights reserved.
For info, please visit https://www.isc.org/software/dhcp/


Listening on Socket/wlan0
Sending on   Socket/wlan0
Created duid "\000\001\000\001&\235`\264\\\340\305'\307p".
PRC: Soliciting for leases (INIT).
XMT: Forming Solicit, 0 ms elapsed.
XMT:  X-- IA_PD c5:27:c7:70
XMT:  | X-- Request renew in  +3600
XMT:  | X-- Request rebind in +5400
XMT: Solicit on wlan0, interval 1080ms.
XMT: Forming Solicit, 1080 ms elapsed.
XMT:  X-- IA_PD c5:27:c7:70
XMT:  | X-- Request renew in  +3600
XMT:  | X-- Request rebind in +5400
XMT: Solicit on wlan0, interval 2070ms.
XMT: Forming Solicit, 3150 ms elapsed.
XMT:  X-- IA_PD c5:27:c7:70
XMT:  | X-- Request renew in  +3600
XMT:  | X-- Request rebind in +5400
XMT: Solicit on wlan0, interval 4010ms.

See if you get any response (I do not, my ISP router gets single /64 prefix from ISP).

dcurtisfra · July 12, 2020, 2:44pm

Oh yes, there is – Page 24 – DHCPv6 Server – Stateful or Stateless – default: Stateless – start address: 2a02:908:f519:d180::/64 …

Did you, by chance, choose “Stateful”?

Possibly not a good idea – the resulting load on your Router will be rather more than that, which will be the case with the choice of “Stateless” …
By the way, simply let your Router be the DHCP server for your LAN – household routers supplied by (German) ISPs only generate private IP addresses for your household LAN/WLAN – die Bundesnetzagentur will es nicht anders haben …

And, AFAIK, the DSL link from from your residence to Vodafone is also private – to Vodafone – because it also carries your VoIP telephony – once again the Bundesnetzagentur …

If you wish to inspect what’s going on, use <https://www.iplocation.net> – it will first indicate your Router’s IPv4 address as seen by the world, probably at a location you didn’t expect at all «the physical location of Vodafone’s Internet Gateway» – take a look into your Router – you’ll find the IPv6 address Vodafone assigned to your Router – then drop that IPv6 address into iplocation.net – probably yet another unexpected location …

BTW, Vodafone Kabel suggest that you use the following URLs to determine your Router’s IP address:
<http://www.ip-adresse-ermitteln.de/>
<https://www.wieistmeineip.de/> – indicates both your Router’s IPv6 address and the IPv4 address …
<https://meine-aktuelle-ip.vergleich.org/>

The first believes that, I’m in Dortmund, the third believes that, I’m in Munich – both are wrong – on the other hand, my ISP isn’t Vodafone …

kasimir · July 12, 2020, 3:14pm

localhost:~ # dhclient -6 -P -d -v --no-pid eth0
Internet Systems Consortium DHCP Client 4.3.6-P1
Copyright 2004-2018 Internet Systems Consortium.
All rights reserved.
For info, please visit https://www.isc.org/software/dhcp/

Listening on Socket/eth0
Sending on   Socket/eth0
Created duid "\000\001\000\001&\235\300x\334\2462\001\253\030".
PRC: Soliciting for leases (INIT).
XMT: Forming Solicit, 0 ms elapsed.
XMT:  X-- IA_PD 32:01:ab:18
XMT:  | X-- Request renew in  +3600
XMT:  | X-- Request rebind in +5400
XMT: Solicit on eth0, interval 1050ms.
RCV: Advertise message on eth0 from fe80::3a43:7dff:fe15:8c75.
RCV:  X-- Preference 0.
RCV:  X-- IA_PD 32:01:ab:18
RCV:  | X-- starts 1594557433
RCV:  | X-- t1 - renew  +3600
RCV:  | X-- t2 - rebind +5400
RCV:  | X-- [Options]
RCV:  | !-- Status code of no prefix, IA_PD discarded.
RCV:  X-- Server ID: 00:01:00:01:26:9c:b9:e7:38:43:7d:07:ac:24
PRC: Lease failed to satisfy.
XMT: Forming Solicit, 1050 ms elapsed.
XMT:  X-- IA_PD 32:01:ab:18
XMT:  | X-- Request renew in  +3600
XMT:  | X-- Request rebind in +5400
XMT: Solicit on eth0, interval 2160ms.
RCV: Advertise message on eth0 from fe80::3a43:7dff:fe15:8c75.
RCV:  X-- Preference 0.
RCV:  X-- IA_PD 32:01:ab:18
RCV:  | X-- starts 1594557434
RCV:  | X-- t1 - renew  +3600
RCV:  | X-- t2 - rebind +5400
RCV:  | X-- [Options]
RCV:  | !-- Status code of no prefix, IA_PD discarded.
RCV:  X-- Server ID: 00:01:00:01:26:9c:b9:e7:38:43:7d:07:ac:24
PRC: Lease failed to satisfy.

Looks like I’m not getting a prefix. An inquiry with my ISP is already running.

No, it is set to “Stateless”.

I have a dual stack connection, i.e. a public IPv4 and IPv6 address (IPv4: 82.212.X.Xand IPv6: 2a02:8071: X : X :…)

arvidjaar · July 12, 2020, 4:47pm

kasimir:

RCV: Advertise message on eth0 from fe80::3a43:7dff:fe15:8c75.
RCV:  X-- Preference 0.
RCV:  X-- IA_PD 32:01:ab:18
RCV:  | X-- starts 1594557433
RCV:  | X-- t1 - renew  +3600
RCV:  | X-- t2 - rebind +5400
RCV:  | X-- [Options]
RCV:  | !-- Status code of no prefix, IA_PD discarded.
RCV:  X-- Server ID: 00:01:00:01:26:9c:b9:e7:38:43:7d:07:ac:24
PRC: Lease failed to satisfy./code]

Well, it looks better than in my case - at least your DHCPv6 server actually understands and responds to PD request. There are quite a lot of discussions in Internet about PD with your router (both Vodafone and other providers). It looks like your router has severe limitations - several threads suggest that it is capable of delegating exactly one /60 prefix and fails if anything else is requested.

Unfortunately dhclient is pretty limited in this regard. You may try to manually run dhcpcd which has much better support and allows requesting specific prefix length.

Another threads say that PD stopped working since beginning of this year unless you have extra agreement (and pay extra money).

I would suggest asking on your ISP forums as well.

dcurtisfra · July 13, 2020, 10:27am

@kasimir:

Taking the information from my Laptop and my (German) ISP – another one – the “blue” one – the DSL Router is an AVM FRITZ!Box 7490 – my Desktop uses wicked and therefore, dhclient is blocked …
I do not have a fixed public IP address, my contract does not include a dual stack clause and, the DSL also carries my VoIP telephone traffic …


IPv6-Adresse: 2001:16b8:2702:6a49:5e49:xxxx:xxxx:xxxx, Gültigkeit: 259000/172600s,
IPv6-Präfix: 2001:16b8:2d8a:xxxx::/56, Gültigkeit: 240848/154448s


 # dhclient -6 -P -d -v --no-pid  wlan1
Internet Systems Consortium DHCP Client 4.3.6-P1
Copyright 2004-2018 Internet Systems Consortium.
All rights reserved.
For info, please visit https://www.isc.org/software/dhcp/

Listening on Socket/wlan1
Sending on   Socket/wlan1
Created duid "\000\001\000\001&\236\323\021\244\3330\327\361`".
PRC: Soliciting for leases (INIT).
XMT: Forming Solicit, 0 ms elapsed.
XMT:  X-- IA_PD 30:d7:f1:60
XMT:  | X-- Request renew in  +3600
XMT:  | X-- Request rebind in +5400
XMT: Solicit on wlan1, interval 1070ms.
RCV: Advertise message on wlan1 from fe80::5e49:xxxx:xxxx:xxxx.
RCV:  X-- Server ID: 00:03:00:01:5c:49:79:dc:e1:aa
PRC: Lease failed to satisfy.
XMT: Forming Solicit, 1070 ms elapsed.
XMT:  X-- IA_PD 30:d7:f1:60
XMT:  | X-- Request renew in  +3600
XMT:  | X-- Request rebind in +5400
XMT: Solicit on wlan1, interval 2170ms.
RCV: Advertise message on wlan1 from fe80::5e49:xxxx:xxxx:xxxx.
RCV:  X-- Server ID: 00:03:00:01:5c:49:79:dc:e1:aa
PRC: Lease failed to satisfy.
XMT: Forming Solicit, 3240 ms elapsed.
XMT:  X-- IA_PD 30:d7:f1:60
XMT:  | X-- Request renew in  +3600
XMT:  | X-- Request rebind in +5400
XMT: Solicit on wlan1, interval 4390ms.
RCV: Advertise message on wlan1 from fe80::5e49:xxxx:xxxx:xxxx.
RCV:  X-- Server ID: 00:03:00:01:5c:49:79:dc:e1:aa
PRC: Lease failed to satisfy.
XMT: Forming Solicit, 7630 ms elapsed.
XMT:  X-- IA_PD 30:d7:f1:60
XMT:  | X-- Request renew in  +3600
XMT:  | X-- Request rebind in +5400
XMT: Solicit on wlan1, interval 8920ms.
RCV: Advertise message on wlan1 from fe80::5e49:xxxx:xxxx:xxxx.
RCV:  X-- Server ID: 00:03:00:01:5c:49:79:dc:e1:aa
PRC: Lease failed to satisfy.
XMT: Forming Solicit, 16560 ms elapsed.
XMT:  X-- IA_PD 30:d7:f1:60
XMT:  | X-- Request renew in  +3600
XMT:  | X-- Request rebind in +5400
XMT: Solicit on wlan1, interval 17260ms.
RCV: Advertise message on wlan1 from fe80::5e49:xxxx:xxxx:xxxx.
RCV:  X-- Server ID: 00:03:00:01:5c:49:79:dc:e1:aa
PRC: Lease failed to satisfy.
^C
 #


 # dhclient -6 -P -d -v --no-pid eth0
Internet Systems Consortium DHCP Client 4.3.6-P1
Copyright 2004-2018 Internet Systems Consortium.
All rights reserved.
For info, please visit https://www.isc.org/software/dhcp/

Listening on Socket/eth0
Sending on   Socket/eth0
PRC: Soliciting for leases (INIT).
XMT: Forming Solicit, 0 ms elapsed.
XMT:  X-- IA_PD 06:2e:c5:c2
XMT:  | X-- Request renew in  +3600
XMT:  | X-- Request rebind in +5400
XMT: Solicit on eth0, interval 1010ms.
RCV: Advertise message on eth0 from fe80::5e49:xxxx:xxxx:xxxx.
RCV:  X-- Server ID: 00:03:00:01:5c:49:79:dc:e1:aa
PRC: Lease failed to satisfy.
XMT: Forming Solicit, 1010 ms elapsed.
XMT:  X-- IA_PD 06:2e:c5:c2
XMT:  | X-- Request renew in  +3600
XMT:  | X-- Request rebind in +5400
XMT: Solicit on eth0, interval 1960ms.
RCV: Advertise message on eth0 from fe80::5e49:xxxx:xxxx:xxxx.
RCV:  X-- Server ID: 00:03:00:01:5c:49:79:dc:e1:aa
PRC: Lease failed to satisfy.
XMT: Forming Solicit, 2970 ms elapsed.
XMT:  X-- IA_PD 06:2e:c5:c2
XMT:  | X-- Request renew in  +3600
XMT:  | X-- Request rebind in +5400
XMT: Solicit on eth0, interval 3780ms.
RCV: Advertise message on eth0 from fe80::5e49:xxxx:xxxx:xxxx.
RCV:  X-- Server ID: 00:03:00:01:5c:49:79:dc:e1:aa
PRC: Lease failed to satisfy.
XMT: Forming Solicit, 6750 ms elapsed.
XMT:  X-- IA_PD 06:2e:c5:c2
XMT:  | X-- Request renew in  +3600
XMT:  | X-- Request rebind in +5400
XMT: Solicit on eth0, interval 7390ms.
RCV: Advertise message on eth0 from fe80::5e49:xxxx:xxxx:xxxx.
RCV:  X-- Server ID: 00:03:00:01:5c:49:79:dc:e1:aa
PRC: Lease failed to satisfy.
^C
 #

arvidjaar · July 13, 2020, 8:13pm

FTR, here what I get when server actually offers prefixes (values are entirely fake), Three times -P was by accident:

bor@10:~> sudo /sbin/dhclient -6 -P -d -v -P -P -lf /tmp/dhcp.lease --no-pid eth1
[sudo] password for root: 
Internet Systems Consortium DHCP Client 4.3.6-P1
Copyright 2004-2018 Internet Systems Consortium.
All rights reserved.
For info, please visit https://www.isc.org/software/dhcp/


Listening on Socket/eth1
Sending on   Socket/eth1
Created duid "\000\001\000\001&\237^\220\336\255\276\357\001\003".
PRC: Soliciting for leases (INIT).
XMT: Forming Solicit, 0 ms elapsed.
XMT:  X-- IA_PD be:ef:01:03
XMT:  | X-- Request renew in  +3600
XMT:  | X-- Request rebind in +5400
XMT:  X-- IA_PD be:ef:01:04
XMT:  | X-- Request renew in  +3600
XMT:  | X-- Request rebind in +5400
XMT:  X-- IA_PD be:ef:01:05
XMT:  | X-- Request renew in  +3600
XMT:  | X-- Request rebind in +5400
XMT: Solicit on eth1, interval 1090ms.
RCV: Advertise message on eth1 from fe80::9105:f436:4589:87bc.
RCV:  X-- IA_PD be:ef:01:03
RCV:  | X-- starts 1594663441
RCV:  | X-- t1 - renew  +0
RCV:  | X-- t2 - rebind +0
RCV:  | X-- [Options]
RCV:  | | X-- IAPREFIX 2001:db8:1234:b000::/56
RCV:  | | | X-- Preferred lifetime 27000.
RCV:  | | | X-- Max lifetime 43200.
RCV:  X-- IA_PD be:ef:01:04
RCV:  | X-- starts 1594663441
RCV:  | X-- t1 - renew  +0
RCV:  | X-- t2 - rebind +0
RCV:  | X-- [Options]
RCV:  | | X-- IAPREFIX 2001:db8:1234:b000::/56
RCV:  | | | X-- Preferred lifetime 27000.
RCV:  | | | X-- Max lifetime 43200.
RCV:  X-- IA_PD be:ef:01:05
RCV:  | X-- starts 1594663441
RCV:  | X-- t1 - renew  +0
RCV:  | X-- t2 - rebind +0
RCV:  | X-- [Options]
RCV:  | | X-- IAPREFIX 2001:db8:1234:b000::/56
RCV:  | | | X-- Preferred lifetime 27000.
RCV:  | | | X-- Max lifetime 43200.
RCV:  X-- Server ID: 00:01:00:01:26:9f:5d:aa:de:ad:be:ef:01:01
RCV:  Advertisement recorded.
PRC: Selecting best advertised lease.
PRC: Considering best lease.
PRC:  X-- Initial candidate 00:01:00:01:26:9f:5d:aa:de:ad:be:ef:01:01 (s: 30302, p: 0).
XMT: Forming Request, 0 ms elapsed.
XMT:  X-- IA_PD be:ef:01:03
XMT:  | X-- Requested renew  +3600
XMT:  | X-- Requested rebind +5400
XMT:  | | X-- IAPREFIX 2001:db8:1234:b000::/56
XMT:  | | | X-- Preferred lifetime +7200
XMT:  | | | X-- Max lifetime +7500
XMT:  V IA_PD appended.
XMT:  X-- IA_PD be:ef:01:04
XMT:  | X-- Requested renew  +3600
XMT:  | X-- Requested rebind +5400
XMT:  | | X-- IAPREFIX 2001:db8:1234:b000::/56
XMT:  | | | X-- Preferred lifetime +7200
XMT:  | | | X-- Max lifetime +7500
XMT:  V IA_PD appended.
XMT:  X-- IA_PD be:ef:01:05
XMT:  | X-- Requested renew  +3600
XMT:  | X-- Requested rebind +5400
XMT:  | | X-- IAPREFIX 2001:db8:1234:b000::/56
XMT:  | | | X-- Preferred lifetime +7200
XMT:  | | | X-- Max lifetime +7500
XMT:  V IA_PD appended.
XMT: Request on eth1, interval 980ms.
RCV: Reply message on eth1 from fe80::9105:f436:4589:87bc.
RCV:  X-- IA_PD be:ef:01:03
RCV:  | X-- starts 1594663442
RCV:  | X-- t1 - renew  +0
RCV:  | X-- t2 - rebind +0
RCV:  | X-- [Options]
RCV:  | | X-- IAPREFIX 2001:db8:1234:b000::/56
RCV:  | | | X-- Preferred lifetime 7200.
RCV:  | | | X-- Max lifetime 7500.
RCV:  X-- IA_PD be:ef:01:04
RCV:  | X-- starts 1594663442
RCV:  | X-- t1 - renew  +0
RCV:  | X-- t2 - rebind +0
RCV:  | X-- [Options]
RCV:  | | X-- IAPREFIX 2001:db8:1234:a200::/56
RCV:  | | | X-- Preferred lifetime 7200.
RCV:  | | | X-- Max lifetime 7500.
RCV:  X-- IA_PD be:ef:01:05
RCV:  | X-- starts 1594663442
RCV:  | X-- t1 - renew  +0
RCV:  | X-- t2 - rebind +0
RCV:  | X-- [Options]
RCV:  | | X-- IAPREFIX 2001:db8:1234:a700::/56
RCV:  | | | X-- Preferred lifetime 7200.
RCV:  | | | X-- Max lifetime 7500.
RCV:  X-- Server ID: 00:01:00:01:26:9f:5d:aa:de:ad:be:ef:01:01
PRC: Bound to lease 00:01:00:01:26:9f:5d:aa:de:ad:be:ef:01:01.
PRC: Renewal event scheduled in 3749 seconds, to run for 1875 seconds.
PRC: Depreference scheduled in 7199 seconds.
PRC: Expiration scheduled in 7499 seconds.
^C
bor@10:~>

arvidjaar · July 13, 2020, 8:24pm

And you actually configured your FRITZ!Box to perform prefix delegation? https://www.o-schroeder.de/sysadmin/DSLite/fritzbox.php

tsu2 · July 13, 2020, 8:49pm

Let me ask an open question…

Why ask for a prefix at all?

You aren’t a major ISP, so you don’t need a registered block of addresses from APNIC.
The way IPv6 works, as long as you use an address that uses the same prefix as your gateway router, you are routable to the Internet (and vice versa).
There is no such thing as IPv6 NAT (or at least, it’s highly discouraged because there are many reason not to configure and hardly any good reason to deploy).
If you want a larger bit prefix, why not just grab some unused part? It’s easy to test whether those addresses are already used and as vast as the address space is, it’s unlikely that anyone would notice what you’ve done. Unless you were actually stepping on someone else, I can’t imagine an ISP would care whether you do this.
IPv6 DHCP might be implemented only for management purposes so that new hosts might be grouped into contiguous addresses. But, it’s not required to acquire a working IP address like in IPv4. The self-generated IPv6 address is considered to be perfectly usable unlike IPv4. And IPv6 DHCP ordinarily grants you a very large block of usable addresses, ie 64 bits. An ISP would have to be incredibly miserly to do otherwise.

As an ISP, you might have an interest in this topic.
As a customer/User, I’m having a bit harder time seeing a use case.

This is more or less consistent with discussions and presentations I’ve seen, but maybe I just haven’t spoken to the right people…

TSU

dcurtisfra · July 14, 2020, 6:02pm

Thanks for the tip – No – But, the investigation into the IPv6 capabilities of the AVM router was quite interesting and informative …

Oliver Schröder seems to be very well informed and active in this area.
Yet another no – I don’t have an additional router on my LAN – the AVM router does everything I need …

[HR][/HR]Which leaves the question, as Tsu pointed out, why the extra effort?

If we take the Schröder case, he doesn’t want anyone, not even AVM, to define how his private LAN shall be configured.

He does however, admit that, the AVM router is a little bit too limited for his needs – if that router were to be a little bit more complex then …
Possibly …

I suspect that, provided that, the folks who feel they need IPv6 prefix delegation can define and plan their private LAN as Schröder did, then, the effort will be worth while.
If however, the definition and planning of everything that needs to be done, is only executed half heartedly then, the exercise will possibly be doomed to failure …

kasimir · July 17, 2020, 4:56pm

The answer from my ISP was that he can no longer help me and sent me the following link:
https://community.upc.ch/t5/Connect-Box/Technische-Details-zu-IPv6-mit-Prefix-Delegation/td-p/131817