ISC DHCP Users

cannot renew IPV6 address

Classic

List

Threaded

12 messages Options

Jean-Max Reymond

cannot renew IPV6 address

Hi,
I am running dhclient 4.3.5 (from isc site) on ubuntu 16.04 LTS
When starting my server, all is OK, I have an IPV6 address, I can ping,
ssh, etc.
After 12 hours, the interface is down and I cannot obtain a new IPV6 adress.

# cat /etc/dhcp/dhclient6.conf
interface "eno1" {
send dhcp6.client-id 00:03:00:01:73:41:e0:29:71:a3;
}

$ /usr/local/sbin/dhclient -cf /etc/dhcp/dhclient6.conf -6 -P -v eno1
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/eno1
Sending on Socket/eno1
PRC: Confirming active lease (INIT-REBOOT).
XMT: Forming Rebind, 0 ms elapsed.
XMT: X-- IA_PD 35:07:ad:18
XMT: | X-- Requested renew +3600
XMT: | X-- Requested rebind +5400
XMT: | | X-- IAPREFIX 2001:bc8:344f:200::/56
XMT: | | | X-- Preferred lifetime +7200
XMT: | | | X-- Max lifetime +7500
XMT: V IA_PD appended.
XMT: Rebind on eno1, interval 1030ms.
RCV: Reply message on eno1 from fe80::fe5b:39ff:fe72:9fff.
RCV: X-- Preference 255.
RCV: X-- IA_PD 35:07:ad:18
RCV: | X-- starts 1485444775
RCV: | X-- t1 - renew +43200
RCV: | X-- t2 - rebind +172800
RCV: | X-- [Options]
RCV: | | X-- IAPREFIX 2001:bc8:344f:200::/56
RCV: | | | X-- Preferred lifetime 7200.
RCV: | | | X-- Max lifetime 43200.
RCV: X-- Server ID: 00:01:00:01:1b:ac:bc:2d:10:60:4b:9b:0a:f4
PRC: Bound to lease 00:01:00:01:1b:ac:bc:2d:10:60:4b:9b:0a:f4.

and

# ifconfig eno1
eno1 Link encap:Ethernet HWaddr 54:9f:35:07:ad:18
inet addr:62.210.247.117 Bcast:62.210.247.255
Mask:255.255.255.0
inet6 addr: fe80::569f:35ff:fe07:ad18/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:25519061 errors:0 dropped:0 overruns:0 frame:0
TX packets:52829191 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:1920059401 (1.9 GB) TX bytes:79910066020 (79.9 GB)
Interrupt:16

For my ISP, all is good but I have no IPV6 connection.
thanks for your tips,

--
Jean-Max Reymond
CKR Solutions Open Source https://www.ckr-solutions.com
_______________________________________________
dhcp-users mailing list
[hidden email]
https://lists.isc.org/mailman/listinfo/dhcp-users

Simon Hobson

Re: cannot renew IPV6 address

Jean-Max Reymond <[hidden email]> wrote:

> After 12 hours, the interface is down and I cannot obtain a new IPV6 adress.

> $ /usr/local/sbin/dhclient -cf /etc/dhcp/dhclient6.conf -6 -P -v eno1

> ...
> RCV: | | | X-- Max lifetime 43200.

OK, your lease is 12 hours, at the end of the lease you lose the address. Are you leaving the dhcp client running ? Is it sending any renewal requests ? Are you running a firewall that could be blocking DHCP6 ?

The basic troubleshooting at this point is to narrow it down to one of 3 things :

1) Your client isn't attempting to renew

2) Your client is attempting to renew but the server isn't responding

3) Something else - such as server responding but client doesn't accept it

You probably need to run a packet sniffer on the relevant interface and capture DHCP6 packets. That should answer the questions: Is the client trying to renew ? Is the server replying ?

_______________________________________________
dhcp-users mailing list
[hidden email]
https://lists.isc.org/mailman/listinfo/dhcp-users

Brice Abba

Re: cannot renew IPV6 address

In reply to this post by Jean-Max Reymond

Hi Jean,

Ensure the server is running with "ps cmd"
play with this value to test " Max lifetime 43200"
Ensure the router on the link advertise "management config flag"

