[Dibbler] PD client questions

Mathias Koerber mathias at koerber.org
Wed Jul 10 16:03:25 CEST 2013


I would like to find out more on how dibbler
uses assigned prefixes on a Linux (RHEL6-64) system.

I can get my PD delegated, and the dibbled-client log
tells me it that it is assigning those prefixes (split)
to the interfaces:

> 2013.07.10 21:34:28 Client Notice    CONFIRM support compiled in.
> 2013.07.10 21:34:28 Client Info      Creating SOLICIT message with 0 IA(s), no TA and 1 PD(s) on eth2/4 interface.
> 2013.07.10 21:34:28 Client Debug     Sending SOLICIT(opts:1 25 8 6 ) on eth2/4 to multicast.
> 2013.07.10 21:34:28 Client Debug     Sleeping for 1 second(s).
> 2013.07.10 21:34:28 Client Debug     Received 114 bytes on interface eth2/4 (socket=2, addr=fe80::20c:29ff:fe8a:40be).
> 2013.07.10 21:34:28 Client Info      Received ADVERTISE on eth2/4,trans-id=0x2eebbe, 3 opts: 2 1 25
> 2013.07.10 21:34:28 Client Debug     Not executing external script (Notify script disabled).
> 2013.07.10 21:34:28 Client Debug     Sleeping for 1 second(s).
> 2013.07.10 21:34:29 Client Info      Processing msg (SOLICIT,transID=0x2eebbe,opts: 1 25 8 6)
> 2013.07.10 21:34:29 Client Info      Creating REQUEST. Backup server list contains 1 server(s).
> 2013.07.10 21:34:29 Client Debug     Advertise from Server ID=00:01:00:01:19:6d:dd:31:00:50:56:2c:5c:91, no preference option, assumed 0, no auth info.[using this]
> 2013.07.10 21:34:29 Client Debug     Authentication is disabled, not including auth options in message.
> 2013.07.10 21:34:29 Client Debug     Sending REQUEST(opts:1 25 6 2 8 ) on eth2/4 to multicast.
> 2013.07.10 21:34:29 Client Debug     Sleeping for 1 second(s).
> 2013.07.10 21:34:29 Client Debug     Received 114 bytes on interface eth2/4 (socket=2, addr=fe80::20c:29ff:fe8a:40be).
> 2013.07.10 21:34:29 Client Info      Received REPLY on eth2/4,trans-id=0x466102, 3 opts: 2 1 25
> 2013.07.10 21:34:29 Client Debug     PD: Adding 2001:1:0:8000:: prefix to PD (iaid=10) to addrDB.
> 2013.07.10 21:34:29 Client Notice    PD: Adding prefix 2001:1:0:8000::/64 to all interfaces (prefix will be split to /72 prefixes if necessary).
> 2013.07.10 21:34:29 Client Debug     PD: Interface eth2/4 is the interface, where prefix has been obtained, skipping.
> 2013.07.10 21:34:29 Client Debug     PD: Interface lo/1 is not multicast capable, ignoring.
> 2013.07.10 21:34:29 Client Info      PD: Using 2 suitable interface(s):eth1 eth0
> 2013.07.10 21:34:29 Client Notice    PD: Adding prefix 2001:1:0:8000:300::/72 on the eth1/3 interface.
> 2013.07.10 21:34:29 Client Notice    PD: Adding prefix 2001:1:0:8000:200::/72 on the eth0/2 interface.
> 2013.07.10 21:34:29 Client Debug     RENEW(IA_PD) will be sent (T1) after 600, REBIND (T2) after 960 seconds.
> 2013.07.10 21:34:29 Client Debug     PD: Adding 2001:2:0:8000:: prefix to PD (iaid=10) to addrDB.
> 2013.07.10 21:34:29 Client Notice    PD: Adding prefix 2001:2:0:8000::/64 to all interfaces (prefix will be split to /72 prefixes if necessary).
> 2013.07.10 21:34:29 Client Debug     PD: Interface eth2/4 is the interface, where prefix has been obtained, skipping.
> 2013.07.10 21:34:29 Client Debug     PD: Interface lo/1 is not multicast capable, ignoring.
> 2013.07.10 21:34:29 Client Info      PD: Using 2 suitable interface(s):eth1 eth0
> 2013.07.10 21:34:29 Client Notice    PD: Adding prefix 2001:2:0:8000:300::/72 on the eth1/3 interface.


My prefixes are advertising varying Preferred Lifetimes.

Hoewver, the generated radvd.conf does not seem to indicate the
preferred lifetime:

> ### eth1 start ###
> interface eth1
> {
>      AdvSendAdvert on;
>      prefix 2001:1:0:8000:300::/72     {
>          AdvOnLink on;
>          AdvAutonomous on;
>      };
> };
> ### eth1 end ###
> 
> 
> ### eth0 start ###
> interface eth0
> {
>      AdvSendAdvert on;
>      prefix 2001:1:0:8000:200::/72     {
>          AdvOnLink on;
>          AdvAutonomous on;
>      };
> };
> ### eth0 end ###
> 
> 
> ### eth1 start ###
> interface eth1
> {
>      AdvSendAdvert on;
>      prefix 2001:2:0:8000:300::/72     {
>          AdvOnLink on;
>          AdvAutonomous on;
>      };
> };
> ### eth1 end ###
> 
> 
> ### eth0 start ###
> interface eth0
> {
>      AdvSendAdvert on;
>      prefix 2001:2:0:8000:200::/72     {
>          AdvOnLink on;
>          AdvAutonomous on;
>      };
> };
> ### eth0 end ###

Should dibbler-client not also set AdvPreferredLifetime

> AdvPreferredLifetime seconds|infinity
> 
>     The length of time in seconds (relative to the time the packet is sent) that addresses generated from the prefix via stateless address autoconfiguration remain preferred. The symbolic value infinity represents infinity (i.e. a value of all one bits (0xffffffff)). See RFC 4862.
> 
>     Note: RFC4861's suggested default value is significantly longer: 7 days.
> 
>     Default: 14400 seconds (4 hours) 


when the DHCPv6 server sets that for a prefix?

Mathias


More information about the Dibbler mailing list