NetworkManager

English Network/Internet
#1

I have an HP 840 and was previously running openSUSE 42.2 LEAP and had no issues. One of my job duties required me to dabble with some RHEL systems so I had installed RHEL 7.3 and then Fedora 25. I went with Fedora 25 and then ran VMware Workstation to run RHEL virtually and all was well. I kept reading and hearing about openSUSE Tumbleweed being a great rolling release so I recently wiped out everything and installed openSUSE Tumbleweed. The installation went fine and I must admit having snapper and btrfs makes me giggly lol! but I have been experience several issues. The one that is the most annoying is with NetworkManager. It appears I am running 1.4.6 according to the applet and I use XFCE, I like simple. However, when I reboot it takes about 2 minutes to get a network connection and the panel icon shows the disconnected icon. I have discovered I have networking but the icon doesn’t show the wireless bars, as an example, for several minutes after boot up. It also freezes up on occasion if I try to look at what wireless networks are available. I wasn’t sure if this was just an issue with Tumbleweed, this HP 840 networking cards or what.

I am hoping I can get this resolved as my other issue I believe is with the touchpad so I just need to mess around more with those setting but the NetworkManager item is top priority. If I can’t get this fixed I’ll have to move back to either LEAP or Fedora both of which I ran XFCE fine.

Thanks!

#2

How is your wireless connection defined in Networkanager? Specfically is it configured as a ‘system connection’ (for all users) or a ‘user connection’? And how do you have the secrets stored?

More about this here
https://doc.opensuse.org/documentation/leap/reference/html/book.opensuse.reference/cha.nm.html#sec.nm.configure

If you need to share details about your connection profile, check the configuration in the /etc/NetworkManager/system-connections/ directory.

You can also examine the messaging from NM using

sudo journalctl -u NetworkManager
#3

It may also pay to check that wicked (alternative openSUSE network management service) is not active concurrently with NetworkManager.

sudo systemctl status wicked
#4

You can also examine the messaging from NM using

sudo journalctl -u NetworkManager

[/QUOTE]

– Logs begin at Fri 2017-06-02 18:21:37 EDT, end at Sat 2017-06-03 18:57:53 EDT. –
Jun 02 18:21:43 PC4399N systemd[1]: Started Network Manager.
Jun 02 18:21:43 PC4399N NetworkManager[1190]: <warn> [1496442103.0901] settings: skipping deprecated plugin ifcfg-suse
Jun 02 18:21:43 PC4399N NetworkManager[1190]: <info> [1496442103.0902] settings: loaded plugin keyfile: (c) 2007 - 2016 Red Hat, Inc. To report bugs
Jun 02 18:21:43 PC4399N NetworkManager[1190]: <info> [1496442103.1002] keyfile: new connection /etc/NetworkManager/system-connections/Oscitsox_Plus (
Jun 02 18:21:43 PC4399N NetworkManager[1190]: <info> [1496442103.1283] keyfile: new connection /etc/NetworkManager/system-connections/WS-SECURE (59d7
Jun 02 18:21:43 PC4399N NetworkManager[1190]: <info> [1496442103.1398] keyfile: new connection /etc/NetworkManager/system-connections/WS-DSL (434ed25
Jun 02 18:21:43 PC4399N NetworkManager[1190]: <info> [1496442103.2676] settings: hostname: using hostnamed
Jun 02 18:21:43 PC4399N NetworkManager[1190]: <info> [1496442103.2676] settings: hostname changed from (none) to “PC4399N.WS.WSFGRP.NET”
Jun 02 18:21:43 PC4399N dns-resolver[1358]: ATTENTION: You have modified /etc/resolv.conf. Leaving it untouched…
Jun 02 18:21:43 PC4399N NetworkManager[1190]: <13>Jun 2 18:21:43 dns-resolver: ATTENTION: You have modified /etc/resolv.conf. Leaving it untouched…
Jun 02 18:21:43 PC4399N NetworkManager[1190]: <13>Jun 2 18:21:43 dns-resolver: You can find my version in /etc/resolv.conf.netconfig
Jun 02 18:21:43 PC4399N NetworkManager[1190]: ATTENTION: You have modified /etc/resolv.conf. Leaving it untouched…
Jun 02 18:21:43 PC4399N NetworkManager[1190]: You can find my version in /etc/resolv.conf.netconfig …
Jun 02 18:21:43 PC4399N NetworkManager[1190]: nisdomainname: you must be root to change the domain name
Jun 02 18:21:43 PC4399N NetworkManager[1190]: <warn> [1496442103.7909] dns-mgr: could not commit DNS changes: Error calling netconfig: exited with st
Jun 02 18:21:43 PC4399N NetworkManager[1190]: <info> [1496442103.7909] policy: setting system hostname to ‘PC4399N.WS.WSFGRP.NET’ (from system config
Jun 02 18:21:43 PC4399N NetworkManager[1190]: <info> [1496442103.7911] dhcp-init: Using DHCP client ‘dhclient’
Jun 02 18:21:43 PC4399N.WS.WSFGRP.NET NetworkManager[1190]: <info> [1496442103.7911] manager: WiFi enabled by radio killswitch; enabled by state file
Jun 02 18:21:43 PC4399N.WS.WSFGRP.NET NetworkManager[1190]: <info> [1496442103.7912] manager: WWAN enabled by radio killswitch; enabled by state file
Jun 02 18:21:43 PC4399N.WS.WSFGRP.NET NetworkManager[1190]: <info> [1496442103.7912] manager: Networking is enabled by state file
Jun 02 18:21:43 PC4399N.WS.WSFGRP.NET NetworkManager[1190]: <info> [1496442103.7913] Loaded device plugin: NMBondDeviceFactory (internal)
Jun 02 18:21:43 PC4399N.WS.WSFGRP.NET NetworkManager[1190]: <info> [1496442103.7913] Loaded device plugin: NMBridgeDeviceFactory (internal)
Jun 02 18:21:43 PC4399N.WS.WSFGRP.NET NetworkManager[1190]: <info> [1496442103.7913] Loaded device plugin: NMEthernetDeviceFactory (internal)
Jun 02 18:21:43 PC4399N.WS.WSFGRP.NET NetworkManager[1190]: <info> [1496442103.7913] Loaded device plugin: NMInfinibandDeviceFactory (internal)
Jun 02 18:21:43 PC4399N.WS.WSFGRP.NET NetworkManager[1190]: <info> [1496442103.7913] Loaded device plugin: NMIPTunnelDeviceFactory (internal)
Jun 02 18:21:43 PC4399N.WS.WSFGRP.NET NetworkManager[1190]: <info> [1496442103.7914] Loaded device plugin: NMMacsecDeviceFactory (internal)
Jun 02 18:21:43 PC4399N.WS.WSFGRP.NET NetworkManager[1190]: <info> [1496442103.7914] Loaded device plugin: NMMacvlanDeviceFactory (internal)
Jun 02 18:21:43 PC4399N.WS.WSFGRP.NET NetworkManager[1190]: <info> [1496442103.7914] Loaded device plugin: NMTunDeviceFactory (internal)
…skipping…
Jun 03 18:55:01 PC4399N.WS.WSFGRP.NET NetworkManager[1190]: <info> [1496530501.3066] device (wlo1): supplicant interface state: inactive → disconnec
Jun 03 18:55:01 PC4399N.WS.WSFGRP.NET NetworkManager[1190]: <info> [1496530501.3068] sup-iface[0x55b96b39f630,wlo1]: config: set interface ap_scan to
Jun 03 18:55:01 PC4399N.WS.WSFGRP.NET NetworkManager[1190]: <info> [1496530501.3157] device (wlo1): supplicant interface state: disconnected → inact
Jun 03 18:55:01 PC4399N.WS.WSFGRP.NET NetworkManager[1190]: <info> [1496530501.3220] device (wlo1): supplicant interface state: inactive → scanning
Jun 03 18:55:04 PC4399N.WS.WSFGRP.NET NetworkManager[1190]: <info> [1496530504.5370] device (wlo1): supplicant interface state: scanning → authentic
Jun 03 18:55:04 PC4399N.WS.WSFGRP.NET NetworkManager[1190]: <info> [1496530504.5384] device (wlo1): supplicant interface state: authenticating → ass
Jun 03 18:55:04 PC4399N.WS.WSFGRP.NET NetworkManager[1190]: <info> [1496530504.5467] device (wlo1): supplicant interface state: associating → associ
Jun 03 18:55:04 PC4399N.WS.WSFGRP.NET NetworkManager[1190]: <info> [1496530504.5555] device (wlo1): supplicant interface state: associated → 4-way h
Jun 03 18:55:04 PC4399N.WS.WSFGRP.NET NetworkManager[1190]: <info> [1496530504.5661] device (wlo1): supplicant interface state: 4-way handshake → co
Jun 03 18:55:04 PC4399N.WS.WSFGRP.NET NetworkManager[1190]: <info> [1496530504.5661] device (wlo1): Activation: (wifi) Stage 2 of 5 (Device Configure
Jun 03 18:55:04 PC4399N.WS.WSFGRP.NET NetworkManager[1190]: <info> [1496530504.5662] device (wlo1): state change: config → ip-config (reason ‘none’)
Jun 03 18:55:04 PC4399N.WS.WSFGRP.NET NetworkManager[1190]: <info> [1496530504.5668] dhcp4 (wlo1): activation: beginning transaction (timeout in 45 s
Jun 03 18:55:04 PC4399N.WS.WSFGRP.NET NetworkManager[1190]: <info> [1496530504.5690] dhcp4 (wlo1): dhclient started with pid 8158
Jun 03 18:55:04 PC4399N.WS.WSFGRP.NET NetworkManager[1190]: <info> [1496530504.6163] dhcp4 (wlo1): address 192.168.29.101
Jun 03 18:55:04 PC4399N.WS.WSFGRP.NET NetworkManager[1190]: <info> [1496530504.6163] dhcp4 (wlo1): plen 24 (255.255.255.0)
Jun 03 18:55:04 PC4399N.WS.WSFGRP.NET NetworkManager[1190]: <info> [1496530504.6163] dhcp4 (wlo1): gateway 192.168.29.1
Jun 03 18:55:04 PC4399N.WS.WSFGRP.NET NetworkManager[1190]: <info> [1496530504.6163] dhcp4 (wlo1): server identifier 192.168.29.1
Jun 03 18:55:04 PC4399N.WS.WSFGRP.NET NetworkManager[1190]: <info> [1496530504.6163] dhcp4 (wlo1): lease time 86400
Jun 03 18:55:04 PC4399N.WS.WSFGRP.NET NetworkManager[1190]: <info> [1496530504.6163] dhcp4 (wlo1): hostname ‘PC4399N’
Jun 03 18:55:04 PC4399N.WS.WSFGRP.NET NetworkManager[1190]: <info> [1496530504.6164] dhcp4 (wlo1): nameserver ‘192.168.29.1’
Jun 03 18:55:04 PC4399N.WS.WSFGRP.NET NetworkManager[1190]: <info> [1496530504.6164] dhcp4 (wlo1): domain name ‘T-mobile.com’
Jun 03 18:55:04 PC4399N.WS.WSFGRP.NET NetworkManager[1190]: <info> [1496530504.6164] dhcp4 (wlo1): wins ‘192.168.29.1’
Jun 03 18:55:04 PC4399N.WS.WSFGRP.NET NetworkManager[1190]: <info> [1496530504.6164] dhcp4 (wlo1): state changed unknown → bound
Jun 03 18:55:04 PC4399N.WS.WSFGRP.NET NetworkManager[1190]: <info> [1496530504.6190] device (wlo1): state change: ip-config → ip-check (reason 'none
Jun 03 18:55:04 PC4399N.WS.WSFGRP.NET NetworkManager[1190]: <info> [1496530504.6197] device (wlo1): state change: ip-check → secondaries (reason 'no
Jun 03 18:55:04 PC4399N.WS.WSFGRP.NET NetworkManager[1190]: <info> [1496530504.6202] device (wlo1): state change: secondaries → activated (reason 'n
Jun 03 18:55:04 PC4399N.WS.WSFGRP.NET NetworkManager[1190]: <info> [1496530504.6203] manager: NetworkManager state is now CONNECTED_LOCAL
Jun 03 18:55:04 PC4399N.WS.WSFGRP.NET NetworkManager[1190]: <info> [1496530504.6223] manager: NetworkManager state is now CONNECTED_SITE
Jun 03 18:55:04 PC4399N.WS.WSFGRP.NET NetworkManager[1190]: <info> [1496530504.6225] policy: set ‘Oscitsox_Plus’ (wlo1) as default for IPv4 routing a
Jun 03 18:55:04 PC4399N.WS.WSFGRP.NET NetworkManager[1190]: <13>Jun 3 18:55:04 dns-resolver: ATTENTION: You have modified /etc/resolv.conf. Leaving i
Jun 03 18:55:04 PC4399N.WS.WSFGRP.NET NetworkManager[1190]: <13>Jun 3 18:55:04 dns-resolver: You can find my version in /etc/resolv.conf.netconfig
Jun 03 18:55:04 PC4399N.WS.WSFGRP.NET NetworkManager[1190]: ATTENTION: You have modified /etc/resolv.conf. Leaving it untouched…
Jun 03 18:55:04 PC4399N.WS.WSFGRP.NET NetworkManager[1190]: You can find my version in /etc/resolv.conf.netconfig …
Jun 03 18:55:04 PC4399N.WS.WSFGRP.NET NetworkManager[1190]: nisdomainname: you must be root to change the domain name
Jun 03 18:55:04 PC4399N.WS.WSFGRP.NET NetworkManager[1190]: <warn> [1496530504.7891] dns-mgr: could not commit DNS changes: Error calling netconfig:
Jun 03 18:55:04 PC4399N.WS.WSFGRP.NET NetworkManager[1190]: <info> [1496530504.7892] device (wlo1): Activation: successful, device activated.
Jun 03 18:55:05 PC4399N.WS.WSFGRP.NET NetworkManager[1190]: <info> [1496530505.0863] manager: NetworkManager state is now CONNECTED_GLOBAL
…skipping…
Jun 03 18:55:01 PC4399N.WS.WSFGRP.NET NetworkManager[1190]: <info> [1496530501.3066] device (wlo1): supplicant interface state: inactive → disconnec
Jun 03 18:55:01 PC4399N.WS.WSFGRP.NET NetworkManager[1190]: <info> [1496530501.3068] sup-iface[0x55b96b39f630,wlo1]: config: set interface ap_scan to
Jun 03 18:55:01 PC4399N.WS.WSFGRP.NET NetworkManager[1190]: <info> [1496530501.3157] device (wlo1): supplicant interface state: disconnected → inact
Jun 03 18:55:01 PC4399N.WS.WSFGRP.NET NetworkManager[1190]: <info> [1496530501.3220] device (wlo1): supplicant interface state: inactive → scanning
Jun 03 18:55:04 PC4399N.WS.WSFGRP.NET NetworkManager[1190]: <info> [1496530504.5370] device (wlo1): supplicant interface state: scanning → authentic
Jun 03 18:55:04 PC4399N.WS.WSFGRP.NET NetworkManager[1190]: <info> [1496530504.5384] device (wlo1): supplicant interface state: authenticating → ass
Jun 03 18:55:04 PC4399N.WS.WSFGRP.NET NetworkManager[1190]: <info> [1496530504.5467] device (wlo1): supplicant interface state: associating → associ
Jun 03 18:55:04 PC4399N.WS.WSFGRP.NET NetworkManager[1190]: <info> [1496530504.5555] device (wlo1): supplicant interface state: associated → 4-way h
Jun 03 18:55:04 PC4399N.WS.WSFGRP.NET NetworkManager[1190]: <info> [1496530504.5661] device (wlo1): supplicant interface state: 4-way handshake → co
Jun 03 18:55:04 PC4399N.WS.WSFGRP.NET NetworkManager[1190]: <info> [1496530504.5661] device (wlo1): Activation: (wifi) Stage 2 of 5 (Device Configure
Jun 03 18:55:04 PC4399N.WS.WSFGRP.NET NetworkManager[1190]: <info> [1496530504.5662] device (wlo1): state change: config → ip-config (reason ‘none’)
Jun 03 18:55:04 PC4399N.WS.WSFGRP.NET NetworkManager[1190]: <info> [1496530504.5668] dhcp4 (wlo1): activation: beginning transaction (timeout in 45 s
Jun 03 18:55:04 PC4399N.WS.WSFGRP.NET NetworkManager[1190]: <info> [1496530504.5690] dhcp4 (wlo1): dhclient started with pid 8158
Jun 03 18:55:04 PC4399N.WS.WSFGRP.NET NetworkManager[1190]: <info> [1496530504.6163] dhcp4 (wlo1): address 192.168.29.101
Jun 03 18:55:04 PC4399N.WS.WSFGRP.NET NetworkManager[1190]: <info> [1496530504.6163] dhcp4 (wlo1): plen 24 (255.255.255.0)
Jun 03 18:55:04 PC4399N.WS.WSFGRP.NET NetworkManager[1190]: <info> [1496530504.6163] dhcp4 (wlo1): gateway 192.168.29.1
Jun 03 18:55:04 PC4399N.WS.WSFGRP.NET NetworkManager[1190]: <info> [1496530504.6163] dhcp4 (wlo1): server identifier 192.168.29.1
Jun 03 18:55:04 PC4399N.WS.WSFGRP.NET NetworkManager[1190]: <info> [1496530504.6163] dhcp4 (wlo1): lease time 86400
Jun 03 18:55:04 PC4399N.WS.WSFGRP.NET NetworkManager[1190]: <info> [1496530504.6163] dhcp4 (wlo1): hostname ‘PC4399N’
Jun 03 18:55:04 PC4399N.WS.WSFGRP.NET NetworkManager[1190]: <info> [1496530504.6164] dhcp4 (wlo1): nameserver ‘192.168.29.1’
Jun 03 18:55:04 PC4399N.WS.WSFGRP.NET NetworkManager[1190]: <info> [1496530504.6164] dhcp4 (wlo1): domain name ‘T-mobile.com’
Jun 03 18:55:04 PC4399N.WS.WSFGRP.NET NetworkManager[1190]: <info> [1496530504.6164] dhcp4 (wlo1): wins ‘192.168.29.1’
Jun 03 18:55:04 PC4399N.WS.WSFGRP.NET NetworkManager[1190]: <info> [1496530504.6164] dhcp4 (wlo1): state changed unknown → bound
Jun 03 18:55:04 PC4399N.WS.WSFGRP.NET NetworkManager[1190]: <info> [1496530504.6190] device (wlo1): state change: ip-config → ip-check (reason 'none
Jun 03 18:55:04 PC4399N.WS.WSFGRP.NET NetworkManager[1190]: <info> [1496530504.6197] device (wlo1): state change: ip-check → secondaries (reason 'no
Jun 03 18:55:04 PC4399N.WS.WSFGRP.NET NetworkManager[1190]: <info> [1496530504.6202] device (wlo1): state change: secondaries → activated (reason 'n
Jun 03 18:55:04 PC4399N.WS.WSFGRP.NET NetworkManager[1190]: <info> [1496530504.6203] manager: NetworkManager state is now CONNECTED_LOCAL
Jun 03 18:55:04 PC4399N.WS.WSFGRP.NET NetworkManager[1190]: <info> [1496530504.6223] manager: NetworkManager state is now CONNECTED_SITE
Jun 03 18:55:04 PC4399N.WS.WSFGRP.NET NetworkManager[1190]: <info> [1496530504.6225] policy: set ‘Oscitsox_Plus’ (wlo1) as default for IPv4 routing a
Jun 03 18:55:04 PC4399N.WS.WSFGRP.NET NetworkManager[1190]: <13>Jun 3 18:55:04 dns-resolver: ATTENTION: You have modified /etc/resolv.conf. Leaving i
Jun 03 18:55:04 PC4399N.WS.WSFGRP.NET NetworkManager[1190]: <13>Jun 3 18:55:04 dns-resolver: You can find my version in /etc/resolv.conf.netconfig
Jun 03 18:55:04 PC4399N.WS.WSFGRP.NET NetworkManager[1190]: ATTENTION: You have modified /etc/resolv.conf. Leaving it untouched…
Jun 03 18:55:04 PC4399N.WS.WSFGRP.NET NetworkManager[1190]: You can find my version in /etc/resolv.conf.netconfig …
Jun 03 18:55:04 PC4399N.WS.WSFGRP.NET NetworkManager[1190]: nisdomainname: you must be root to change the domain name
Jun 03 18:55:04 PC4399N.WS.WSFGRP.NET NetworkManager[1190]: <warn> [1496530504.7891] dns-mgr: could not commit DNS changes: Error calling netconfig:
Jun 03 18:55:04 PC4399N.WS.WSFGRP.NET NetworkManager[1190]: <info> [1496530504.7892] device (wlo1): Activation: successful, device activated.
Jun 03 18:55:05 PC4399N.WS.WSFGRP.NET NetworkManager[1190]: <info> [1496530505.0863] manager: NetworkManager state is now CONNECTED_GLOBAL
lines 246-282/282 (END)

Not sure what I am looking for.

#5

I just went back to LEAP. I need a stable system but thought Tumbleweed could provide that seeing all the positive comments. The LEAP installation everything is working just fine. Guess I’ll run Tubleweed in a VM.

#6

There was nothing in the log snippet that you submitted that suggested any real issue with getting connected (other than /etc/resolv had been modified apparently so NM won’t touch it). Anyway, if Leap is working for you (as it does me) that is good.