Re: Ethernet is not started at boot
- Date: Tue, 6 Feb 2018 11:23:28 +0100
- From: <tomas@xxxxxxxxxx>
- Subject: Re: Ethernet is not started at boot
-----BEGIN PGP SIGNED MESSAGE-----
On Tue, Feb 06, 2018 at 11:27:08AM +0200, Michelle Konzack wrote:
> Am DATE hackte AUTHOR in die Tasten: john doe
> > - Are you using '/etc/network/interfaces' or
> > /etc/systemd/network/INT-NAME.network?
> I have removed systemd from Stretch!
> > - What is the content of your interface file?
> 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
This is all? No "lo" stanza? Hm.
In that case, it looks more or less correct. Issuing "ifup -a"
should bring up your enp0s25 interface. Does it?
But in this case it isn't clear what is triggering your DHCP
Nothing else in some subdirectory /etc/network/interfaces.d?
(But then, for that to have any effect, you'd have to have some
"source /etc/network/interfaces.d/*" or similar in your e/n/i
OK. Let's try to debug that: since you're doing SysV init, the
whole magic is done in /etc/init.d/networking. This one is controlled
by parameters set in /etc/default/networking. What is in there?
Next time you boot: could you watch your boot process and see whether
you see anything special around "Configuring network interfaces" (that
should be the message issued by /etc/init.d/networking). Perhaps there
is something enlightening around that.
- -- tomás
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)
-----END PGP SIGNATURE-----