I had a drive failure on my OpenSUSe 13.2 box and had to do a clean install. After the install, I could not get either my wired or wireless cards to load. They were seen, but would not connect. They were both connecting fine under the previous install & I made no changes to the router.
I stopped Wicked & disabled the service, then turned on Network Manager (not in the mood to learn Wicked right now). Network Manager sees eth0 & wlan0 (so drivers are loading), but now only wlan0 can connect. The Wired connection never connects. It’s set to DHCP v4 & the MAC is registered with the router, so the issue is probably not with the router.
This should be a pretty straightforward kind of thing, does anyone have any idea what could be wrong, or what I can query to get some troubleshooting info?
#nmcli d
DEVICE TYPE STATE CONNECTION
wlp3s5 wifi connected signal
eth0 ethernet unavailable –
lo loopback unmanaged –
The file /etc/NetworkManager/NetworkManager.conf does contain this:
[main]
plugins=ifcfg-suse,keyfile
I’m still at a loss…
And yes, I did check the physical connection between the computer and the router. Link lights all around (this ain’t my first rodeo, just still kinda new to Linux Administration).
Okay, that all checks out as expected. Plug in your ethernet cable, and report back with
systemctl status network
For reference, I get
# systemctl status network
NetworkManager.service - Network Manager
Loaded: loaded (/usr/lib/systemd/system/NetworkManager.service; enabled)
Active: active (running) since Mon 2015-10-19 07:38:05 NZDT; 2 days ago
Main PID: 943 (NetworkManager)
CGroup: /system.slice/NetworkManager.service
├─ 943 /usr/sbin/NetworkManager --no-daemon
├─21818 /sbin/dhclient -d -sf /usr/lib/nm-dhcp-helper -pf /var/run/dhclient-wlp2s0.pid -lf /var/lib/NetworkManage...
└─24567 /sbin/dhclient -d -sf /usr/lib/nm-dhcp-helper -pf /var/run/dhclient-enp3s0.pid -lf /var/lib/NetworkManage...
Oct 21 17:17:58 linux-54cw.site NetworkManager[943]: <info> Activation (enp3s0) Stage 5 of 5 (IPv4 Commit) started...
Oct 21 17:17:58 linux-54cw.site NetworkManager[943]: <info> (enp3s0): device state change: ip-config -> ip-check (reaso...80 0]
Oct 21 17:17:58 linux-54cw.site NetworkManager[943]: <info> Activation (enp3s0) Stage 5 of 5 (IPv4 Commit) complete.
Oct 21 17:17:58 linux-54cw.site NetworkManager[943]: <info> (enp3s0): device state change: ip-check -> secondaries (rea...90 0]
Oct 21 17:17:58 linux-54cw.site NetworkManager[943]: <info> (enp3s0): device state change: secondaries -> activated (re...00 0]
Oct 21 17:17:58 linux-54cw.site NetworkManager[943]: bound to 192.168.90.246 -- renewal in 105677 seconds.
Oct 21 17:17:58 linux-54cw.site NetworkManager[943]: <info> NetworkManager state is now CONNECTED_LOCAL
Oct 21 17:17:58 linux-54cw.site NetworkManager[943]: <info> NetworkManager state is now CONNECTED_GLOBAL
Oct 21 17:17:58 linux-54cw.site NetworkManager[943]: <info> Policy set 'DHCP' (enp3s0) as default for IPv4 routing and DNS.
Oct 21 17:17:59 linux-54cw.site NetworkManager[943]: <info> Activation (enp3s0) successful, device activated.
Hint: Some lines were ellipsized, use -l to show in full.
If I run
sudo journalctl -f|grep NetworkManager
I get
Oct 21 17:21:12 linux-54cw.site NetworkManager[943]: <info> (enp3s0): link connected
Oct 21 17:21:12 linux-54cw.site NetworkManager[943]: <info> (enp3s0): device state change: unavailable -> disconnected (reason 'carrier-changed') [20 30 40]
Oct 21 17:21:12 linux-54cw.site NetworkManager[943]: <info> Auto-activating connection 'DHCP'.
Oct 21 17:21:12 linux-54cw.site NetworkManager[943]: <info> Activation (enp3s0) starting connection 'DHCP'
Oct 21 17:21:12 linux-54cw.site NetworkManager[943]: <info> Activation (enp3s0) Stage 1 of 5 (Device Prepare) scheduled...
Oct 21 17:21:12 linux-54cw.site NetworkManager[943]: <info> Activation (enp3s0) Stage 1 of 5 (Device Prepare) started...
Oct 21 17:21:12 linux-54cw.site NetworkManager[943]: <info> (enp3s0): device state change: disconnected -> prepare (reason 'none') [30 40 0]
Oct 21 17:21:12 linux-54cw.site NetworkManager[943]: <info> Activation (enp3s0) Stage 2 of 5 (Device Configure) scheduled...
Oct 21 17:21:12 linux-54cw.site NetworkManager[943]: <info> Activation (enp3s0) Stage 1 of 5 (Device Prepare) complete.
Oct 21 17:21:12 linux-54cw.site NetworkManager[943]: <info> Activation (enp3s0) Stage 2 of 5 (Device Configure) starting...
Oct 21 17:21:12 linux-54cw.site NetworkManager[943]: <info> (enp3s0): device state change: prepare -> config (reason 'none') [40 50 0]
Oct 21 17:21:12 linux-54cw.site NetworkManager[943]: <info> Activation (enp3s0) Stage 2 of 5 (Device Configure) successful.
Oct 21 17:21:12 linux-54cw.site NetworkManager[943]: <info> Activation (enp3s0) Stage 3 of 5 (IP Configure Start) scheduled.
Oct 21 17:21:12 linux-54cw.site NetworkManager[943]: <info> Activation (enp3s0) Stage 2 of 5 (Device Configure) complete.
Oct 21 17:21:12 linux-54cw.site NetworkManager[943]: <info> Activation (enp3s0) Stage 3 of 5 (IP Configure Start) started...
Oct 21 17:21:12 linux-54cw.site NetworkManager[943]: <info> (enp3s0): device state change: config -> ip-config (reason 'none') [50 70 0]
Oct 21 17:21:12 linux-54cw.site NetworkManager[943]: <info> Activation (enp3s0) Beginning DHCPv4 transaction (timeout in 45 seconds)
Oct 21 17:21:12 linux-54cw.site NetworkManager[943]: <info> dhclient started with pid 24847
Oct 21 17:21:12 linux-54cw.site NetworkManager[943]: <info> Activation (enp3s0) Stage 3 of 5 (IP Configure Start) complete.
Oct 21 17:21:12 linux-54cw.site NetworkManager[943]: Internet Systems Consortium DHCP Client 4.2.6
Oct 21 17:21:12 linux-54cw.site NetworkManager[943]: Copyright 2004-2014 Internet Systems Consortium.
Oct 21 17:21:12 linux-54cw.site NetworkManager[943]: All rights reserved.
Oct 21 17:21:12 linux-54cw.site NetworkManager[943]: For info, please visit https://www.isc.org/software/dhcp/
Oct 21 17:21:12 linux-54cw.site NetworkManager[943]: <info> (enp3s0): DHCPv4 state changed nbi -> preinit
Oct 21 17:21:12 linux-54cw.site NetworkManager[943]: Listening on LPF/enp3s0/4c:72:b9:d7:29:49
Oct 21 17:21:12 linux-54cw.site NetworkManager[943]: Sending on LPF/enp3s0/4c:72:b9:d7:29:49
Oct 21 17:21:12 linux-54cw.site NetworkManager[943]: Sending on Socket/fallback
Oct 21 17:21:12 linux-54cw.site NetworkManager[943]: DHCPDISCOVER on enp3s0 to 255.255.255.255 port 67 interval 2 (xid=0x5eb52bf8)
Oct 21 17:21:12 linux-54cw.site NetworkManager[943]: DHCPOFFER from 192.168.90.1
^Z
[2]+ Stopped sudo journalctl -f | grep --color=auto Network
There should be a default wired ethernet configuration to handle DHCP as far as I understand. Check /etc/NetworkManager/system-connections/ for a default DHCP connection definition.
bunny:~ # systemctl status network
NetworkManager.service - Network Manager
Loaded: loaded (/usr/lib/systemd/system/NetworkManager.service; enabled)
Active: active (running) since Tue 2015-10-20 21:54:31 PDT; 9min ago
Main PID: 11683 (NetworkManager)
CGroup: /system.slice/NetworkManager.service
├─11683 /usr/sbin/NetworkManager --no-daemon
└─11854 /sbin/dhclient -d -sf /usr/lib/nm-dhcp-helper -pf /var/run/dhclient-wlan0.pid -lf /var/lib/NetworkManager/dhclient-6196215a-e3d7-4a...
Oct 20 21:54:37 bunny.site NetworkManager[11683]: <info> Activation (wlan0) Stage 5 of 5 (IPv4 Commit) started...
Oct 20 21:54:37 bunny.site NetworkManager[11683]: <info> (wlan0): device state change: ip-config -> ip-check (reason 'none') [70 80 0]
Oct 20 21:54:37 bunny.site NetworkManager[11683]: <info> Activation (wlan0) Stage 5 of 5 (IPv4 Commit) complete.
Oct 20 21:54:37 bunny.site NetworkManager[11683]: <info> (wlan0): device state change: ip-check -> secondaries (reason 'none') [80 90 0]
Oct 20 21:54:37 bunny.site NetworkManager[11683]: <info> (wlan0): device state change: secondaries -> activated (reason 'none') [90 100 0]
Oct 20 21:54:37 bunny.site NetworkManager[11683]: <info> NetworkManager state is now CONNECTED_LOCAL
Oct 20 21:54:37 bunny.site NetworkManager[11683]: <info> NetworkManager state is now CONNECTED_GLOBAL
Oct 20 21:54:37 bunny.site NetworkManager[11683]: <info> Policy set 'signal' (wlan0) as default for IPv4 routing and DNS.
Oct 20 21:54:37 bunny.site NetworkManager[11683]: <info> Activation (wlan0) successful, device activated.
Oct 20 21:54:37 bunny.site NetworkManager[11683]: <info> startup complete
bunny:~ # journalctl -f|grep NetworkManager
Oct 20 22:01:58 bunny.site polkitd[15635]: Operator of unix-session:71 successfully authenticated as unix-user:root to gain TEMPORARY authorization for action org.freedesktop.NetworkManager.settings.modify.system for unix-process:13175:25567752 [/usr/bin/kde-nm-connection-editor c320ba27-a7b5-44cf-8175-0747e6cdb7a0] (owned by unix-user:...)
So while my wireless nic is up, eth0 is nowhere to be found, despite there being an eth0 available to make a DHCP v4 connection with (i.e. when I go to Network Manager Connections & create a wired connection, I can restrict it to eth0 - as it appears in the list with the correct MAC address).
This is what has me flummoxed, the card shows up everywhere except as something with an active connection.
IMO you are seeing something that likely resulted from your personal efforts, and may be blocking.
Just as you don’t have a wlan0 which is instead identified as wlp3s5,
You should not see any references to eth0 and instead should be seeing a network device identified by manufacturer, and according to your posted log entry should be enp3s0.
So, for starters…
Maybe open up YAST > network settings
And if you see anything that isn’t related to your wlan, remove it and reboot. Note that you may have to temporarily switch to Wicked to do this before switching back to NM.
Then, after that with your wired network connected (and wireless turned off) check your working network configuration
Thanks for the suggestions & I apologize for dropping off for a bit (slammed at work). I’ll try these suggestions & report back ASAP (might be next week).