You are not logged in.

Pages: 1

#1 2018-06-07 13:40:09

niezniszczalny
Member
Registered: 2015-12-11
Posts: 66

[SOLVED] Cannot connect via network manager (both wired & wireless)

Last weekend my system stopped connecting to Internet via either wireless and ethernet interface. When I plug phone via USB, nmcli has no problem connecting. Also 'dhcpd en0s25' works.

$ nmcli dev connect enp0s25
Error: Connection activation failed: (54) A secondary connection of the base connection failed.
$ ip link
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
2: enp0s25: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP mode DEFAULT group default qlen 1000
    link/ether 48:0f:cf:23:0a:fd brd ff:ff:ff:ff:ff:ff
3: wlo1: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc mq state DOWN mode DORMANT group default qlen 1000
    link/ether be:13:f5:fb:b2:3f brd ff:ff:ff:ff:ff:ff
4: docker0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN mode DEFAULT group default 
    link/ether 02:42:46:11:0f:d8 brd ff:ff:ff:ff:ff:ff

When I was installing Arch some time ago, my ethernet interface's name was "eth0", now it's being renamed to "enp0s25". Also my wireless interface is renamed:

$ dmesg | grep e1000e
[   15.461620] e1000e: Intel(R) PRO/1000 Network Driver - 3.2.6-k
[   15.461621] e1000e: Copyright(c) 1999 - 2015 Intel Corporation.
[   15.461944] e1000e 0000:00:19.0: Interrupt Throttling Rate (ints/sec) set to dynamic conservative mode
[   15.552078] e1000e 0000:00:19.0 0000:00:19.0 (uninitialized): registered PHC clock
[   15.647737] e1000e 0000:00:19.0 eth0: (PCI Express:2.5GT/s:Width x1) 48:0f:cf:23:0a:fd
[   15.647745] e1000e 0000:00:19.0 eth0: Intel(R) PRO/1000 Network Connection
[   15.647790] e1000e 0000:00:19.0 eth0: MAC: 11, PHY: 12, PBA No: FFFFFF-0FF
[   15.788021] e1000e 0000:00:19.0 enp0s25: renamed from eth0
[  104.432260] e1000e: enp0s25 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: Rx/Tx
[  767.941750] e1000e: enp0s25 NIC Link is Down
[  771.923988] e1000e: enp0s25 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: Rx/Tx
[ 1065.334491] e1000e: enp0s25 NIC Link is Down
[ 1069.553191] e1000e: enp0s25 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: Rx/Tx
$ dmesg | grep iwlwifi
[   15.592855] iwlwifi 0000:02:00.0: enabling device (0000 -> 0002)
[   15.614297] iwlwifi 0000:02:00.0: loaded firmware version 17.948900127.0 op_mode iwlmvm
[   15.705501] iwlwifi 0000:02:00.0: Detected Intel(R) Dual Band Wireless AC 7260, REV=0x144
[   15.724841] iwlwifi 0000:02:00.0: base HW address: 7c:5c:f8:a5:f8:f2
[   15.932393] iwlwifi 0000:02:00.0 wlo1: renamed from wlan0

Any advice?

Last edited by niezniszczalny (2018-06-07 15:56:49)

Offline

#2 2018-06-07 14:46:34

seth
Member
Registered: 2012-09-03
Posts: 51,132

Re: [SOLVED] Cannot connect via network manager (both wired & wireless)

The interesting information will rather be in the journal than in dmesg (since the device works and this is a problem w/ NM)

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

Offline

#3 2018-06-07 15:19:52

niezniszczalny
Member
Registered: 2015-12-11
Posts: 66

Re: [SOLVED] Cannot connect via network manager (both wired & wireless)

