Date: Tue, 20 Jul 2004 21:00:05 -0400 (EDT) From: Andrew Gallatin <gallatin@cs.duke.edu> To: FreeBSD-gnats-submit@FreeBSD.org Subject: bin/69361: dhclient sends bogus data to dhcpd and fails to get a lease Message-ID: <200407210100.i6L105Tm045340@grasshopper.cs.duke.edu> Resent-Message-ID: <200407210100.i6L10gG9043129@freefall.freebsd.org>
next in thread | raw e-mail | index | archive | help
>Number: 69361
>Category: bin
>Synopsis: dhclient sends bogus data to dhcpd and fails to get a lease
>Confidential: no
>Severity: serious
>Priority: medium
>Responsible: freebsd-bugs
>State: open
>Quarter:
>Keywords:
>Date-Required:
>Class: sw-bug
>Submitter-Id: current-users
>Arrival-Date: Wed Jul 21 01:00:42 GMT 2004
>Closed-Date:
>Last-Modified:
>Originator: Andrew Gallatin
>Release: FreeBSD 5.2-CURRENT amd64 and powerpc at least
>Organization:
>Environment:
FreeBSD thor 5.2-CURRENT FreeBSD 5.2-CURRENT #1: Sat Jul 17 07:33:17 EDT
2004 root@:/usr/src/sys/amd64/compile/THORL amd64
FreeBSD g4 5.2-CURRENT FreeBSD 5.2-CURRENT #1: Sun Jul 11 17:05:07 GMT 2004
gallatin@g4:/home/gallatin/current/sys/powerpc/compile/G4 powerpc
>Description:
dhclient occasionally fails to obtain a lease.
>How-To-Repeat:
Watch for random hangs at boot. It seems to be totally random,
but perhaps it has something to do with the current time. Both
machines (ppc and amd64) failed to obtain a lease within an
hour of each other.
Here is the lease for the amd64:
less /var/db/dhclient.leases
lease {
interface "sk0";
fixed-address 172.31.193.11;
option subnet-mask 255.255.255.0;
option routers 172.31.193.254;
option dhcp-lease-time 86400;
option dhcp-message-type 5;
option domain-name-servers 152.3.140.1,172.31.0.1;
option dhcp-server-identifier 172.31.193.254;
option broadcast-address 172.31.193.255;
renew 2 2004/7/20 11:22:49;
rebind 2 2004/7/20 20:27:21;
expire 2 2004/7/20 23:27:21;
}
And here is the lease for the powerpc:
lease {
interface "gem0";
fixed-address 172.31.193.6;
option subnet-mask 255.255.255.0;
option routers 172.31.193.254;
option dhcp-lease-time 86400;
option dhcp-message-type 5;
option domain-name-servers 172.31.0.1;
option dhcp-server-identifier 172.31.193.254;
option broadcast-address 172.31.193.255;
renew 2 2004/7/20 07:36:02;
rebind 2 2004/7/20 16:46:43;
expire 2 2004/7/20 19:46:43;
}
I powered off my snapgear VPN/router and ran
isc-dhcp3-3.0.1.r12 on an x86 when the problem happened for the second time
(ie, on the powerpc). The server gave these messages when run in
forground mode:
stening on BPF/fxp0/00:07:e9:a8:36:f2/172.31.193.0/24
Sending on BPF/fxp0/00:07:e9:a8:36:f2/172.31.193.0/24
Sending on Socket/fallback/fallback-net
DHCPREQUEST for 0.0.0.0 from 00:03:93:56:99:42 via fxp0: unknown lease 0.0.0.0.
DHCPREQUEST for 0.0.0.0 from 00:03:93:56:99:42 via fxp0: unknown lease 0.0.0.0.
>Fix:
Unknown.
Removing /var/db/dhclient.leases works around the problem.
>Release-Note:
>Audit-Trail:
>Unformatted:
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200407210100.i6L105Tm045340>