Dev1 Galaxy Forum / ifup wait at boot

Re: ifup wait at boot

dummy@example.com (Ogis1975) — Mon, 18 Oct 2021 16:22:14 +0000

This problem fixed in Devuan Chimaera 4.0

Re: ifup wait at boot

dummy@example.com (Kiergan) — Mon, 11 Oct 2021 13:02:05 +0000

Thanks for your quick reply.
I will give that a try. ( I went to try Devuan 3.0.0 but it behaves the same, so might as well go again install 3.1.1 then.)
I am not such a Veteran, at least not on *nix, so I used a MX-linux installer to make changes in the root.
I have heard of this chroot you mention, I did LFS once, but I have to look up everything, there is not much that I know by heart, on Linux.

Edit:
Thanks, the
auto eth0 in /etc/network/interfaces
works.

Now to find a way to fix this in the installer .iso

Re: ifup wait at boot

dummy@example.com (ralph.ronnquist) — Mon, 11 Oct 2021 12:31:40 +0000

It sounds like your /etc/network/interfaces should have the normal configuration setup for eth0 of

auto eth0
iface eth0 inet dhcp

Yes, you can use an installation iso as a (limited) rescue system for an installed system. Just start the installation and use ctrl-alt-f2 at the very first dialog. That brings you to a command line, where you can mount the installed root partition onto /mnt, and then chroot into that for various hands-on.

Re: ifup wait at boot

dummy@example.com (Kiergan) — Mon, 11 Oct 2021 10:44:50 +0000

Hi,
I have this problem when booting for the 1st time after installing the net-install and also the server-install Devuan 3.1.1 Beowulf.
How can I make the needed changes when I can not boot?
Do I need to get a rescue-cd or is it possible to modify the installer?

I have not had this problem before, with older versions.

Edit:

I booted with a rescue-cd and modified the file etc/network/interfaces
Now it boots, but I get no IP, (state DOWN)

This is very inconvenient.

edit:
/sbin/ifconfig eth0 up
dhclient

gave me an IP.

How to fix this, so it will get an IP on boot, like normal?

Re: ifup wait at boot

dummy@example.com (Jafa) — Wed, 21 Aug 2019 17:33:53 +0000

For the primary network interface, changing the interface from using "dhcp" to "manual" solves this ..

Re: ifup wait at boot

dummy@example.com (geki) — Sun, 07 Jul 2019 10:11:27 +0000

JFYI, this looks more sane, as Geoff pointed out. I wonder, if the dependency to iproute2 is acceptable.

--- /etc/init.d/networking	2019-07-07 12:05:57.696076136 +0200
+++ /etc/init.d/networking	2019-07-07 12:11:41.412092526 +0200
@@ -14,6 +14,7 @@
 IFSTATE="$RUN_DIR/ifstate"
 STATEDIR="$RUN_DIR/state"
 
+[ -x /sbin/ip ] || exit 0
 [ -x /sbin/ifup ] || exit 0
 [ -x /sbin/ifdown ] || exit 0
 
@@ -107,7 +108,12 @@
 				    link=${link##.*}
 				    if [ -e "/sys/class/net/$link" ]
 				    then
-					echo "$iface"
+					# link detection does not work unless we up the link
+					ip link set "$iface" up || true
+					if [ "$(cat /sys/class/net/$link/operstate)" = up ]
+					then
+						echo "$iface"
+					fi
 				    fi
 			    done)
 	    if [ -n "$ifaces" ]

Re: ifup wait at boot

dummy@example.com (Geoff 42) — Wed, 24 Apr 2019 14:47:55 +0000

As I am looking at a simple set-up with no network manager, I was looking at this patch to get past the disconnected eth0.

I am not too good at some of the scoping in some of these languages, but I think that in this patch that $iface and $link are not defined when we get to use them. I think that $ifaces is defined and in my case I only have one interface with allow-hotplug, so putting $ifaces in this patch seems to work for me, although probably not strictly correct.

Geoff

Re: ifup wait at boot

dummy@example.com (fsmithred) — Thu, 11 Apr 2019 21:15:19 +0000

The DNG message that golinux linked earlier in this thread is gone. I think I know what it pointed to - there was a patch submitted by Didier Kryn for /etc/init.d/networking that fixes the problem. I have the patch, and I have the message in my mail. Both are copied below.

I don't know if the line numbers in the patch are still correct, but I do know that it works in ascii. I've applied it manually.