2017-01-26 19:53 GMT+04:00 Jean-Max Reymond <[hidden email]>:

Hi,
I am running dhclient 4.3.5 (from isc site) on ubuntu 16.04 LTS
When starting my server, all is OK, I have an IPV6 address, I can ping, ssh, etc.
After 12 hours, the interface is down and I cannot obtain a new IPV6 adress.

# cat /etc/dhcp/dhclient6.conf
interface "eno1" {
send dhcp6.client-id 00:03:00:01:73:41:e0:29:71:a3;
}

$ /usr/local/sbin/dhclient -cf /etc/dhcp/dhclient6.conf -6 -P -v eno1
Internet Systems Consortium DHCP Client 4.3.5
Copyright <a href="tel:2004-2016" value="+22520042016" target="_blank">2004-2016 Internet Systems Consortium.
All rights reserved.
For info, please visit https://www.isc.org/software/dhcp/

Listening on Socket/eno1
Sending on Socket/eno1
PRC: Confirming active lease (INIT-REBOOT).
XMT: Forming Rebind, 0 ms elapsed.
XMT: X-- IA_PD 35:07:ad:18
XMT: | X-- Requested renew +3600
XMT: | X-- Requested rebind +5400
XMT: | | X-- IAPREFIX 2001:bc8:344f:200::/56
XMT: | | | X-- Preferred lifetime +7200
XMT: | | | X-- Max lifetime +7500
XMT: V IA_PD appended.
XMT: Rebind on eno1, interval 1030ms.
RCV: Reply message on eno1 from fe80::fe5b:39ff:fe72:9fff.
RCV: X-- Preference 255.
RCV: X-- IA_PD 35:07:ad:18
RCV: | X-- starts 1485444775
RCV: | X-- t1 - renew +43200
RCV: | X-- t2 - rebind +172800
RCV: | X-- [Options]
RCV: | | X-- IAPREFIX 2001:bc8:344f:200::/56
RCV: | | | X-- Preferred lifetime 7200.
RCV: | | | X-- Max lifetime 43200.
RCV: X-- Server ID: 00:01:00:01:1b:ac:bc:2d:10:60:4b:9b:0a:f4
PRC: Bound to lease 00:01:00:01:1b:ac:bc:2d:10:60:4b:9b:0a:f4.

and

# ifconfig eno1
eno1 Link encap:Ethernet HWaddr 54:9f:35:07:ad:18
inet addr:62.210.247.117 Bcast:62.210.247.255 Mask:255.255.255.0
inet6 addr: fe80::569f:35ff:fe07:ad18/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:25519061 errors:0 dropped:0 overruns:0 frame:0
TX packets:52829191 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:1920059401 (1.9 GB) TX bytes:79910066020 (79.9 GB)
Interrupt:16

For my ISP, all is good but I have no IPV6 connection.
thanks for your tips,

--
Jean-Max Reymond
CKR Solutions Open Source https://www.ckr-solutions.com
_______________________________________________
dhcp-users mailing list
[hidden email]
https://lists.isc.org/mailman/listinfo/dhcp-users

Brice ABBA
www.afrinic.net

_______________________________________________
dhcp-users mailing list
[hidden email]
https://lists.isc.org/mailman/listinfo/dhcp-users

Jean-Max Reymond

Re: cannot renew IPV6 address

In reply to this post by Simon Hobson

Le 26/01/2017 à 17:01, Simon Hobson a écrit :

> Jean-Max Reymond <[hidden email]> wrote:
>
>> After 12 hours, the interface is down and I cannot obtain a new IPV6 adress.
>
>> $ /usr/local/sbin/dhclient -cf /etc/dhcp/dhclient6.conf -6 -P -v eno1
>
>> ...
>> RCV: | | | X-- Max lifetime 43200.
>
> OK, your lease is 12 hours, at the end of the lease you lose the address. Are you leaving the dhcp client running ? Is it sending any renewal requests ? Are you running a firewall that could be blocking DHCP6 ?
>

thanks for your fast answer. dhcp client is always running but I cannot
ping6 another server.
I have no messages in /var/log/syslog and no firewall.
At boot, IPV6 is OK.
So I suspect this bug
https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1551351
but after updating with dhcpclient 4.3.5, same issue

