64-bit time_t safe lease time
Joerg Wunsch
j at ida.interface-business.de
Sun Jun 27 09:59:51 UTC 2004
As Martin Blapp wrote:
> > Right now, my impression is that ISC DHCP client is completely broken
> > for 64-bit time_t machines.
> Does it help if you define TIME as int32_t ?
Yes, that helps quite a bit. Well, now it starts to send requests quickly,
but it sends the requests to a random dst port so the DHCP server never
responds:
11:57:57.075934 0.0.0.0.68 > 255.255.255.255.39463: (request) xid:0x4f353b0d vend-rfc1048 DHCP:DISCOVER PR:SM+BR+TZ+DG+DN+NS+HN [tos 0x10]
^C
# dhclient -v gem0
Internet Systems Consortium DHCP Client V3.0.1rc14
Copyright 2004 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/products/DHCP
Listening on BPF/gem0/08:00:20:fe:a2:6e
Sending on BPF/gem0/08:00:20:fe:a2:6e
Sending on Socket/fallback
DHCPDISCOVER on gem0 to 255.255.255.255 port 39463 interval 8
DHCPDISCOVER on gem0 to 255.255.255.255 port 39463 interval 14
DHCPDISCOVER on gem0 to 255.255.255.255 port 39463 interval 14
DHCPDISCOVER on gem0 to 255.255.255.255 port 39463 interval 21
DHCPDISCOVER on gem0 to 255.255.255.255 port 39463 interval 4
No DHCPOFFERS received.
No working leases in persistent database - sleeping.
--
J"org Wunsch Unix support engineer
joerg_wunsch at interface-systems.de http://www.interface-systems.de/~j/
More information about the dhcp-hackers
mailing list