Le 22/12/2017 à 08:49, KatolaZ a écrit :
> On Fri, Dec 22, 2017 at 08:40:37AM +0100, Didier Kryn wrote:
>> Hello.
>>
>> I've now switched to ASCII for my personal laptop (amd-64 arch) and I
>> found it working well, better for me than Jessie.
> Hi Didier,
>
> that's pretty good news
>
> [cut]
>
>> A regression with respect to the older releases of Debian and Devuan is
>> the new /etc/init.d/networking script. I have sent on the list a patch to
>> correct this file. I aso had to change /etc/interfaces: previously I had
>> "allow-hotplug wlan0"; now I still have it, plus "auto wlan0", otherwise
>> wlan0 is not always started at boot time. This ifpudown logic is rather
>> convoluted and I fall down to this kind of tricks.
>>
> Could you please send a patch to /etc/init.d/networking (it's very
> difficult to retrieve it from the ML)? I am not looking forward to
> fork ifupdown, to be honest. It would be better maybe to submit the
> patch upstream (i.e., to Debian).
Seems the patch introducing the regression is from the author, not from Debian. It is in the form of a patch in the source of the package, but I didn't find where this patch is applied. Maybe, as suggested by Svante, I should modify the patch so that it changes the behaviour only if systemd is installed, and propose this modification to the author.
Didier

check-link-state.patch

--- networking~	2016-09-16 15:02:20.000000000 +0200
+++ networking	2017-12-18 17:25:49.902781233 +0100
@@ -112,7 +112,12 @@ ifup_hotplug () {
 			    done)
 	    if [ -n "$ifaces" ]
 	    then
-		ifup $ifaces "$@" || true
+		# link detection does not work unless we up the link
+		ip link set "$iface" up || true
+		if [ "$(cat /sys/class/net/$link/operstate)" = up ]
+		then
+		    echo "$iface"
+		fi
 	    fi
     fi
 }

Re: ifup wait at boot

dummy@example.com (climbingturtle) — Fri, 15 Mar 2019 22:20:57 +0000

Hi. Just want to say I also had this problem for a long time and can not remember when it appeared. The solution that worked for me was what people here have suggested, commenting out the lines: allow-hotplug eth0,,, iface eth0 inet dhcp

Re: ifup wait at boot

dummy@example.com (Ogis1975) — Wed, 03 Oct 2018 17:41:00 +0000

MiyoLinux wrote:

This affects only wireless network connections from my experience. Wired isn't affected.

Hello. I am on wired connection. I do not have wireless connection. It is a desktop.

Re: ifup wait at boot

dummy@example.com (MiyoLinux) — Mon, 01 Oct 2018 22:22:24 +0000

This affects only wireless network connections from my experience. Wired isn't affected.

The fix is shown above, and it has worked for me for months and months. I include this fix in MiyoLinux releases also. As root, open the file /etc/network/interfaces

Save a copy of that file (before editing it) somewhere just in case you need to put it back.

You can comment out lines if you prefer, but I personally remove everything in that file and leave only the following two lines...

auto lo
iface lo inet loopback

Save the file. Close it. Then reboot. The delay should be gone,

Re: ifup wait at boot

dummy@example.com (Ogis1975) — Mon, 01 Oct 2018 16:28:14 +0000

Same bug here.

Re: ifup wait at boot

dummy@example.com (menuhin) — Mon, 01 Oct 2018 12:05:34 +0000

Hi Forum members,

This behavior also exhibits in my laptop: a long ifup eth0 wait with the 'allow-hotplug eth0' line in etc/network/interfaces

It seems to be a known Debian bug as well:

https://bugs.debian.org/cgi-bin/bugrepo … bug=838871

Re: ifup wait at boot

dummy@example.com (figdev) — Sat, 19 May 2018 22:52:54 +0000

thanks very much!

Re: ifup wait at boot

dummy@example.com (dxrobertson) — Sat, 19 May 2018 21:46:09 +0000

The file is etc/network/interfaces.

The contents before the modification:

# This file describes the network interfaces available on your system
# and how to activate them. For more information, see interfaces(5).

source /etc/network/interfaces.d/*

# The loopback network interface
auto lo
iface lo inet loopback

# The primary network interface
allow-hotplug eth0
iface eth0 inet dhcp

The file contents after the modification (the fix):

# This file describes the network interfaces available on your system
# and how to activate them. For more information, see interfaces(5).

source /etc/network/interfaces.d/*

# The loopback network interface
auto lo
iface lo inet loopback