Package: dhcp3-server
Version: 3.0.2-3
Severity: grave
Justification: renders package unusable
Hello,
since when I upgraded to the most recent version of the package, I've noticed
that if one-lease-per-client is set to on and a client releases the old IP
and re-request new one (after a reboot for example), the dhcp server goes
into an inifite loop and writes the same information to the
dhcpd.leases file until it fills up the disk
dhcpd.leases file:
===
lease 192.168.2.210 {
starts 3 2005/08/24 16:19:15;
ends 3 2005/08/24 16:44:14;
tstp 3 2005/08/31 16:19:15;
binding state free;
hardware ethernet 00:e0:81:2e:9e:7a;
client-hostname "node1";
}
lease 192.168.2.210 {
starts 3 2005/08/24 16:19:15;
ends 3 2005/08/24 16:44:14;
tstp 3 2005/08/31 16:19:15;
binding state free;
hardware ethernet 00:e0:81:2e:9e:7a;
client-hostname "node1";
}
lease 192.168.2.210 {
starts 3 2005/08/24 16:19:15;
ends 3 2005/08/24 16:44:14;
tstp 3 2005/08/31 16:19:15;
binding state free;
hardware ethernet 00:e0:81:2e:9e:7a;
client-hostname "node1";
}
lease 192.168.2.210 {
starts 3 2005/08/24 16:19:15;
ends 3 2005/08/24 16:44:14;
tstp 3 2005/08/31 16:19:15;
binding state free;
hardware ethernet 00:e0:81:2e:9e:7a;
client-hostname "node1";
}
[...]
=====
This renders the server unusable where one-lease-per-client is needed
my config
===============
# option definitions common to all supported networks...
option domain-name "cluster";
option domain-name-servers 192.168.2.1, 192.168.1.2, 206.83.0.42;
default-lease-time 604800;
max-lease-time 604800;
authoritative;
log-facility local7;
do-forward-updates on;
ignore client-updates;
ddns-updates on;
ddns-update-style interim;
subnet 192.168.2.0 netmask 255.255.255.0 {
range 192.168.2.10 192.168.2.253;
option routers 192.168.2.1;
option domain-name "cluster";
option broadcast-address 192.168.2.255;
option domain-name-servers 192.168.2.1, 192.168.1.2, 206.83.0.42;
option netbios-name-servers 192.168.1.2;
option ntp-servers 192.168.2.1;
ddns-update-style interim;
update-static-leases true;
one-lease-per-client on;
}
=================
I think the same bug was present in one of the 3.0 release candidates,
it might be the same surfacing again.
Same behavior is present on i386 architectures.
Thanks
Valerio Aimale
-- System Information:
Debian Release: testing/unstable
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)
Shell: /bin/sh linked to /bin/bash
Kernel: Linux 2.6.11-9-amd64-k8-smp
Locale: LANG=en_US, LC_CTYPE=en_US (charmap=ISO-8859-1)
Versions of packages dhcp3-server depends on:
ii debconf 1.4.56 Debian configuration management sy
ii debianutils 2.14.1 Miscellaneous utilities specific t
ii dhcp3-common 3.0.2-3 Common files used by all the dhcp3
ii libc6 2.3.5-3 GNU C Library: Shared libraries an
dhcp3-server recommends no packages.
-- debconf information:
* dhcp3-server/new_auth_behavior:
* dhcp3-server/interfaces: eth1
* dhcp3-server/config_warn:
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