> The basic troubleshooting at this point is to narrow it down to one of 3 things :
>
> 1) Your client isn't attempting to renew
>
> 2) Your client is attempting to renew but the server isn't responding
>
> 3) Something else - such as server responding but client doesn't accept it
>
> You probably need to run a packet sniffer on the relevant interface and capture DHCP6 packets. That should answer the questions: Is the client trying to renew ? Is the server replying ?

OK, I suspect answer 1 because I have no traces in /var/log/syslog but
restarting dhclient give answer 2
I start a sniffer client to capture DHCP6 packets

--
Jean-Max Reymond
CKR Solutions Open Source https://www.ckr-solutions.com
_______________________________________________
dhcp-users mailing list
[hidden email]
https://lists.isc.org/mailman/listinfo/dhcp-users

Simon Hobson

Re: cannot renew IPV6 address

In reply to this post by Brice Abba

Brice Abba <[hidden email]> wrote:

> Hi Jean,
>
> • Ensure the server is running with "ps cmd"
> • play with this value to test " Max lifetime 43200"
> • Ensure the router on the link advertise "management config flag"

I read it as the server is the ISP's, so he has no access to check things like that.
Besides, if he is getting an address initially (and I assume, after a reboot), then the server must be running.

_______________________________________________
dhcp-users mailing list
[hidden email]
https://lists.isc.org/mailman/listinfo/dhcp-users

Jean-Max Reymond

Re: cannot renew IPV6 address

Le 26/01/2017 à 17:42, Simon Hobson a écrit :

> Brice Abba <[hidden email]> wrote:
>
>> Hi Jean,
>>
>> • Ensure the server is running with "ps cmd"
>> • play with this value to test " Max lifetime 43200"
>> • Ensure the router on the link advertise "management config flag"
>
> I read it as the server is the ISP's, so he has no access to check things like that.
> Besides, if he is getting an address initially (and I assume, after a reboot), then the server must be running.

yes, that's correct. My ISP gives me an IPV6 adress at boot and reboot

dhclient write a file /var/db/dhclient6.leases

# cat /var/db/dhclient6.leases
default-duid "\000\001\000\001 \033\313$T\2375\007\255\030";
lease6 {
interface "eno1";
ia-pd 35:07:ad:18 {
starts 1485445025;
renew 43200;
rebind 172800;
iaprefix 2001:bc8:344f:200::/56 {
starts 1485445025;
preferred-life 7200;
max-life 43200;
}
}
option dhcp6.client-id 0:3:0:1:73:41:e0:29:71:a3;
option dhcp6.server-id 0:1:0:1:1b:ac:bc:2d:10:60:4b:9b:a:f4;
option dhcp6.name-servers 2001:bc8:401::3,2001:bc8:1::16;
option dhcp6.domain-search "online.net.";
}
lease6 {
interface "eno1";
ia-pd 35:07:ad:18 {
starts 1485445038;
renew 43200;
rebind 172800;
iaprefix 2001:bc8:344f:200::/56 {
starts 1485445038;
preferred-life 7200;
max-life 43200;
}
}
option dhcp6.client-id 0:3:0:1:73:41:e0:29:71:a3;
option dhcp6.server-id 0:1:0:1:1b:ac:bc:2d:10:60:4b:9b:a:f4;
option dhcp6.name-servers 2001:bc8:401::3,2001:bc8:1::16;
option dhcp6.domain-search "online.net.";
}

--
Jean-Max Reymond
CKR Solutions Open Source https://www.ckr-solutions.com
_______________________________________________
dhcp-users mailing list
[hidden email]
https://lists.isc.org/mailman/listinfo/dhcp-users

Jean-Max Reymond

Re: cannot renew IPV6 address

In reply to this post by Jean-Max Reymond

Le 26/01/2017 à 17:13, Jean-Max Reymond a écrit :

