From mboxrd@z Thu Jan 1 00:00:00 1970 From: Brad Spencer 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 Message-ID: <273b3167-f41f-f1ab-316c-214b91b94dab@jacknife.org> In-Reply-To: <828db493-9cab-4eee-8e70-04fea6b18ca2@diaslan.com> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============1388946167830134755==" List-Id: --===============1388946167830134755== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable 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=20 > downed isp will do. > > My solution is to have a script run every 5 minutes to try again and=20 > after an hour reboot ipfire again. > > My desktop just died and I'm rebuilding it but I can post that script=20 > if it's helpful. Yes, I agree.=C2=A0 In the community post I linked to, I tried to explain=20 details failure. With my change to its startup arguments, I've been able to demonstrate=20 that even if dhcpcd is unable to obtain an initial DHCP lease at boot,=20 ipfire's boot sequence is not blocked, and dhcpcd does correctly keep=20 retrying for longer than 60 seconds, and that ipfire reacts correctly=20 when an IP is leased.=C2=A0 See If you're interested, you can see my most recent followup in the=20 community:=20 https://community.ipfire.org/t/dhcp-client-on-red0-wont-reassign-ip-upon-reco= nnection/2455/38?u=3Dspencer So, I'm going to try this instead of rebooting.=C2=A0 The retries are=20 frequent and cheap, and other (local) ipfire services remain available=20 the whole time. Thanks for the offer! --=20 Brad Spencer --===============1388946167830134755==--