Jun 07 17:04:42 kujawLap NetworkManager[3119]: <info>  [1528383882.4715] policy: auto-activating connection 'Auto Ethernet'
Jun 07 17:04:42 kujawLap NetworkManager[3119]: <info>  [1528383882.4724] device (enp0s25): Activation: starting connection 'Auto Ethernet' (358a5792-f9a1-420f-9c5e-59d4a17161f5)
Jun 07 17:04:42 kujawLap NetworkManager[3119]: <info>  [1528383882.4725] device (enp0s25): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed')
Jun 07 17:04:42 kujawLap NetworkManager[3119]: <info>  [1528383882.4728] device (enp0s25): state change: prepare -> config (reason 'none', sys-iface-state: 'managed')
Jun 07 17:04:42 kujawLap NetworkManager[3119]: <info>  [1528383882.4732] device (enp0s25): state change: config -> ip-config (reason 'none', sys-iface-state: 'managed')
Jun 07 17:04:42 kujawLap NetworkManager[3119]: <info>  [1528383882.4736] dhcp4 (enp0s25): activation: beginning transaction (timeout in 45 seconds)
Jun 07 17:04:42 kujawLap NetworkManager[3119]: <info>  [1528383882.5003] dhcp4 (enp0s25):   address 10.3.159.7
Jun 07 17:04:42 kujawLap NetworkManager[3119]: <info>  [1528383882.5003] dhcp4 (enp0s25):   plen 21
Jun 07 17:04:42 kujawLap NetworkManager[3119]: <info>  [1528383882.5003] dhcp4 (enp0s25):   expires in 172800 seconds
Jun 07 17:04:42 kujawLap NetworkManager[3119]: <info>  [1528383882.5004] dhcp4 (enp0s25):   nameserver '217.113.224.36'
Jun 07 17:04:42 kujawLap NetworkManager[3119]: <info>  [1528383882.5004] dhcp4 (enp0s25):   nameserver '217.113.224.134'
Jun 07 17:04:42 kujawLap NetworkManager[3119]: <info>  [1528383882.5004] dhcp4 (enp0s25):   domain name 'toya.net.pl'
Jun 07 17:04:42 kujawLap NetworkManager[3119]: <info>  [1528383882.5004] dhcp4 (enp0s25):   gateway 10.3.152.1
Jun 07 17:04:42 kujawLap NetworkManager[3119]: <info>  [1528383882.5007] dhcp4 (enp0s25): state changed unknown -> bound
Jun 07 17:04:42 kujawLap NetworkManager[3119]: <info>  [1528383882.5024] device (enp0s25): state change: ip-config -> ip-check (reason 'none', sys-iface-state: 'managed')
Jun 07 17:04:42 kujawLap NetworkManager[3119]: <info>  [1528383882.5036] device (enp0s25): state change: ip-check -> secondaries (reason 'none', sys-iface-state: 'managed')
Jun 07 17:04:42 kujawLap NetworkManager[3119]: <warn>  [1528383882.5038] policy: secondary connection '151e5056-a0f3-4494-8724-60fefcaf51e9' auto-activation failed: The connection doesn't exist.
Jun 07 17:04:42 kujawLap NetworkManager[3119]: <info>  [1528383882.5040] device (enp0s25): state change: secondaries -> failed (reason 'secondary-connection-failed', sys-iface-state: 'managed')
Jun 07 17:04:42 kujawLap NetworkManager[3119]: <warn>  [1528383882.5045] device (enp0s25): Activation: failed for connection 'Auto Ethernet'
Jun 07 17:04:42 kujawLap NetworkManager[3119]: <info>  [1528383882.5053] device (enp0s25): state change: failed -> disconnected (reason 'none', sys-iface-state: 'managed')
Jun 07 17:04:42 kujawLap NetworkManager[3119]: <info>  [1528383882.5060] dhcp4 (enp0s25): canceled DHCP transaction
Jun 07 17:04:42 kujawLap NetworkManager[3119]: <info>  [1528383882.5061] dhcp4 (enp0s25): state changed bound -> done
Jun 07 17:04:42 kujawLap NetworkManager[3119]: <info>  [1528383882.5118] policy: auto-activating connection 'Auto Ethernet'
Jun 07 17:04:42 kujawLap NetworkManager[3119]: <info>  [1528383882.5127] device (enp0s25): Activation: starting connection 'Auto Ethernet' (358a5792-f9a1-420f-9c5e-59d4a17161f5)
Jun 07 17:04:42 kujawLap NetworkManager[3119]: <info>  [1528383882.5128] device (enp0s25): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed')
Jun 07 17:04:42 kujawLap NetworkManager[3119]: <info>  [1528383882.5132] device (enp0s25): state change: prepare -> config (reason 'none', sys-iface-state: 'managed')
Jun 07 17:04:42 kujawLap NetworkManager[3119]: <info>  [1528383882.5137] device (enp0s25): state change: config -> ip-config (reason 'none', sys-iface-state: 'managed')
Jun 07 17:04:42 kujawLap NetworkManager[3119]: <info>  [1528383882.5140] dhcp4 (enp0s25): activation: beginning transaction (timeout in 45 seconds)
Jun 07 17:04:42 kujawLap NetworkManager[3119]: <info>  [1528383882.5544] dhcp4 (enp0s25):   address 10.3.159.7
Jun 07 17:04:42 kujawLap NetworkManager[3119]: <info>  [1528383882.5544] dhcp4 (enp0s25):   plen 21
Jun 07 17:04:42 kujawLap NetworkManager[3119]: <info>  [1528383882.5545] dhcp4 (enp0s25):   expires in 172800 seconds
Jun 07 17:04:42 kujawLap NetworkManager[3119]: <info>  [1528383882.5545] dhcp4 (enp0s25):   nameserver '217.113.224.36'
Jun 07 17:04:42 kujawLap NetworkManager[3119]: <info>  [1528383882.5545] dhcp4 (enp0s25):   nameserver '217.113.224.134'
Jun 07 17:04:42 kujawLap NetworkManager[3119]: <info>  [1528383882.5546] dhcp4 (enp0s25):   domain name 'toya.net.pl'
Jun 07 17:04:42 kujawLap NetworkManager[3119]: <info>  [1528383882.5546] dhcp4 (enp0s25):   gateway 10.3.152.1
Jun 07 17:04:42 kujawLap NetworkManager[3119]: <info>  [1528383882.5550] dhcp4 (enp0s25): state changed unknown -> bound
Jun 07 17:04:42 kujawLap NetworkManager[3119]: <info>  [1528383882.5574] device (enp0s25): state change: ip-config -> ip-check (reason 'none', sys-iface-state: 'managed')
Jun 07 17:04:42 kujawLap NetworkManager[3119]: <info>  [1528383882.5589] device (enp0s25): state change: ip-check -> secondaries (reason 'none', sys-iface-state: 'managed')
Jun 07 17:04:42 kujawLap NetworkManager[3119]: <warn>  [1528383882.5591] policy: secondary connection '151e5056-a0f3-4494-8724-60fefcaf51e9' auto-activation failed: The connection doesn't exist.
Jun 07 17:04:42 kujawLap NetworkManager[3119]: <info>  [1528383882.5593] device (enp0s25): state change: secondaries -> failed (reason 'secondary-connection-failed', sys-iface-state: 'managed')
Jun 07 17:04:42 kujawLap NetworkManager[3119]: <warn>  [1528383882.5598] device (enp0s25): Activation: failed for connection 'Auto Ethernet'
Jun 07 17:04:42 kujawLap NetworkManager[3119]: <info>  [1528383882.5606] device (enp0s25): state change: failed -> disconnected (reason 'none', sys-iface-state: 'managed')
Jun 07 17:04:42 kujawLap NetworkManager[3119]: <info>  [1528383882.5612] dhcp4 (enp0s25): canceled DHCP transaction
Jun 07 17:04:42 kujawLap NetworkManager[3119]: <info>  [1528383882.5613] dhcp4 (enp0s25): state changed bound -> done
lines 6072-6131/6131 (END)

