You are not logged in.
Hi everyone. I'm still relatively new to Linux so I need a little help troubleshooting this issue.
Whether I'm on wifi or ethernet, I have the same issue. I close the lid to my laptop, open it, unlock, and I have no Internet access.
I'm using KDE Plasma 5 with the default plasma-nm for network management.
While on wifi, I am able to "systemctl restart NetworkManager" to get it to reconnect. And while on ethernet, I'm able to "systemctl restart dhcpcd" to get it to reconnect.
Any ideas as to why this is happening?
This laptop is dual booted with Windows 10, which doesn't have these issues, so I know it's not the hardware.
Offline
You shouldn't be running NetworkManager.service and dhcpcd.service at the same time. Perhaps there are other problems, but start by disabling one of them (dhcpcd.service?).
Offline
You shouldn't be running NetworkManager.service and dhcpcd.service at the same time. Perhaps there are other problems, but start by disabling one of them (dhcpcd.service?).
Thanks for the help.
I'd definitely like to use NetworkManager as that's what Plasma uses. I disabled dhcpcd.service and I'm still having issues. In fact, I couldn't connect to wifi at all. Not sure if it's an issue, but my router isn't broadcasting the SSID. I manually added the profile to my list of networks. I also couldn't get a connect via ethernet.
While on ethernet, I noticed that my ip address (using ip addr) was 192.168.1.30/24. I'm on a 10.10.1.0/24 network. I don't ever remember setting a static address. That's done via netctl, correct? Is there another way a static address could be set?
Offline
Well, I guess it's an issue with my router. I've been having problems connecting to wifi at home, even on first boot. However, now that I'm at someone else's house, it works just fine. Even reconnects after waking from suspend. What's odd is that I don't have any issues on the Windows side & no issues with my other devices. I do have issues on the 2.4 GHz band of my router. But I just have that disabled now. For some reason, all of my devices have problems connecting on that band.
The only configuration difference (that I can think of) between my router & others is that I'm not broadcasting the SSID. But I'm sure I'm not the only one that does that.
Offline
So I logged into my router today & saw a notification of an update (I'm using AdvancedTomato). After updating my router, the issue seems to be resolved. Except with the 2.4 GHz band. That's probably a hardware problem since that works with none of my devices.
Offline
Well, it seems that update didn't actually fix the issue. Initially that seemed to work, but I'm thinking it may be the fact that I had my SSID hidden. Shortly before updating the router's firmware, I set the SSID to broadcast. Today I set it to not broadcast again & I'm having the same problems. Any ideas?
Offline
what is in /etc/NetworkManager/NetworkManager.conf
try adding: (or uncommenting)
[Device]
wifi-scan-rand-mac-address=0
Last edited by sotram (2016-12-20 22:48:08)
Offline
This is all that was in my NetworkManager.conf file:
[main]
plugins=keyfile
dns=default
## HTTP-based connectivity check
#[connectivity]
#uri=http://nmcheck.gnome.org/check_network_status.txt
#interval=100After adding what you suggested & rebooting, it didn't seem to help with reconnecting after resuming from suspend. I only tested wifi since that's what I'll mainly be using. After doing a systemctl restart NetworkManager, I was able to reconnect to wifi.
After going through the "journalctl -b", it looks like there may be some error messages that might be relevant. I'll put them here in case someone can make heads or tails of them:
Dec 20 18:24:59 elusivearch NetworkManager[489]: <info> [1482276299.5092] rfkill3: found WiFi radio killswitch (at /sys/devices/pci0000:00/0000:00:1d.2/0000:03:00.0/ieee80211/phy0/rfkill3) (driver ath10k_pci)
Dec 20 18:24:59 elusivearch NetworkManager[489]: <info> [1482276299.5161] (wlan0): using nl80211 for WiFi device control
Dec 20 18:24:59 elusivearch NetworkManager[489]: <info> [1482276299.5164] device (wlan0): driver supports Access Point (AP) mode
Dec 20 18:24:59 elusivearch NetworkManager[489]: <info> [1482276299.5173] manager: (wlan0): new 802.11 WiFi device (/org/freedesktop/NetworkManager/Devices/2)
Dec 20 18:24:59 elusivearch dbus[484]: [system] Activating via systemd: service name='fi.w1.wpa_supplicant1' unit='wpa_supplicant.service'
Dec 20 18:24:59 elusivearch kernel: ath10k_pci 0000:03:00.0 wlp3s0: renamed from wlan0
Dec 20 18:24:59 elusivearch systemd[1]: Starting WPA supplicant...
Dec 20 18:24:59 elusivearch NetworkManager[489]: <info> [1482276299.5376] device (wlan0): interface index 3 renamed iface from 'wlan0' to 'wlp3s0'
Dec 20 18:24:59 elusivearch NetworkManager[489]: <info> [1482276299.5445] device (wlp3s0): state change: unmanaged -> unavailable (reason 'managed') [10 20 2]
Dec 20 18:24:59 elusivearch kernel: IPv6: ADDRCONF(NETDEV_UP): wlp3s0: link is not ready
Dec 20 18:24:59 elusivearch dbus[484]: [system] Successfully activated service 'fi.w1.wpa_supplicant1'
Dec 20 18:24:59 elusivearch kernel: pcieport 0000:00:1d.2: AER: Multiple Corrected error received: id=00ea
Dec 20 18:24:59 elusivearch kernel: pcieport 0000:00:1d.2: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=00ea(Receiver ID)
Dec 20 18:24:59 elusivearch kernel: pcieport 0000:00:1d.2: device [8086:9d1a] error status/mask=00000001/00002000
Dec 20 18:24:59 elusivearch wpa_supplicant[659]: Successfully initialized wpa_supplicant
Dec 20 18:24:59 elusivearch kernel: pcieport 0000:00:1d.2: [ 0] Receiver Error (First)
Dec 20 18:24:59 elusivearch kernel: pcieport 0000:00:1d.2: AER: Multiple Corrected error received: id=00ea
Dec 20 18:24:59 elusivearch kernel: pcieport 0000:00:1d.2: can't find device of ID00ea
Dec 20 18:24:59 elusivearch systemd[1]: Started WPA supplicant.
Dec 20 18:24:59 elusivearch kernel: pcieport 0000:00:1d.2: AER: Multiple Corrected error received: id=00ea
Dec 20 18:24:59 elusivearch kernel: pcieport 0000:00:1d.2: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=00ea(Receiver ID)
Dec 20 18:24:59 elusivearch kernel: pcieport 0000:00:1d.2: device [8086:9d1a] error status/mask=00002041/00002000
Dec 20 18:24:59 elusivearch kernel: pcieport 0000:00:1d.2: [ 0] Receiver Error (First)
Dec 20 18:24:59 elusivearch kernel: pcieport 0000:00:1d.2: [ 6] Bad TLP
Dec 20 18:25:01 elusivearch NetworkManager[489]: <info> [1482276301.4669] (wlp3s0): using nl80211 for WiFi device control
Dec 20 18:25:01 elusivearch NetworkManager[489]: <info> [1482276301.4736] device (wlp3s0): set-hw-addr: set MAC address to 6E:37:D8:EE:D7:1E (scanning)
Dec 20 18:25:01 elusivearch kernel: pcieport 0000:00:1d.2: AER: Multiple Corrected error received: id=00ea
Dec 20 18:25:01 elusivearch kernel: pcieport 0000:00:1d.2: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=00ea(Receiver ID)
Dec 20 18:25:01 elusivearch kernel: pcieport 0000:00:1d.2: device [8086:9d1a] error status/mask=00000001/00002000
Dec 20 18:25:01 elusivearch kernel: pcieport 0000:00:1d.2: [ 0] Receiver Error (First)
Dec 20 18:25:01 elusivearch sddm-greeter[675]: UdevQt: unhandled device action "move"
Dec 20 18:25:01 elusivearch kernel: pcieport 0000:00:1d.2: AER: Multiple Corrected error received: id=00ea
Dec 20 18:25:01 elusivearch kernel: pcieport 0000:00:1d.2: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=00ea(Receiver ID)
Dec 20 18:25:01 elusivearch kernel: pcieport 0000:00:1d.2: device [8086:9d1a] error status/mask=00000041/00002000
Dec 20 18:25:01 elusivearch kernel: pcieport 0000:00:1d.2: [ 0] Receiver Error (First)
Dec 20 18:25:01 elusivearch kernel: pcieport 0000:00:1d.2: [ 6] Bad TLP
Offline