Scheduled Maintenance: We are aware of an issue with Google, AOL, and Yahoo services as email providers which are blocking new registrations. We are trying to fix the issue and we have several internal and external support tickets in process to resolve the issue. Please see: viewtopic.php?t=158230

 

 

 

Networking doesn't work unless ethernet plugged in on boot

Linux Kernel, Network, and Services configuration.
Post Reply
Message
Author
mvanorder
Posts: 3
Joined: 2018-03-14 12:07

Networking doesn't work unless ethernet plugged in on boot

#1 Post by mvanorder »

This seems to be quite a bit of an odd problem. I recently reinstalled Debian 9.3.0 and it complained about iwlwifi firmware being missing form the ISO, so when it rebooted I connected to the internet via ethernet and installed the firmware from the repo. This happened with my 9.2.0 installation(which I read something about a broken popularity contest on the original version of that set of ISOs causing the missing firmware issue which was supposed to be fixed the next day). However on 9.2.0, after installing the firmware everything worked fine. With this new install I have the following 2 scenarios:

Works:
Ethernet plugged in on boot. I get ipv4 and ipv6 IPs on both wired and wireless. I have to disconnect one sometimes in order to keep sessions in things like steam from disconnecting. At this point I can safely disconnect from wired or wireless and not worry about losing the ability to connect to the network.

Doesn't work:
Ethernet unplugged on boot. When boot completes I can see both interfaces, but no IPs and the wifi interface appears to be down. I can bring it up but nothing happens. dhclient doesn't get an IP. If I plug in the wired interface the port appears dead(no lights on either end). Also restarting the networking service has no affect on this issue.

Has anyone seen anything like this? I'm not sure where to start since I have drivers and a config that's working, but the entire networking behaves differently based on weather or not my ethernet is plugged in on boot.

User avatar
debiman
Posts: 3063
Joined: 2013-03-12 07:18

Re: Networking doesn't work unless ethernet plugged in on bo

#2 Post by debiman »

strange.
let's start with some hard data.
output of

Code: Select all

uname -rv
lspci -k
(additionally lsusb if devices are usb device, and yes, also internal devices can be)

mvanorder
Posts: 3
Joined: 2018-03-14 12:07

Re: Networking doesn't work unless ethernet plugged in on bo

#3 Post by mvanorder »

Well... I'm unable to reproduce the issue after I got home from work. I've rebooted 4 times without ethernet connected including into the 4.9.0-4 kernel(which won't boot after installing the nvidia driver on 4.9.0-6) and the wifi connects on boot every time.

If you're curious here's the output you requested:

Code: Select all

root@mvanorde-w700:~# uname -rv
4.9.0-6-amd64 #1 SMP Debian 4.9.82-1+deb9u3 (2018-03-02)
root@mvanorde-w700:~# lspci -k|grep '\(Network\|Ethernet\) controller' -A3
00:19.0 Ethernet controller: Intel Corporation 82567LM Gigabit Network Connection (rev 03)
        Subsystem: Lenovo 82567LM Gigabit Network Connection
        Kernel driver in use: e1000e
        Kernel modules: e1000e
--
03:00.0 Network controller: Intel Corporation Ultimate N WiFi Link 5300
        Subsystem: Intel Corporation Ultimate N WiFi Link 5300
        Kernel driver in use: iwlwifi
        Kernel modules: iwlwifi
root@mvanorde-w700:~# lsusb
Bus 008 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 006 Device 003: ID 17ef:1003 Lenovo Integrated Smart Card Reader
Bus 006 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 004 Device 003: ID 046d:c07d Logitech, Inc.
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 007 Device 006: ID 0781:5567 SanDisk Corp. Cruzer Blade
Bus 007 Device 005: ID 17ef:1008 Lenovo Hub
Bus 007 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 002 Device 005: ID 08ff:2810 AuthenTec, Inc. AES2810
Bus 002 Device 004: ID 0a5c:2145 Broadcom Corp. BCM2045B (BDC-2.1) [Bluetooth Controller]
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 001 Device 003: ID 046d:c52b Logitech, Inc. Unifying Receiver
Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
root@mvanorde-w700:~#

User avatar
debiman
Posts: 3063
Joined: 2013-03-12 07:18

Re: Networking doesn't work unless ethernet plugged in on bo

#4 Post by debiman »

mvanorder wrote:I'm unable to reproduce the issue after I got home from work. I've rebooted 4 times without ethernet connected including into the 4.9.0-4 kernel(which won't boot after installing the nvidia driver on 4.9.0-6) and the wifi connects on boot every time.
so it works as desired now?

mvanorder
Posts: 3
Joined: 2018-03-14 12:07

Re: Networking doesn't work unless ethernet plugged in on bo

#5 Post by mvanorder »

It was working as intended up until today. My computer rebooted(probably because we had another brownout), and I didn't have internet again. I tried everything I did the last time, then looked at dmesg which had the following line followed by a dump:

Code: Select all

[Sat Apr 28 21:39:43 2018] CPU: 0 PID: 464 Comm: NetworkManager Tainted: P        W  O    4.9.0-6-amd64 #1 Debian 4.9.82-1+deb9u3
I ran service network-manager restart which fixes the issue. I'm not sure what the cause of it is however. I'm not good at reading dmesg, it's here if anyone wants to look at it: https://pastebin.com/NcNAw8vT

arzgi
Posts: 1185
Joined: 2008-02-21 17:03
Location: Finland
Been thanked: 31 times

Re: Networking doesn't work unless ethernet plugged in on bo

#6 Post by arzgi »

mvanorder wrote:

Code: Select all

[Sat Apr 28 21:39:43 2018] CPU: 0 PID: 464 Comm: NetworkManager Tainted: P        W  O    4.9.0-6-amd64 #1 Debian 4.9.82-1+deb9u3
I ran service network-manager restart which fixes the issue. I'm not sure what the cause of it is however. I'm not good at reading dmesg, it's here if anyone wants to look at it: https://pastebin.com/NcNAw8vT
Dmesg showed succesful wlan startup. Nothin alarming there.

It is great you managed to fix your net connection. Previous years I had some issues with network-manager, and avoided installing it ever since.

User avatar
None1975
df -h | participant
df -h | participant
Posts: 1389
Joined: 2015-11-29 18:23
Location: Russia, Kaliningrad
Has thanked: 45 times
Been thanked: 66 times

Re: Networking doesn't work unless ethernet plugged in on bo

#7 Post by None1975 »

I think, network-manager is a buggy software. Avoid it and use systemd-networkd tools.
OS: Debian 12.4 Bookworm / DE: Enlightenment
Debian Wiki | DontBreakDebian, My config files on github

User avatar
debiman
Posts: 3063
Joined: 2013-03-12 07:18

Re: Networking doesn't work unless ethernet plugged in on bo

#8 Post by debiman »

mvanorder wrote:I'm not good at reading dmesg, it's here if anyone wants to look at it: https://pastebin.com/NcNAw8vT
maybe you should also be looking at systemd (commands: journalctl, systemctl).
nobody is good at reading this information, it's extremely tedious and sometimes even nerve-wracking, but does not require aquired skills, just patience and concentration.
personally, i don't like when people dump unfiltered logs on me.

Post Reply