Bug: DHCPv6 Server not able to read its own lease file (4.1.1)

[Maurice Massar]

hi again,

On Wed, Feb 03, 2010 at 01:06:23PM +0100, Maurice Massar wrote:
> anyway, my current workarounds before restarting dhcpd -6 are:
> 
> sed -i 's/ends never;$/ends never;;/' /var/lib/dhcp/dhcpd6.leases
> awk -v RS='\n\n' '! /binding state (expired|released)/ {IP=gensub(".*iaaddr ([^ ]*) .*", "\\1", 1); T=gensub(".*cltt ([^;]*);.*", "\\1", 1); if (T > TS[IP]) {BIND[IP] = $0; TS[IP]=T}}  END {for (IP in BIND) {print BIND[IP]"\n"}}' /var/lib/dhcp/dhcpd6.leases /var/lib/dhcp/dhcpd6.leases-AWK ; mv /var/lib/dhcp/dhcpd6.leases-AWK /var/lib/dhcp/dhcpd6.leases

with these workarounds in place, no crash in the lase 11 hours.

But: I've found yet another Bug:
If a lease is known for IAID+DUID combination it will get then in the
advertise message, even if it is not on-link for the network the client
is currently connected too (my test-case was just an active lease, I'm
not sure about expired/released ones). Here is a log output from ISCs
dhclient (4.1.1):

### first time to start dhclient on that interface:
Feb  3 18:15:08 sumomo dhclient: Listening on Socket/eth0
Feb  3 18:15:08 sumomo dhclient: Sending on   Socket/eth0
Feb  3 18:15:09 sumomo dhclient: XMT: Solicit on eth0, interval 1070ms.
Feb  3 18:15:09 sumomo dhclient: RCV: Advertise message on eth0 from fe80::21d:e5ff:fe47:2849.
Feb  3 18:15:09 sumomo dhclient: XMT: Request on eth0, interval 980ms.
Feb  3 18:15:09 sumomo dhclient: RCV: Reply message on eth0 from fe80::21d:e5ff:fe47:2849.

### after moving to another place / another network
Feb  3 18:18:30 sumomo dhclient: Listening on Socket/eth0
Feb  3 18:18:30 sumomo dhclient: Sending on   Socket/eth0
Feb  3 18:18:31 sumomo dhclient: XMT: Confirm on eth0, interval 950ms.
Feb  3 18:18:31 sumomo dhclient: RCV: Reply message on eth0 from fe80::21e:7aff:fe7b:9c7f.
Feb  3 18:18:31 sumomo dhclient: message status code NotOnLink: "Some of the addresses are not on link."
Feb  3 18:18:31 sumomo dhclient: RCV: Reply message on eth0 from fe80::21e:13ff:fe25:dbf.
Feb  3 18:18:31 sumomo dhclient: Packet received, but nothing done with it.
Feb  3 18:18:32 sumomo dhclient: XMT: Solicit on eth0, interval 1020ms.
Feb  3 18:18:32 sumomo dhclient: RCV: Advertise message on eth0 from fe80::21e:7aff:fe7b:9c7f.
Feb  3 18:18:32 sumomo dhclient: XMT: Request on eth0, interval 1070ms.
Feb  3 18:18:32 sumomo dhclient: RCV: Advertise message on eth0 from fe80::21e:13ff:fe25:dbf.
Feb  3 18:18:32 sumomo dhclient: Packet received, but nothing done with it.
Feb  3 18:18:32 sumomo dhclient: RCV: Reply message on eth0 from fe80::21e:7aff:fe7b:9c7f.
Feb  3 18:18:32 sumomo dhclient: IA_NA status code NotOnLink: "Address not for use on this link."
Feb  3 18:18:32 sumomo dhclient: RCV: Reply message on eth0 from fe80::21e:13ff:fe25:dbf.
Feb  3 18:18:32 sumomo dhclient: Packet received, but nothing done with it.
Feb  3 18:18:32 sumomo dhclient: XMT: Solicit on eth0, interval 1020ms.
Feb  3 18:18:32 sumomo dhclient: RCV: Advertise message on eth0 from fe80::21e:13ff:fe25:dbf.
Feb  3 18:18:32 sumomo dhclient: XMT: Request on eth0, interval 910ms.
Feb  3 18:18:32 sumomo dhclient: RCV: Reply message on eth0 from fe80::21e:13ff:fe25:dbf.
Feb  3 18:18:32 sumomo dhclient: IA_NA status code NotOnLink: "Address not for use on this link."
Feb  3 18:18:32 sumomo dhclient: RCV: Advertise message on eth0 from fe80::21e:7aff:fe7b:9c7f.
Feb  3 18:18:32 sumomo dhclient: Packet received, but nothing done with it.
Feb  3 18:18:32 sumomo dhclient: RCV: Reply message on eth0 from fe80::21e:7aff:fe7b:9c7f.
Feb  3 18:18:32 sumomo dhclient: Packet received, but nothing done with it.
[...]

[there are 2 relays on the second network, therefore
every requests receives 2 replies]

cu
Maurice Massar

PS: how about putting the actual global address in the syslog output?