Your message dated Mon, 12 May 2025 14:43:54 +0300
with message-id
<CAPZXPQf2aSGiGRDGc8y-=p44gceyy++2ylmq9tazqfpef_x...@mail.gmail.com>
and subject line Re: ifupdown: prepend -b to dhcpcd options to avoid exit on
timeout
has caused the Debian Bug report #1104637,
regarding dhcpcd: 1:10.1.0-11 needed for Trixie
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.)
--
1104637: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1104637
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: ifupdown
Version: 0.8.44
Severity: important
X-Debbugs-Cc: [email protected]
Since 'dhcpcd' is started by 'ifupdown' on a per-interface basis, it will exit
on timeout if no IP has been acquired, rendering the host unreachable.
As per upstream advice, avoiding this requires using the -b flag. This makes
'dhcpcd' fork to the background and keep on requesting an IP until one has been
acquired.
RM open on Salsa. The debdiff:
diff -Nru ifupdown-0.8.44/debian/changelog ifupdown-0.8.44+nmu1/debian/changelog
--- ifupdown-0.8.44/debian/changelog 2024-09-17 15:08:12.000000000 +0300
+++ ifupdown-0.8.44+nmu1/debian/changelog 2025-05-03 12:12:47.000000000
+0300
@@ -1,3 +1,10 @@
+ifupdown (0.8.44+nmu1) unstable; urgency=medium
+
+ * Non-maintainer upload.
+ * inet.defn: Prepend -b option to all 3 dhcpcd occurences.
+
+ -- Martin-Éric Racine <[email protected]> Sat, 03 May 2025 12:12:47
+0300
+
ifupdown (0.8.44) unstable; urgency=low
[ Debian Janitor ]
diff -Nru ifupdown-0.8.44/inet.defn ifupdown-0.8.44+nmu1/inet.defn
--- ifupdown-0.8.44/inet.defn 2024-08-20 05:02:23.000000000 +0300
+++ ifupdown-0.8.44+nmu1/inet.defn 2025-05-03 12:12:16.000000000 +0300
@@ -102,7 +102,7 @@
if (execable("dhclient"))
udhcpc -n -p /run/udhcpc.%iface%.pid -i %iface% [[-x hostname:%hostname%]]
\
elsif (execable("udhcpc"))
- dhcpcd [[-h %hostname%]] [[-i %vendor%]] [[-I %client%]] \
+ dhcpcd -b [[-h %hostname%]] [[-i %vendor%]] [[-I %client%]] \
[[-l %leasetime%]] [[-m %metric%]] %iface% \
elsif (execable("dhcpcd"))
echo 'No DHCP client software found!' >&2; false \
@@ -285,7 +285,7 @@
udhcpc -n -p /run/udhcpc.%iface%.pid -i %iface% [[-H %hostname%]] \
[[-c %client%]] \
elsif (execable("udhcpc"))
- dhcpcd [[-h %hostname%]] [[-i %vendor%]] [[-I %client%]] \
+ dhcpcd -b [[-h %hostname%]] [[-i %vendor%]] [[-I %client%]] \
[[-l %leasetime%]] %iface% \
elsif (execable("dhcpcd"))
echo 'No DHCP client software found!' >&2; false \
@@ -436,7 +436,7 @@
udhcpc -n -p /run/udhcpc.%iface///.%.pid -i %iface% [[-H %hostname%]] \
[[-c %client%]] \
elsif (execable("udhcpc"))
- dhcpcd [[-h %hostname%]] [[-i %vendor%]] [[-I %client%]] \
+ dhcpcd -b [[-h %hostname%]] [[-i %vendor%]] [[-I %client%]] \
[[-l %leasetime%]] %iface% \
elsif (execable("dhcpcd"))
echo 'No DHCP client software found!' >&2; false \
--- End Message ---
--- Begin Message ---
On Mon, 12 May 2025 11:51:35 +0300
=?UTF-8?Q?Martin=2D=C3=89ric_Racine?= <[email protected]>
wrote:
> On Sat, 03 May 2025 17:06:50 +0300 =?utf-8?q?Martin-=C3=89ric_Racine?=
> <[email protected]> wrote:
> > Package: ifupdown
> > Version: 0.8.44
> > Severity: important
> > X-Debbugs-Cc: [email protected]
> >
> > Since 'dhcpcd' is started by 'ifupdown' on a per-interface basis, it will
> > exit on timeout if no IP has been acquired, rendering the host unreachable.
> >
> > As per upstream advice, avoiding this requires using the -b flag. This
> > makes 'dhcpcd' fork to the background and keep on requesting an IP until
> > one has been acquired.
> >
> > RM open on Salsa. The debdiff:
>
> This problem has been solved in dhcpcd 1:10.1.0-11 instead by merging
> an upstream Git cherry-pick that makes dhcpcd fork to the background,
> after the initial timeout has been reached, instead of exiting. This
> also makes dhcpcd resilient to carrier losses, etc. since it will
> revert to IPv4LL until DHCP has acquired a lease, then delete the
> IPV4LL route, which mimics what dhclient does with the avahi-autoipd
> exit hook.
>
> Martin-Éric
Closing. I filed an unblock request instead.
Martin-Éric
--- End Message ---