> Le 26/01/2017 à 17:01, Simon Hobson a écrit :
>> Jean-Max Reymond <[hidden email]> wrote:
>>
>>> After 12 hours, the interface is down and I cannot obtain a new IPV6
>>> adress.
>>
>>> $ /usr/local/sbin/dhclient -cf /etc/dhcp/dhclient6.conf -6 -P -v eno1
>>
>>> ...
>>> RCV: | | | X-- Max lifetime 43200.
>>
>> OK, your lease is 12 hours, at the end of the lease you lose the
>> address. Are you leaving the dhcp client running ? Is it sending any
>> renewal requests ? Are you running a firewall that could be blocking
>> DHCP6 ?
>>
>
> thanks for your fast answer. dhcp client is always running but I cannot
> ping6 another server.
> I have no messages in /var/log/syslog and no firewall.
> At boot, IPV6 is OK.
> So I suspect this bug
> https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1551351
> but after updating with dhcpclient 4.3.5, same issue
>
>> The basic troubleshooting at this point is to narrow it down to one of
>> 3 things :
>>
>> 1) Your client isn't attempting to renew
>>
>> 2) Your client is attempting to renew but the server isn't responding
>>
>> 3) Something else - such as server responding but client doesn't
>> accept it
>>
>> You probably need to run a packet sniffer on the relevant interface
>> and capture DHCP6 packets. That should answer the questions: Is the
>> client trying to renew ? Is the server replying ?
>
> OK, I suspect answer 1 because I have no traces in /var/log/syslog but
> restarting dhclient give answer 2
> I start a sniffer client to capture DHCP6 packets
>

It seems that dhcp server from my ISP is not answering to my requests

# ip6tables -L
Chain INPUT (policy ACCEPT)
target prot opt source destination

Chain FORWARD (policy ACCEPT)
target prot opt source destination

Chain OUTPUT (policy ACCEPT)
target prot opt source destination

# tcpdump -i eno1 -vv ip6|head -10
tcpdump: listening on eno1, link-type EN10MB (Ethernet), capture size
262144 bytes
19:36:23.877024 IP6 (hlim 1, next-header UDP (17) payload length: 52)
fe80::250:56ff:fe00:d633.dhcpv6-client > ff02::1:2.dhcpv6-server: [udp
sum ok] dhcp6 solicit (xid=f24d5e (client-ID hwaddr/time type 1 time
514053608 000c2983d6d2) (elapsed-time 0) (IA_PD IAID:4 T1:0 T2:0))
19:36:23.882100 IP6 (hlim 1, next-header UDP (17) payload length: 76)
fe80::250:56ff:fe00:d633.dhcpv6-client > ff02::1:2.dhcpv6-server: [udp
sum ok] dhcp6 request (xid=7d8662 (client-ID hwaddr/time type 1 time
514053608 000c2983d6d2) (server-ID hwaddr/time type 1 time 464305197
10604b9b0af4) (elapsed-time 0) (IA_PD IAID:4 T1:0 T2:0 (status-code no
prefixes)))
19:36:24.292983 IP6 (hlim 1, next-header UDP (17) payload length: 52)
fe80::250:56ff:fe00:d633.dhcpv6-client > ff02::1:2.dhcpv6-server: [udp
sum ok] dhcp6 solicit (xid=9cebbf (client-ID hwaddr/time type 1 time
514053608 000c2983d6d2) (elapsed-time 0) (IA_PD IAID:4 T1:0 T2:0))
19:36:24.300359 IP6 (hlim 1, next-header UDP (17) payload length: 76)
fe80::250:56ff:fe00:d633.dhcpv6-client > ff02::1:2.dhcpv6-server: [udp
sum ok] dhcp6 request (xid=41724a (client-ID hwaddr/time type 1 time
514053608 000c2983d6d2) (server-ID hwaddr/time type 1 time 464305197
10604b9b0af4) (elapsed-time 0) (IA_PD IAID:4 T1:0 T2:0 (status-code no
prefixes)))
19:36:24.900604 IP6 (hlim 1, next-header UDP (17) payload length: 52)
fe80::250:56ff:fe00:d633.dhcpv6-client > ff02::1:2.dhcpv6-server: [udp
sum ok] dhcp6 solicit (xid=1f6b95 (client-ID hwaddr/time type 1 time
514053608 000c2983d6d2) (elapsed-time 0) (IA_PD IAID:4 T1:0 T2:0))
19:36:24.905277 IP6 (hlim 1, next-header UDP (17) payload length: 76)
fe80::250:56ff:fe00:d633.dhcpv6-client > ff02::1:2.dhcpv6-server: [udp
sum ok] dhcp6 request (xid=fec410 (client-ID hwaddr/time type 1 time
514053608 000c2983d6d2) (server-ID hwaddr/time type 1 time 464305197
10604b9b0af4) (elapsed-time 0) (IA_PD IAID:4 T1:0 T2:0 (status-code no
prefixes)))
19:36:25.160943 IP6 (hlim 1, next-header UDP (17) payload length: 52)
fe80::250:56ff:fe00:d633.dhcpv6-client > ff02::1:2.dhcpv6-server: [udp
sum ok] dhcp6 solicit (xid=9e3f36 (client-ID hwaddr/time type 1 time
514053608 000c2983d6d2) (elapsed-time 0) (IA_PD IAID:4 T1:0 T2:0))
19:36:25.179613 IP6 (hlim 1, next-header UDP (17) payload length: 76)
fe80::250:56ff:fe00:d633.dhcpv6-client > ff02::1:2.dhcpv6-server: [udp
sum ok] dhcp6 request (xid=502d2a (client-ID hwaddr/time type 1 time
514053608 000c2983d6d2) (server-ID hwaddr/time type 1 time 464305197
10604b9b0af4) (elapsed-time 0) (IA_PD IAID:4 T1:0 T2:0 (status-code no
prefixes)))
19:36:25.756287 IP6 (hlim 1, next-header UDP (17) payload length: 52)
fe80::250:56ff:fe00:d633.dhcpv6-client > ff02::1:2.dhcpv6-server: [udp
sum ok] dhcp6 solicit (xid=416443 (client-ID hwaddr/time type 1 time
514053608 000c2983d6d2) (elapsed-time 0) (IA_PD IAID:4 T1:0 T2:0))
19:36:25.763720 IP6 (hlim 1, next-header UDP (17) payload length: 76)
fe80::250:56ff:fe00:d633.dhcpv6-client > ff02::1:2.dhcpv6-server: [udp
sum ok] dhcp6 request (xid=4ace44 (client-ID hwaddr/time type 1 time
514053608 000c2983d6d2) (server-ID hwaddr/time type 1 time 464305197
10604b9b0af4) (elapsed-time 0) (IA_PD IAID:4 T1:0 T2:0 (status-code no
prefixes)))
28 packets captured
28 packets received by filter
0 packets dropped by kernel

