Network down after reboot
I recently rebooted my Debian desktop, and there is no working network now. Networking has "just worked" for so long that I am at a loss as to what to do. I haven't changed /etc/network/interfaces in forever, but ifconfig -a shows that eth0 is not being configured, and if down eth0 confirms it. I tried fiddling with the Network Tools thing in Gnome, but it hasn't changed anything. Did I miss a change to how this is done and need to learn a new approach? Thanks!
On 30/05/16 11:38 PM, William Witteman wrote:
I recently rebooted my Debian desktop, and there is no working network now. Networking has "just worked" for so long that I am at a loss as to what to do.
I haven't changed /etc/network/interfaces in forever, but ifconfig -a shows that eth0 is not being configured, and if down eth0 confirms it.
I tried fiddling with the Network Tools thing in Gnome, but it hasn't changed anything. Did I miss a change to how this is done and need to learn a new approach?
Hi William, Check /etc/udev/rules.d/70-persistent-net.rules against your eth0's MAC address Half a dozen times bitten... Cheers, Mike
On 31 May 2016 12:08 a.m., "El Fontanero" <el.fontanero@gmail.com> wrote:
On 30/05/16 11:38 PM, William Witteman wrote:
I haven't changed /etc/network/interfaces in forever, but ifconfig -a shows that eth0 is not being configured, and if down eth0 confirms it.
Check /etc/udev/rules.d/70-persistent-net.rules against your eth0's MAC address
Half a dozen times bitten...
Thanks for the tip. Sadly, the MAC address is in there correctly.
On 31/05/16 12:25 AM, William Witteman wrote:
On 31 May 2016 12:08 a.m., "El Fontanero" <el.fontanero@gmail.com <mailto:el.fontanero@gmail.com>> wrote:
On 30/05/16 11:38 PM, William Witteman wrote:
I haven't changed /etc/network/interfaces in forever, but ifconfig -a shows that eth0 is not being configured, and if down eth0 confirms it.
Check /etc/udev/rules.d/70-persistent-net.rules against your eth0's MAC address
Half a dozen times bitten...
Thanks for the tip. Sadly, the MAC address is in there correctly.
Do you have a fairly explicit setup in /etc/network/interfaces, or did the helpful-but-rather-secretive Gnome Network Mangler offer to do everything? I tend to set up wired Ethernet explicitly, but let Gnome or whatever have its way with a wireless interface, if applicable... At least it stays out of the way if you have specified a system-wide network setup. Mike
On 31 May 2016 at 00:29, El Fontanero <el.fontanero@gmail.com> wrote:
On 30/05/16 11:38 PM, William Witteman wrote:
I haven't changed /etc/network/interfaces in forever, but ifconfig -a shows that eth0 is not being configured, and if down eth0 confirms it.
Do you have a fairly explicit setup in /etc/network/interfaces, or did the helpful-but-rather-secretive Gnome Network Mangler offer to do everything? I tend to set up wired Ethernet explicitly, but let Gnome or whatever have its way with a wireless interface, if applicable... At least it stays out of the way if you have specified a system-wide network setup.
I have always set up networking in a text file - very explicitly. I thought that something Gnome-y had wormed its way in there and "helped". However, I have a partial solution - I ran an "ifup eth0", and I have a network again. What I wonder now is why isn't that happening when I boot up?
On 31/05/16 12:34 AM, William Witteman wrote:
I have always set up networking in a text file - very explicitly. I thought that something Gnome-y had wormed its way in there and "helped".
However, I have a partial solution - I ran an "ifup eth0", and I have a network again. What I wonder now is why isn't that happening when I boot up?
That is odd. udev is correct, network/interfaces is OK. Perhaps it's time to look over the logs, or poke through /etc/rc?.d/ and /etc/init.d to see if anything has gone astray. Again, my experience of Network Manager, whatever its foibles, has at least stayed out of the way of whatever I had set up in network/interfaces. This is why the truly paranoid just set up /etc/ as a git repository... This is also what you get when systems have uptimes reaching hundreds of days, as opposed to needing to reboot every hour or two. Cheers, Mike
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 El Fontanero wrote:
This is why the truly paranoid just set up /etc/ as a git repository...
I have recently discovered the packager 'etckeeper': https://joeyh.name/code/etckeeper/
etckeeper is a collection of tools to let /etc be stored in a git, mercurial, darcs, or bzr repository. It hooks into apt (and other package managers including yum and pacman-g2) to automatically commit changes made to /etc during package upgrades. It tracks file metadata that revison control systems do not normally support, but that is important for /etc, such as the permissions of /etc/shadow. It's quite modular and configurable, while also being simple to use if you understand the basics of working with revision control.
Available directly from the Debian repositories... - --Bob. On 2016-05-31 12:41 AM, El Fontanero wrote:
On 31/05/16 12:34 AM, William Witteman wrote:
I have always set up networking in a text file - very explicitly. I thought that something Gnome-y had wormed its way in there and "helped".
However, I have a partial solution - I ran an "ifup eth0", and I have a network again. What I wonder now is why isn't that happening when I boot up?
That is odd. udev is correct, network/interfaces is OK. Perhaps it's time to look over the logs, or poke through /etc/rc?.d/ and /etc/init.d to see if anything has gone astray. Again, my experience of Network Manager, whatever its foibles, has at least stayed out of the way of whatever I had set up in network/interfaces.
This is why the truly paranoid just set up /etc/ as a git repository...
This is also what you get when systems have uptimes reaching hundreds of days, as opposed to needing to reboot every hour or two.
Cheers, Mike --- Talk Mailing List talk@gtalug.org https://gtalug.org/mailman/listinfo/talk
- -- Bob Jonkman <bjonkman@sobac.com> Phone: +1-519-635-9413 SOBAC Microcomputer Services http://sobac.com/sobac/ Software --- Office & Business Automation --- Consulting GnuPG Fngrprnt:04F7 742B 8F54 C40A E115 26C2 B912 89B0 D2CC E5EA -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 Comment: Ensure confidentiality, authenticity, non-repudiability iEYEARECAAYFAldN0L0ACgkQuRKJsNLM5erWagCgzuVp8Ns8Eydr2S4wZwJnJUEM 9A0AoI7d+pqp+kLdQ0UNOaOg+pxDh8mF =37Ba -----END PGP SIGNATURE-----
<snip>
However, I have a partial solution - I ran an "ifup eth0", and I have a network again. What I wonder now is why isn't that happening when I boot up?
Hi William, Try sudo vim /etc/network/interfaces, then add auto in front of eth0 if it is not already there. Mine look's like this: aruna@debian:~$ cat /etc/network/interfaces # This file describes the network interfaces available on your system # and how to activate them. For more information, see interfaces(5). # The loopback network interface auto lo iface lo inet loopback auto eth0 iface eth0 inet dhcp Or you can add the command ifup eth0 to your rc.local file at /etc/rc.local Aruna
On Tue, May 31, 2016 at 12:34:14AM -0400, William Witteman wrote:
I have always set up networking in a text file - very explicitly. I thought that something Gnome-y had wormed its way in there and "helped".
However, I have a partial solution - I ran an "ifup eth0", and I have a network again. What I wonder now is why isn't that happening when I boot up?
Well it will if the config is in /etc/network/interfaces AND that file says 'auto eth0' on one of the lines. That's how debian has done it for over a decade now. I did see one laptop loose its wired network recently. The network device is no longer showing in lspci, which is rather odd for an internal device. Unfortunately being a Dell it seems it has a misfeature of doing an rfkill on the wifi if it can't check the link state on the wired network, so wifi can't connect either. Pretty useless laptop at this point. -- Len Sorensen
On 16-05-31 09:10 AM, Lennart Sorensen wrote:
Well it will if the config is in /etc/network/interfaces AND that file says 'auto eth0' on one of the lines.
That's how debian has done it for over a decade now.
My Linux Mint 17.2 machine running MATE desktop used to bring up the network automatically after waking up from sleep or hibernate mode. I now find that sometimes the network will start up again and sometimes it won't. ifup and ifdown wouldn't work. I used to reboot the machine to get the network back up. I've since found "killall -9 NetworkManager" fixes the problem. It is an annoyance. -- Cheers! Kevin. http://www.ve3syb.ca/ |"Nerds make the shiny things that distract Owner of Elecraft K2 #2172 | the mouth-breathers, and that's why we're | powerful!" #include <disclaimer/favourite> | --Chris Hardwick
participants (6)
-
Aruna Hewapathirane -
Bob Jonkman -
El Fontanero -
Kevin Cozens -
Lennart Sorensen -
William Witteman