You are not logged in.

#1 2015-02-26 11:12:21

pancake_master
Member
Registered: 2015-02-26
Posts: 4

[SOLVED] Networking stopped working

Hello, so this happened yesterday morning. I couldn't connect to wifi at school, but didn't think much of it as things like this sometimes happen (could've been problem on their side, or simply weak signal) and I wasn't using laptop later that day. Today, at home, same problem and LAN doesn't work either.

Now I know it's not just temporary, or even hardware issue. Phone can connect to router wifi without problems and live distro on laptop works well too. The only thing I can recall doing prior to this problem, is system update, altho everything seemed to work fine right after..

Network interface info shows that both interfaces are down, but turning them on does nothing.

1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default 
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host 
       valid_lft forever preferred_lft forever
2: enp37s0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc fq_codel state DOWN group default qlen 1000
    link/ether 10:1f:74:e8:fc:d3 brd ff:ff:ff:ff:ff:ff
3: wlo1: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc mq state DOWN group default qlen 1000
    link/ether d0:df:9a:fc:b5:8a brd ff:ff:ff:ff:ff:ff

Dmesg output after trying to connect to wifi shows 'Reason: 3=DEAUTH_LEAVING', which brought me to one topic on this forum. Trying few methods from there didn't help.

...
[ 2554.857207] wlo1: authenticate with 90:f6:52:d2:29:c0
[ 2554.876440] wlo1: send auth to 90:f6:52:d2:29:c0 (try 1/3)
[ 2554.878595] wlo1: authenticated
[ 2554.878979] wlo1: associate with 90:f6:52:d2:29:c0 (try 1/3)
[ 2554.883418] wlo1: RX AssocResp from 90:f6:52:d2:29:c0 (capab=0x431 status=0 aid=3)
[ 2554.883562] wlo1: associated
[ 2554.902149] wlo1: deauthenticating from 90:f6:52:d2:29:c0 by local choice (Reason: 3=DEAUTH_LEAVING)
[ 2554.920139] cfg80211: Calling CRDA to update world regulatory domain
[ 2555.718617] cfg80211: Calling CRDA to update world regulatory domain

Output of 'systemctl --type=service'

dbus.service                     loaded active running D-Bus System Message Bus
dhcpcd.service                   loaded active running dhcpcd on all interfaces
kmod-static-nodes.service        loaded active exited  Create list of required static d
lightdm.service                  loaded active running Light Display Manager
NetworkManager.service           loaded active running Network Manager
polkit.service                   loaded active running Authorization Manager
rtkit-daemon.service             loaded active running RealtimeKit Scheduling Policy Se
systemd-backlight@backlight:acpi_video0.service loaded active exited  Load/Save Screen 
systemd-backlight@backlight:intel_backlight.service loaded active exited  Load/Save Scr
systemd-fsck-root.service        loaded active exited  File System Check on Root Device
systemd-journal-flush.service    loaded active exited  Flush Journal to Persistent Stor
systemd-journald.service         loaded active running Journal Service
systemd-logind.service           loaded active running Login Service
systemd-random-seed.service      loaded active exited  Load/Save Random Seed
systemd-remount-fs.service       loaded active exited  Remount Root and Kernel File Sys
systemd-rfkill@rfkill0.service   loaded active exited  Load/Save RF Kill Switch Status 
systemd-rfkill@rfkill1.service   loaded active exited  Load/Save RF Kill Switch Status 
systemd-rfkill@rfkill2.service   loaded active exited  Load/Save RF Kill Switch Status 
systemd-rfkill@rfkill3.service   loaded active exited  Load/Save RF Kill Switch Status 
systemd-sysctl.service           loaded active exited  Apply Kernel Variables
systemd-tmpfiles-setup-dev.service loaded active exited  Create Static Device Nodes in 
systemd-tmpfiles-setup.service   loaded active exited  Create Volatile Files and Direct
systemd-udev-trigger.service     loaded active exited  udev Coldplug all Devices
systemd-udevd.service            loaded active running udev Kernel Device Manager
systemd-update-utmp.service      loaded active exited  Update UTMP about System Boot/Sh
systemd-user-sessions.service    loaded active exited  Permit User Sessions
systemd-vconsole-setup.service   loaded active exited  Setup Virtual Console
udisks2.service                  loaded active running Disk Manager
upower.service                   loaded active running Daemon for power management
user@1000.service                loaded active running User Manager for UID 1000
user@620.service                 loaded active running User Manager for UID 620
wpa_supplicant.service           loaded active running WPA supplicant

Last edited by pancake_master (2015-02-28 00:59:53)

Offline

#2 2015-02-27 11:38:18

JJK
Member
Registered: 2013-10-24
Posts: 56

Re: [SOLVED] Networking stopped working

try disabling all network related services like netctl, wpa_supplicant, dhcpcd, networkmanager etc.

then reenable network manager.

e.g.

# systemctl disable netctl
# systemctl enable NetworkManager

then reboot your system and try connecting again.

Offline

#3 2015-02-27 21:55:14

pancake_master
Member
Registered: 2015-02-26
Posts: 4

Re: [SOLVED] Networking stopped working

Unfortunately, that didn't help. Good thing is LAN actually works, but only right after restart. After re-plugging the cable, system won't connect again.

Another thing I tried, was downgrading some packages which got upgraded earlier, but no success either.

Offline

#4 2015-02-27 22:06:29

Head_on_a_Stick
Member
From: London
Registered: 2014-02-20
Posts: 7,732
Website

Re: [SOLVED] Networking stopped working

Please post the output of:

ls -l /etc/systemd/system/multi-user.target.wants

Have you tried connecting manually?

Offline

#5 2015-02-27 23:36:13

pancake_master
Member
Registered: 2015-02-26
Posts: 4

Re: [SOLVED] Networking stopped working

Output of the command:

lrwxrwxrwx 1 root root 44 Jan  4 22:19 netctl-auto@wlo1.service -> /usr/lib/systemd/system/netctl-auto@.service
lrwxrwxrwx 1 root root 46 Jan  4 22:12 netctl@eth_network.service -> /etc/systemd/system/netctl@eth_network.service
lrwxrwxrwx 1 root root 46 Feb 27 22:15 NetworkManager.service -> /usr/lib/systemd/system/NetworkManager.service
lrwxrwxrwx 1 root root 51 Feb 15 17:32 remote-fs.target -> ../../../../usr/lib/systemd/system/remote-fs.target
lrwxrwxrwx 1 root root 46 Feb 27 21:25 wpa_supplicant.service -> /usr/lib/systemd/system/wpa_supplicant.service

I tried connecting manually using wpa_supplicant, didn't work.

Offline

#6 2015-02-27 23:59:38

frank604
Member
From: BC, Canada
Registered: 2011-04-20
Posts: 1,212

Re: [SOLVED] Networking stopped working

I hope you didn't just type in the example JJK wrote as it was only an 'example'.  You needed to modify with correct spelling of the service and capitalization.  https://wiki.archlinux.org/index.php/Wi … atic_setup
"There are many solutions to choose from, but remember that all of them are mutually exclusive; you should not run two daemons simultaneously"
This means you cannot have NetworkManager.service, netctl-auto.service, dhcpcd.service all started.  They are all part of the fight club.  They will fight over each other.  Only use one.

Offline

#7 2015-02-28 00:55:55

pancake_master
Member
Registered: 2015-02-26
Posts: 4

Re: [SOLVED] Networking stopped working

I was using netctl some time ago, but not anymore. Don't know why those links stayed there..

I honestly thought dhcpcd worked together with NetworkManager, even in config file for NM I set it to use dhcpcd and it was working fine. Now I read somewhere that NM is using dhclient, so I just changed that option, restarted NM service and it all finally started to work. So there's a good ending to this story.

Thanks for your time.

Offline

Board footer

Powered by FluxBB