NetworkManager going up and down [SOLVED]

b4sqss · 2021-03-25 12:07:22

Hello, I have been using arch for a while now, but since yesterday, networkmanager has been crashing a lot. What happens is that it just stops working and after sometimes starts working again. I've tried restarting it, changing my network manager to iwd, netctl, but it just keeps going up and down. after running "systemctl status NetworkManager" it prints

 Loaded: loaded (/usr/lib/systemd/system/NetworkManager.service; enabled; vendor preset: disabled)
    Drop-In: /usr/lib/systemd/system/NetworkManager.service.d
             `-NetworkManager-ovs.conf
     Active: active (running) since Thu 2021-03-25 08:30:43 -03; 23min ago
       Docs: man:NetworkManager(8)
   Main PID: 10406 (NetworkManager)
      Tasks: 4 (limit: 18964)
     Memory: 5.2M
     CGroup: /system.slice/NetworkManager.service
             |-10406 /usr/bin/NetworkManager --no-daemon
             `-14048 /usr/bin/dnsmasq --no-resolv --keep-in-foreground --no-hosts --bind-interfaces --pid-file=/var/run/NetworkManager/dnsmasq.pid --listen-address=127.0.0.1 --cache-size=>[/ins]

[ins]Mar 25 08:53:36 arch NetworkManager[10406]: <info>  [1616673216.0350] dhcp4 (wlan0): canceled DHCP transaction
Mar 25 08:53:36 arch NetworkManager[10406]: <info>  [1616673216.0351] dhcp4 (wlan0): state changed bound -> done
Mar 25 08:53:36 arch NetworkManager[10406]: <info>  [1616673216.0368] dhcp4 (wlan0): activation: beginning transaction (timeout in 45 seconds)
Mar 25 08:53:36 arch NetworkManager[10406]: <info>  [1616673216.0647] device (wlan0): supplicant interface state: authenticating -> associating
Mar 25 08:53:36 arch NetworkManager[10406]: <info>  [1616673216.0648] device (p2p-dev-wlan0): supplicant management interface state: authenticating -> associating
Mar 25 08:53:36 arch NetworkManager[10406]: <info>  [1616673216.0698] device (wlan0): supplicant interface state: associating -> completed
Mar 25 08:53:36 arch NetworkManager[10406]: <info>  [1616673216.0712] device (p2p-dev-wlan0): supplicant management interface state: associating -> completed
Mar 25 08:54:21 arch NetworkManager[10406]: <warn>  [1616673261.0253] dhcp4 (wlan0): request timed out
Mar 25 08:54:21 arch NetworkManager[10406]: <info>  [1616673261.0253] dhcp4 (wlan0): state changed unknown -> timeout
Mar 25 08:54:21 arch NetworkManager[10406]: <info>  [1616673261.0254] device (wlan0): DHCPv4: trying to acquire a new lease within 90 seconds

I have no idea on what to do, can someone please help me?

Last edited by b4sqss (2021-03-25 22:08:52)

seth · 2021-03-25 13:00:31

Please use code tags, not some random colorization.
The typical cause for this are concurrent services controlling the NIC, please post the output of

find /etc/systemd -type l -exec test -f {} \; -print | awk -F'/' '{ printf ("%-40s | %s\n", $(NF-0), $(NF-1)) }' | sort -f

b4sqss · 2021-03-25 15:46:16

I'm sorry for the color I put it as a mistake, but the output is

cronie.service                           | multi-user.target.wants
dbus-org.freedesktop.nm-dispatcher.service | system
dirmngr.socket                           | sockets.target.wants
display-manager.service                  | system
getty@tty1.service                       | getty.target.wants
gpg-agent-browser.socket                 | sockets.target.wants
gpg-agent-extra.socket                   | sockets.target.wants
gpg-agent-ssh.socket                     | sockets.target.wants
gpg-agent.socket                         | sockets.target.wants
libvirtd-ro.socket                       | sockets.target.wants
libvirtd.service                         | multi-user.target.wants
libvirtd.socket                          | sockets.target.wants
NetworkManager-wait-online.service       | network-online.target.wants
NetworkManager.service                   | multi-user.target.wants
optimus-manager.service                  | graphical.target.wants
p11-kit-server.socket                    | sockets.target.wants
pipewire.socket                          | sockets.target.wants
pulseaudio.socket                        | sockets.target.wants
remote-fs.target                         | multi-user.target.wants
virtlockd.socket                         | sockets.target.wants
virtlogd.socket                          | sockets.target.wants

seth · 2021-03-25 15:55:04

Nope, there's only NM.
Please post the entire system journal,

sudo journalctl -b | curl -F 'f:1=<-' ix.io

*after* you had episodes of NM failing.

Edit, also disable https://wiki.archlinux.org/index.php/Ne … domization

Last edited by seth (2021-03-25 15:56:09)

b4sqss · 2021-03-25 17:27:42

Hello again, I didn't know how to share that ix.io thing, beacause I have never used it, So besides it I also put it in a pastebin, https://pastebin.com/embed_js/9j3U7dWW

seth · 2021-03-25 17:46:28

You get a link in return and you post that. More convenient and complete…
The system has probably some uptime, but there's no inidication of a network loss (though the signal is poor)

You didn't start NM after disabling the mac randomization, did you?
Reboot, wait for the issue to appear (if it still does) and post the complete journal to ix.io.

b4sqss · 2021-03-25 19:12:14

I rebooted it but it continued http://ix.io/2U4H

seth · 2021-03-25 21:36:14

There're (at least) two APs involved.

MAC: 3a:e8:29:5b:f5:d5
SSID='wirelessn'
freq=5660 MHz

and

MAC: 66:d9:e7:92:d6:fc
SSID='wirelessn'
freq=5200 MHz

afaics the system manages to get a least from the first one *once* but immediately tries to switch to the second one and that one constantly fails - you associate but (virtually) never get a lease.

You can try passing "ath10k_core.cryptmode=1" to the kernel (for software encryption) but I suspect this to be a signal issue.
Deactivate the 5200 MHz AP and move the system closer to the 5660 MHz one.

Since you said "since yesterday": what changed yesterday? Update? Did you move locations? New wireless device in the room?…

b4sqss · 2021-03-25 22:08:38

Yesterday I updated it. And also thank you very much, I deactivated it and it worked! Thank you for the help

seth · 2021-03-25 22:17:04

Updated the AP or the Arch system?
pacman log?
Do you experience the same w/ the lts kernel?

b4sqss · 2021-03-26 02:31:12

I had updated the router, but now that I only have one it's solved. I haven't tried using the lts kernel, but can try it later.

Arch Linux

#1 2021-03-25 12:07:22

NetworkManager going up and down [SOLVED]

#2 2021-03-25 13:00:31

Re: NetworkManager going up and down [SOLVED]

#3 2021-03-25 15:46:16

Re: NetworkManager going up and down [SOLVED]

#4 2021-03-25 15:55:04

Re: NetworkManager going up and down [SOLVED]

#5 2021-03-25 17:27:42

Re: NetworkManager going up and down [SOLVED]

#6 2021-03-25 17:46:28

Re: NetworkManager going up and down [SOLVED]

#7 2021-03-25 19:12:14

Re: NetworkManager going up and down [SOLVED]

#8 2021-03-25 21:36:14

Re: NetworkManager going up and down [SOLVED]

#9 2021-03-25 22:08:38

Re: NetworkManager going up and down [SOLVED]

#10 2021-03-25 22:17:04

Re: NetworkManager going up and down [SOLVED]

#11 2021-03-26 02:31:12

Re: NetworkManager going up and down [SOLVED]

Board footer