I set it to connect automatically, this is part of journalctl, all the time repeating.

Offline

#4 2018-06-07 15:50:56

niezniszczalny
Member
Registered: 2015-12-11
Posts: 66

Re: [SOLVED] Cannot connect via network manager (both wired & wireless)

Suddenly it connected. Threw an error, but works ok.

Jun 07 17:36:21 kujawLap NetworkManager[3119]: <info>  [1528385781.5624] device (enp0s25): Activation: starting connection 'Auto Ethernet' (d93574aa-7c72-433b-974c-071475c2e406)
Jun 07 17:36:21 kujawLap NetworkManager[3119]: <info>  [1528385781.5625] audit: op="connection-activate" uuid="d93574aa-7c72-433b-974c-071475c2e406" name="Auto Ethernet" pid=3616 uid=1000 result="success"
Jun 07 17:36:21 kujawLap NetworkManager[3119]: <info>  [1528385781.5627] device (enp0s25): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed')
Jun 07 17:36:21 kujawLap NetworkManager[3119]: <info>  [1528385781.5629] manager: NetworkManager state is now CONNECTING
Jun 07 17:36:21 kujawLap NetworkManager[3119]: <info>  [1528385781.5632] device (enp0s25): state change: prepare -> config (reason 'none', sys-iface-state: 'managed')
Jun 07 17:36:21 kujawLap NetworkManager[3119]: <info>  [1528385781.5638] device (enp0s25): state change: config -> ip-config (reason 'none', sys-iface-state: 'managed')
Jun 07 17:36:21 kujawLap NetworkManager[3119]: <info>  [1528385781.5640] dhcp4 (enp0s25): activation: beginning transaction (timeout in 45 seconds)
Jun 07 17:36:21 kujawLap NetworkManager[3119]: <info>  [1528385781.5957] dhcp4 (enp0s25):   address 10.3.159.7
Jun 07 17:36:21 kujawLap NetworkManager[3119]: <info>  [1528385781.5958] dhcp4 (enp0s25):   plen 21
Jun 07 17:36:21 kujawLap NetworkManager[3119]: <info>  [1528385781.5958] dhcp4 (enp0s25):   expires in 172800 seconds
Jun 07 17:36:21 kujawLap NetworkManager[3119]: <info>  [1528385781.5958] dhcp4 (enp0s25):   nameserver '217.113.224.36'
Jun 07 17:36:21 kujawLap NetworkManager[3119]: <info>  [1528385781.5959] dhcp4 (enp0s25):   nameserver '217.113.224.134'
Jun 07 17:36:21 kujawLap NetworkManager[3119]: <info>  [1528385781.5959] dhcp4 (enp0s25):   domain name 'toya.net.pl'
Jun 07 17:36:21 kujawLap NetworkManager[3119]: <info>  [1528385781.5959] dhcp4 (enp0s25):   gateway 10.3.152.1
Jun 07 17:36:21 kujawLap NetworkManager[3119]: <info>  [1528385781.5963] dhcp4 (enp0s25): state changed unknown -> bound
Jun 07 17:36:21 kujawLap NetworkManager[3119]: <info>  [1528385781.5979] device (enp0s25): state change: ip-config -> ip-check (reason 'none', sys-iface-state: 'managed')
Jun 07 17:36:21 kujawLap NetworkManager[3119]: <info>  [1528385781.5993] device (enp0s25): state change: ip-check -> secondaries (reason 'none', sys-iface-state: 'managed')
Jun 07 17:36:21 kujawLap NetworkManager[3119]: <info>  [1528385781.5998] device (enp0s25): state change: secondaries -> activated (reason 'none', sys-iface-state: 'managed')
Jun 07 17:36:21 kujawLap NetworkManager[3119]: <info>  [1528385781.6000] manager: NetworkManager state is now CONNECTED_LOCAL
Jun 07 17:36:21 kujawLap geoclue[1007]: Failed to query location: Error resolving “location.services.mozilla.com”: Temporary failure in name resolution
Jun 07 17:36:21 kujawLap NetworkManager[3119]: <info>  [1528385781.6095] manager: NetworkManager state is now CONNECTED_SITE
Jun 07 17:36:21 kujawLap NetworkManager[3119]: <info>  [1528385781.6096] policy: set 'Auto Ethernet' (enp0s25) as default for IPv4 routing and DNS
Jun 07 17:36:21 kujawLap NetworkManager[3119]: <info>  [1528385781.6120] device (enp0s25): Activation: successful, device activated.
Jun 07 17:36:21 kujawLap dbus-daemon[487]: [system] Activating via systemd: service name='org.freedesktop.nm_dispatcher' unit='dbus-org.freedesktop.nm-dispatcher.service' requested by ':1.260' (uid=0 pid=3119 comm="/usr/bin/NetworkManage>
Jun 07 17:36:21 kujawLap systemd[1]: Starting Network Manager Script Dispatcher Service...
Jun 07 17:36:21 kujawLap dbus-daemon[487]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher'
Jun 07 17:36:21 kujawLap systemd[1]: Started Network Manager Script Dispatcher Service.
Jun 07 17:36:21 kujawLap nm-dispatcher[6877]: req:1 'up' [enp0s25]: new request (0 scripts)
Jun 07 17:36:21 kujawLap nm-dispatcher[6877]: req:1 'up' [enp0s25]: completed: no scripts
Jun 07 17:36:21 kujawLap NetworkManager[3119]: <info>  [1528385781.7142] manager: NetworkManager state is now CONNECTED_GLOBAL
Jun 07 17:36:21 kujawLap nm-dispatcher[6877]: req:2 'connectivity-change': new request (0 scripts)
Jun 07 17:36:21 kujawLap nm-dispatcher[6877]: req:2 'connectivity-change': completed: no scripts
Jun 07 17:36:23 kujawLap ntpd[503]: Listen normally on 53 enp0s25 10.3.159.7:123
Jun 07 17:36:23 kujawLap ntpd[503]: bind(24) AF_INET6 fe80::6ff2:7bed:d92b:1ca%2#123 flags 0x11 failed: Cannot assign requested address
Jun 07 17:36:23 kujawLap ntpd[503]: unable to create socket on enp0s25 (54) for fe80::6ff2:7bed:d92b:1ca%2#123
Jun 07 17:36:23 kujawLap ntpd[503]: failed to init interface for address fe80::6ff2:7bed:d92b:1ca%2
Jun 07 17:36:23 kujawLap ntpd[503]: new interface(s) found: waking up resolver
lines 7539-7598/7598 (END)

Now I'll be fighting with wireless. Hopefully reboot will help.

Offline

#5 2018-06-07 15:55:47

niezniszczalny
Member
Registered: 2015-12-11
Posts: 66

Re: [SOLVED] Cannot connect via network manager (both wired & wireless)

Wireless also works now. I don't know what happened, 1 hr ago it didn't connect, even after networkmanager reinstallation, restarting services etc.
Problem solved.

Offline

#6 2018-06-07 16:34:44

V1del
Forum Moderator
Registered: 2012-10-16
Posts: 21,707

Re: [SOLVED] Cannot connect via network manager (both wired & wireless)

It could also just be an issue with NM's internal dhcp client, try to switch that to something more mature: https://wiki.archlinux.org/index.php/Ne … HCP_client

Offline

#7 2018-06-08 10:33:50

niezniszczalny
Member
Registered: 2015-12-11
Posts: 66

Re: [SOLVED] Cannot connect via network manager (both wired & wireless)

Oh yes, last thing I've installed was dhclient, but I didn't create or change dhcp-client.conf file as instructed in the link. How to check wchich DHCP client is NetworkManager using? In the global configuration file (/etc/NetworkManager/NetworkManager.conf) there is nothing besides some commented information about the file.

Offline

#8 2018-06-08 10:37:34

seth
Member
Registered: 2012-09-03
Posts: 51,132

Re: [SOLVED] Cannot connect via network manager (both wired & wireless)

It will use the internal dhcp client by default
This is also indicated by the 

NetworkManager[3119]: <info>  [1528385781.5963] dhcp4

lines.

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

Offline

Pages: 1

Board footer

Powered by FluxBB