From: Brad Spencer <spencer@jacknife.org>
To: development@lists.ipfire.org
Subject: Re: Keep trying DHCP on red0 if unavailable at boot
Date: Sat, 08 Jan 2022 23:04:31 -0400 [thread overview]
Message-ID: <273b3167-f41f-f1ab-316c-214b91b94dab@jacknife.org> (raw)
In-Reply-To: <828db493-9cab-4eee-8e70-04fea6b18ca2@diaslan.com>
[-- Attachment #1: Type: text/plain, Size: 1156 bytes --]
On 1/8/2022 10:03 PM, Jose Dias wrote:
> I've had dhcp do that to me and it doesn't take a power failure but a
> downed isp will do.
>
> My solution is to have a script run every 5 minutes to try again and
> after an hour reboot ipfire again.
>
> My desktop just died and I'm rebuilding it but I can post that script
> if it's helpful.
Yes, I agree. In the community post I linked to, I tried to explain
details failure.
With my change to its startup arguments, I've been able to demonstrate
that even if dhcpcd is unable to obtain an initial DHCP lease at boot,
ipfire's boot sequence is not blocked, and dhcpcd does correctly keep
retrying for longer than 60 seconds, and that ipfire reacts correctly
when an IP is leased. See
If you're interested, you can see my most recent followup in the
community:
https://community.ipfire.org/t/dhcp-client-on-red0-wont-reassign-ip-upon-reconnection/2455/38?u=spencer
So, I'm going to try this instead of rebooting. The retries are
frequent and cheap, and other (local) ipfire services remain available
the whole time.
Thanks for the offer!
--
Brad Spencer
next parent reply other threads:[~2022-01-09 3:04 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <828db493-9cab-4eee-8e70-04fea6b18ca2@diaslan.com>
2022-01-09 3:04 ` Brad Spencer [this message]
2022-01-09 1:27 Brad Spencer
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=273b3167-f41f-f1ab-316c-214b91b94dab@jacknife.org \
--to=spencer@jacknife.org \
--cc=development@lists.ipfire.org \
/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