--
Jean-Max Reymond
CKR Solutions Open Source https://www.ckr-solutions.com
_______________________________________________
dhcp-users mailing list
[hidden email]
https://lists.isc.org/mailman/listinfo/dhcp-users

Simon Hobson

Re: cannot renew IPV6 address

Jean-Max Reymond <[hidden email]> wrote:

> It seems that dhcp server from my ISP is not answering to my requests

Or it could be a problem with a relay agent. Either way, if there's no answer from the ISP then you need to take that up with them.

I suspect that so far, IPv6 is at the "most users would never notice" stage for most ISPs and an outage like this won't result in any support calls to them. Thus they'll not know there's a problem to fix until you call them.

_______________________________________________
dhcp-users mailing list
[hidden email]
https://lists.isc.org/mailman/listinfo/dhcp-users

Sten Carlsen

Re: cannot renew IPV6 address

On 27/01/2017 13:02, Simon Hobson wrote:

Jean-Max Reymond [hidden email] wrote:

It seems that dhcp server from my ISP is not answering to my requests

Or it could be a problem with a relay agent. Either way, if there's no answer from the ISP then you need to take that up with them.

This makes me think, what is the real difference between getting an IP first time and renewing it? In IP4 getting an IP is broadcast, renewing is going directly, not passing relays.
I don't off the top of my head remember for IP6, but two situations could be relevant:
- renewal and initial requests go different paths and only one is functional.
- renewal and initial request have to go same way but ISP expects them to be separate so the correct path is not implemented.


I suspect that so far, IPv6 is at the "most users would never notice" stage for most ISPs and an outage like this won't result in any support calls to them. Thus they'll not know there's a problem to fix until you call them.

_______________________________________________
dhcp-users mailing list
[hidden email]
https://lists.isc.org/mailman/listinfo/dhcp-users

-- 
Best regards

Sten Carlsen

No improvements come from shouting:

       "MALE BOVINE MANURE!!!"

_______________________________________________
dhcp-users mailing list
[hidden email]
https://lists.isc.org/mailman/listinfo/dhcp-users

Philippe Clérié

Re: cannot renew IPV6 address

In reply to this post by Jean-Max Reymond

On 01/26/2017 11:54 AM, Jean-Max Reymond wrote:

> Le 26/01/2017 à 17:42, Simon Hobson a écrit :
>> Brice Abba <[hidden email]> wrote:
>>
>>> Hi Jean,
>>>
>>> • Ensure the server is running with "ps cmd"
>>> • play with this value to test " Max lifetime 43200"
>>> • Ensure the router on the link advertise "management config flag"
>>
>> I read it as the server is the ISP's, so he has no access to check
>> things like that.
>> Besides, if he is getting an address initially (and I assume, after a
>> reboot), then the server must be running.
>
> yes, that's correct. My ISP gives me an IPV6 adress at boot and reboot
>
> dhclient write a file /var/db/dhclient6.leases
>
> # cat /var/db/dhclient6.leases
> default-duid "\000\001\000\001 \033\313$T\2375\007\255\030";
> lease6 {
> interface "eno1";
> ia-pd 35:07:ad:18 {
> starts 1485445025;
> renew 43200;
> rebind 172800;
> iaprefix 2001:bc8:344f:200::/56 {
> starts 1485445025;
> preferred-life 7200;
> max-life 43200;
> }
> }
> option dhcp6.client-id 0:3:0:1:73:41:e0:29:71:a3;
> option dhcp6.server-id 0:1:0:1:1b:ac:bc:2d:10:60:4b:9b:a:f4;
> option dhcp6.name-servers 2001:bc8:401::3,2001:bc8:1::16;
> option dhcp6.domain-search "online.net.";
> }
> lease6 {
> interface "eno1";
> ia-pd 35:07:ad:18 {
> starts 1485445038;
> renew 43200;
> rebind 172800;
> iaprefix 2001:bc8:344f:200::/56 {
> starts 1485445038;
> preferred-life 7200;
> max-life 43200;
> }
> }
> option dhcp6.client-id 0:3:0:1:73:41:e0:29:71:a3;
> option dhcp6.server-id 0:1:0:1:1b:ac:bc:2d:10:60:4b:9b:a:f4;
> option dhcp6.name-servers 2001:bc8:401::3,2001:bc8:1::16;
> option dhcp6.domain-search "online.net.";
> }
>
>

Is it possible that you're getting an entire /56 block and not just a
single address? In which case you can pretty much assign yourself any
address you wish on that interface as long as you're within that block.

I do know that Comcast does assign at least a /64. I've also heard /60.
But 64 is what I have seen.

--
Philippe

------
The trouble with common sense it that it is so uncommon.
<Anonymous>
_______________________________________________
dhcp-users mailing list
[hidden email]
https://lists.isc.org/mailman/listinfo/dhcp-users

Bjørn Mork

Re: cannot renew IPV6 address

In reply to this post by Jean-Max Reymond

Jean-Max Reymond <[hidden email]> writes:

> # tcpdump -i eno1 -vv ip6|head -10
> tcpdump: listening on eno1, link-type EN10MB (Ethernet), capture size
> 262144 bytes
> 19:36:23.877024 IP6 (hlim 1, next-header UDP (17) payload length: 52)
> fe80::250:56ff:fe00:d633.dhcpv6-client > ff02::1:2.dhcpv6-server: [udp
> sum ok] dhcp6 solicit (xid=f24d5e (client-ID hwaddr/time type 1 time
> 514053608 000c2983d6d2) (elapsed-time 0) (IA_PD IAID:4 T1:0 T2:0))

and

> # cat /var/db/dhclient6.leases
> default-duid "\000\001\000\001 \033\313$T\2375\007\255\030";
> lease6 {
> interface "eno1";
> ia-pd 35:07:ad:18 {
> starts 1485445025;
> renew 43200;
> rebind 172800;
> iaprefix 2001:bc8:344f:200::/56 {
> starts 1485445025;
> preferred-life 7200;
> max-life 43200;
> }
> }
> option dhcp6.client-id 0:3:0:1:73:41:e0:29:71:a3;
> option dhcp6.server-id 0:1:0:1:1b:ac:bc:2d:10:60:4b:9b:a:f4;
> option dhcp6.name-servers 2001:bc8:401::3,2001:bc8:1::16;
> option dhcp6.domain-search "online.net.";
> }

