From: Peter Korsgaard <peter@korsgaard.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH/next v1] package/ifupdown-scripts: send udhcpc to background in case lease is not obtained
Date: Wed, 17 Feb 2021 17:33:46 +0100 [thread overview]
Message-ID: <87eehe3b85.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <20210216202022.27264-1-ps.report@gmx.net> (Peter Seiderer's message of "Tue, 16 Feb 2021 21:20:22 +0100")
>>>>> "Peter" == Peter Seiderer <ps.report@gmx.net> writes:
> - Add the 'udhcpc_opts -b' option to /etc/network/interfaces for the
> system dhcp configured interface. With this option ('-b: background if
> lease is not obtained') the udhcpc keeps running in case the initial
> dhcp requests are not answered immediately.
> Signed-off-by: Peter Seiderer <ps.report@gmx.net>
> ---
> package/ifupdown-scripts/ifupdown-scripts.mk | 1 +
> 1 file changed, 1 insertion(+)
> diff --git a/package/ifupdown-scripts/ifupdown-scripts.mk b/package/ifupdown-scripts/ifupdown-scripts.mk
> index 5ef032142c..d3135b18b6 100644
> --- a/package/ifupdown-scripts/ifupdown-scripts.mk
> +++ b/package/ifupdown-scripts/ifupdown-scripts.mk
> @@ -28,6 +28,7 @@ define IFUPDOWN_SCRIPTS_DHCP
> echo " pre-up /etc/network/nfs_check"; \
> echo " wait-delay 15"; \
> echo " hostname \$$(hostname)"; \
> + echo " udhcpc_opts -b"; \
Wouldn't it make more sense to change the value of
CONFIG_IFUPDOWN_UDHCPC_CMD_OPTIONS in our default busybox.config instead
of hardcoding it here?
Does this still do the right thing for the fallback to IPv4LL addressing
if avahi-autoipd is enabled?
--
Bye, Peter Korsgaard
next prev parent reply other threads:[~2021-02-17 16:33 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-16 20:20 [Buildroot] [PATCH/next v1] package/ifupdown-scripts: send udhcpc to background in case lease is not obtained Peter Seiderer
2021-02-17 16:33 ` Peter Korsgaard [this message]
2021-08-01 10:07 ` Thomas Petazzoni
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87eehe3b85.fsf@dell.be.48ers.dk \
--to=peter@korsgaard.com \
--cc=buildroot@busybox.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox