So it seems that this is hard to reproduce and I am still not sure what's going on. Attached is a pcap file of a couple of dialogues with a 15s expiry time.
Note how packet 5 is a request that goes unanswered, which would explain the EXPIRE and subsequent discovery. I cannot say why the request goes unanswered. The server actually sees the requests and ACKs: dhcpd: DHCPREQUEST for 192.168.14.28 from 4e:80:ba:7e:34:14 via lan dhcpd: DHCPACK on 192.168.14.28 to 4e:80:ba:7e:34:14 via lan dhcpd: DHCPDISCOVER from 4e:80:ba:7e:34:14 via lan dhcpd: DHCPOFFER on 192.168.14.28 to 4e:80:ba:7e:34:14 via lan dhcpd: DHCPREQUEST for 192.168.14.28 (192.168.14.1) from 4e:80:ba:7e:34:14 via lan dhcpd: DHCPACK on 192.168.14.28 to 4e:80:ba:7e:34:14 via lan but the ACK apparently doesn't make it to the client. My network is otherwise fully functional, however. Anyway, what is also strange is that after packet 9 (the final ACK of the second transaction), the client just sends a DISCOVER without a REQUEST. Something's fishy... -- .''`. martin f. krafft <[EMAIL PROTECTED]> : :' : proud Debian developer, author, administrator, and user `. `'` http://people.debian.org/~madduck - http://debiansystem.info `- Debian - when you have better things to do than fixing systems
dhclient.pcap.bz2
Description: Binary data
digital_signature_gpg.asc
Description: Digital signature (see http://martin-krafft.net/gpg/)