The tcpdump output is hard to read (use tshark -V instead...), but IIUC
you show us two very different requests here. The client DUID and IA_PD
IAID are both different. Your ISP might have a one prefix per circuit
limit, causing requests from any but the first client on a circuit to be
silently ignored.

And you have also not shown us how you use the allocated prefix, making
it impossible to know if the error is in the DHCP transaction or in your
local address assignment policy. Receiving an IA_PD prefix will not
magically provide you with any IPv6 connectivity. You'll need to split
it up and assign it to interfaces. And you will need to set up routing
as well, possibly using a default route from an RA.

Bjørn
_______________________________________________
dhcp-users mailing list
[hidden email]
https://lists.isc.org/mailman/listinfo/dhcp-users

Jean-Max Reymond

Re: cannot renew IPV6 address

In reply to this post by Philippe Clérié

Le 28/01/2017 à 01:21, Philippe Clérié a écrit :

> On 01/26/2017 11:54 AM, Jean-Max Reymond wrote:
>> Le 26/01/2017 à 17:42, Simon Hobson a écrit :
>>> Brice Abba <[hidden email]> wrote:
>>>
>>>> Hi Jean,
>>>>
>>>> • Ensure the server is running with "ps cmd"
>>>> • play with this value to test " Max lifetime 43200"
>>>> • Ensure the router on the link advertise "management config flag"
>>>
>>> I read it as the server is the ISP's, so he has no access to check
>>> things like that.
>>> Besides, if he is getting an address initially (and I assume, after a
>>> reboot), then the server must be running.
>>
>> yes, that's correct. My ISP gives me an IPV6 adress at boot and reboot
>>
>> dhclient write a file /var/db/dhclient6.leases
>>
>> # cat /var/db/dhclient6.leases
>> default-duid "\000\001\000\001 \033\313$T\2375\007\255\030";
>> lease6 {
>> interface "eno1";
>> ia-pd 35:07:ad:18 {
>> starts 1485445025;
>> renew 43200;
>> rebind 172800;
>> iaprefix 2001:bc8:344f:200::/56 {
>> starts 1485445025;
>> preferred-life 7200;
>> max-life 43200;
>> }
>> }
>> option dhcp6.client-id 0:3:0:1:73:41:e0:29:71:a3;
>> option dhcp6.server-id 0:1:0:1:1b:ac:bc:2d:10:60:4b:9b:a:f4;
>> option dhcp6.name-servers 2001:bc8:401::3,2001:bc8:1::16;
>> option dhcp6.domain-search "online.net.";
>> }
>> lease6 {
>> interface "eno1";
>> ia-pd 35:07:ad:18 {
>> starts 1485445038;
>> renew 43200;
>> rebind 172800;
>> iaprefix 2001:bc8:344f:200::/56 {
>> starts 1485445038;
>> preferred-life 7200;
>> max-life 43200;
>> }
>> }
>> option dhcp6.client-id 0:3:0:1:73:41:e0:29:71:a3;
>> option dhcp6.server-id 0:1:0:1:1b:ac:bc:2d:10:60:4b:9b:a:f4;
>> option dhcp6.name-servers 2001:bc8:401::3,2001:bc8:1::16;
>> option dhcp6.domain-search "online.net.";
>> }
>>
>>
>
> Is it possible that you're getting an entire /56 block and not just a
> single address? In which case you can pretty much assign yourself any
> address you wish on that interface as long as you're within that block.
>
> I do know that Comcast does assign at least a /64. I've also heard /60.
> But 64 is what I have seen.
>

this night, my ISP will test my platform and also his IPV6 configuration...

--
Jean-Max Reymond
CKR Solutions Open Source https://www.ckr-solutions.com
_______________________________________________
dhcp-users mailing list
[hidden email]
https://lists.isc.org/mailman/listinfo/dhcp-users