Re: Ethernet is not started at boot
- Date: Tue, 6 Feb 2018 15:48:44 +0100
- From: <tomas@xxxxxxxxxx>
- Subject: Re: Ethernet is not started at boot
-----BEGIN PGP SIGNED MESSAGE-----
On Tue, Feb 06, 2018 at 09:01:21AM -0500, Greg Wooledge wrote:
> On Tue, Feb 06, 2018 at 06:58:50AM -0500, Gene Heskett wrote:
> > On Tuesday 06 February 2018 05:42:53 Michelle Konzack wrote:
> > > auto enp0s25
> > > iface enp0s25 inet static
> > > address 192.168.0.202
> > > netmask 255.255.255.0
> > > gateway 192.168.0.1
> > > network 192.168.0.0
> > >
> > > allow-hotplug enp0s25
> > ^^^^^^^^^^^^^^^^^^^^^
> > Doesn't the above line belong ABOVE the iface line? It has been in every
> > example I've looked at. I am not using that line as its static, not
> > dhcpd.
> No. You either want "auto enp0s25" or "allow-hotplug enp0s25" but not
> If the interface is *important*, and you want services to wait for it
> before starting, then you should use "auto".
Yes, totally agreed: I think you want auto and not allow-hotplug.
But then there's still that /etc/init.d/networking throwing an error
as if it were starting the "wrong" interface, while it should be
doing the moral equivalent of "ifup -a". Hmmm.
- -- t
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)
-----END PGP SIGNATURE-----