Your message dated Wed, 05 Aug 2026 17:31:09 +0000 with message-id <[email protected]> and subject line Bug#1143544: Removed package(s) from unstable has caused the Debian Bug report #800918, regarding isc-dhcp-client: Dual NIC setup takes several hours to renew lease to be marked as done.
This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact [email protected] immediately.) -- 800918: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=800918 Debian Bug Tracking System Contact [email protected] with problems
--- Begin Message ---Package: isc-dhcp-client Version: 4.3.3-3 Severity: normal Dear Maintainer, The recent change in logging format brought this problem to my attention again by means of long logcheck mails arriving in my mailbox. I believe this issue has been around as long as I have been using the setup below. It's just that I've been ignoring it until now because nothing breaks. Here's my setup: - eth0 uses a static IP (10.11.18.2/24) - eth1 uses a dynamic address from 10.11.43.0/24 - DHCP server lives at 10.11.10.11 $ ip route default via 10.11.18.1 dev eth0 10.11.18.0/24 dev eth0 proto kernel scope link src 10.11.18.2 10.11.43.0/24 dev eth1 proto kernel scope link src 10.11.43.128 Networking works without any trouble but when time comes up to renew the lease on eth1, I get reams of messages in my logs. Below is an excerpt, starting at the previous DHCPREQUEST that got DHCPACK'd until the next DHCPACK. This cycle repeats every 3.5 hours (corresponding to the time difference between the expire and renew times in the lease). Oct 5 03:03:09 helix dhclient[1450]: DHCPREQUEST on eth1 to 10.11.10.11 port 67 Oct 5 03:03:28 helix dhclient[1450]: DHCPREQUEST on eth1 to 255.255.255.255 port 67 Oct 5 03:03:28 helix dhclient[1450]: DHCPACK from 10.11.43.1 Oct 5 03:03:28 helix dhclient[1450]: bound to 10.11.43.128 -- renewal in 5624 seconds. Oct 5 04:37:12 helix dhclient[1450]: DHCPREQUEST on eth1 to 10.11.10.11 port 67 Oct 5 04:37:18 helix dhclient[1450]: DHCPREQUEST on eth1 to 10.11.10.11 port 67 Oct 5 04:37:24 helix dhclient[1450]: DHCPREQUEST on eth1 to 10.11.10.11 port 67 [ this repeats every 5 to 20 seconds for about 500 times ] Oct 5 06:33:08 helix dhclient[1450]: DHCPREQUEST on eth1 to 10.11.10.11 port 67 Oct 5 06:33:28 helix dhclient[1450]: DHCPREQUEST on eth1 to 10.11.10.11 port 67 Oct 5 06:33:40 helix dhclient[1450]: DHCPREQUEST on eth1 to 255.255.255.255 port 67 Oct 5 06:33:40 helix dhclient[1450]: DHCPACK from 10.11.43.1 Oct 5 06:33:40 helix dhclient[1450]: bound to 10.11.43.128 -- renewal in 6885 seconds. The switch from 10.11.10.11 to the 255.255.255.255 broadcast happens at the first point in time that exceeds the time given in the lease for a rebind. My iptables implement a DROP policy but ESTABLISHED,RELATED traffic is ACCEPTed. I've tried adding explicit rules to ACCEPT all UDP and TCP traffic on ports 67 and 68 for every interface but that did not change anything. I captured network packets with wireshark and can see the DCHPREQUESTs leave from 10.11.18.2 (as per routing table) and the DCHPACKs come in from 10.11.10.11. Yet, eth1 does not seem able to renew its lease from that. When eth1 finally does renew its lease, it is via the DCHPACK from the subnet's gateway (10.11.43.1). The lease contains 10.11.10.11 as the DCHP server (and 10.11.43.1 as the router). I would have expected eth1 to be able to renew its lease directly from 10.11.10.11 and not for it to log two hours worth of DHCPREQUESTs before it is finally able to renew (or rebind?) via the gateway. -- System Information: Debian Release: stretch/sid APT prefers testing APT policy: (990, 'testing'), (500, 'testing-updates'), (500, 'stable-updates'), (500, 'unstable'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 4.0.0-2-amd64 (SMP w/8 CPU cores) Locale: LANG=ja_JP.UTF-8, LC_CTYPE=ja_JP.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: sysvinit (via /sbin/init) Versions of packages isc-dhcp-client depends on: ii debianutils 4.5.1 ii iproute2 4.1.1-1 ii libc6 2.19-22 ii libdns-export100 1:9.9.5.dfsg-12 ii libisc-export95 1:9.9.5.dfsg-12 Versions of packages isc-dhcp-client recommends: ii isc-dhcp-common 4.3.3-3 Versions of packages isc-dhcp-client suggests: pn avahi-autoipd <none> pn resolvconf <none> -- no debconf information -- Olaf Meeuwissen, LPIC-2 EPSON FLOSS Engineer -- AVASYS CORPORATION FSF Associate Member #1962 Help support software freedom http://www.fsf.org/jf?referrer=1962
--- End Message ---
--- Begin Message ---Version: 4.4.3-P1-8+rm Dear submitter, as the package isc-dhcp has just been removed from the Debian archive unstable we hereby close the associated bug reports. We are sorry that we couldn't deal with your issue properly. For details on the removal, please see https://bugs.debian.org/1143544 The version of this package that was in Debian prior to this removal can still be found using https://snapshot.debian.org/. Please note that the changes have been done on the master archive and will not propagate to any mirrors until the next dinstall run at the earliest. This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing [email protected]. Debian distribution maintenance software pp. Thorsten Alteholz (the ftpmaster behind the curtain)
--- End Message ---
