Network(Manager) problems after messing with netctl

Lacsapix · 2014-09-11 15:32:43

Hello, and thanks for taking time helping me!

The story so far:
I was trying to bridge my wired and wireless network on my laptop, using netctl: https://wiki.archlinux.org/index.php/Bridge_with_netctl

It dind't worked and it messed my network up (I could see the wifi-indicator in the topright of my screen frozen in its "connecting" state), but I could still use wifi.

So I removed netctl and deleted its files from /etc/netctl and disabled/stopped the zombie-bridge. And then I could not connect wireless anymore (wired still works altough still frozen in the "connecting" state according to Gnome).

My system:
PC: An Acer aspire v3 laptop
OS: Arch x86_64
DE: Gnome-Shell
using NetworkManager as a.... NetworkManager I

the bridge I was trying to make:

Description="Example Bridge connection"
Interface=br0
Connection=bridge
BindsToInterfaces=(wlp3s0 enp2s0f0)
IP=dhcp

some logs (# systemctl status NetworkManager):

Sep 11 17:15:16 Skynet NetworkManager[299]: <info> Activation (wlp3s0) Stage 3 of 5 (IP Configure Start) started...
Sep 11 17:15:16 Skynet NetworkManager[299]: <info> (wlp3s0): device state change: config -> ip-config (reason 'none') [50 70 0]
Sep 11 17:15:16 Skynet NetworkManager[299]: <info> Activation (wlp3s0) Beginning DHCPv4 transaction (timeout in 45 seconds)
Sep 11 17:15:16 Skynet NetworkManager[299]: <info> dhcpcd started with pid 1415
Sep 11 17:15:16 Skynet NetworkManager[299]: <info> Activation (wlp3s0) Stage 3 of 5 (IP Configure Start) complete.
Sep 11 17:15:16 Skynet NetworkManager[299]: <info> (wlp3s0): DHCPv4 client pid 1415 exited with status 0
Sep 11 17:15:16 Skynet NetworkManager[299]: <info> Activation (wlp3s0) Stage 4 of 5 (IPv4 Configure Timeout) scheduled...
Sep 11 17:15:16 Skynet NetworkManager[299]: <info> Activation (wlp3s0) Stage 4 of 5 (IPv4 Configure Timeout) started...
Sep 11 17:15:16 Skynet NetworkManager[299]: <info> Activation (wlp3s0) Stage 4 of 5 (IPv4 Configure Timeout) complete.
Sep 11 17:15:16 Skynet NetworkManager[299]: dhcpcd[1415]: sending commands to master dhcpcd process
Sep 11 17:15:22 Skynet NetworkManager[299]: <info> Activation (wlp3s0) Stage 4 of 5 (IPv6 Configure Timeout) started...
Sep 11 17:15:22 Skynet NetworkManager[299]: <info> (wlp3s0): device state change: ip-config -> failed (reason 'ip-config-unavailable') [70 120 5]
Sep 11 17:15:22 Skynet NetworkManager[299]: <info> NetworkManager state is now DISCONNECTED
Sep 11 17:15:22 Skynet NetworkManager[299]: <info> Disabling autoconnect for connection 'Starfleet'.
Sep 11 17:15:22 Skynet NetworkManager[299]: <warn> Activation (wlp3s0) failed for connection 'Starfleet'
Sep 11 17:15:22 Skynet NetworkManager[299]: <info> Activation (wlp3s0) Stage 4 of 5 (IPv6 Configure Timeout) complete.
Sep 11 17:15:22 Skynet NetworkManager[299]: <info> (wlp3s0): device state change: failed -> disconnected (reason 'none') [120 30 0]
Sep 11 17:15:22 Skynet NetworkManager[299]: <info> (wlp3s0): deactivating device (reason 'none') [0]
Sep 11 17:15:22 Skynet NetworkManager[299]: <warn> Connection disconnected (reason -3)
Sep 11 17:15:22 Skynet NetworkManager[299]: <info> (wlp3s0): supplicant interface state: completed -> disconnected

My guess is that somewhere my bridge messed everything up. But as I've leared with arch the awser could be very simple.
Thanks Again,
Pascal

Lacsapix · 2014-09-12 08:45:34

I think I know what the problem is. I saw that a deamon called dhcpcd@wlp3S0 was running at the same time NetworkManager was. This would mean that both Networkmanager and netctl where running at the same time. I've disabled "dhcpcd@wlp3s0" and........ nothing.
Does anyone knows witch daemons i should disable/enable to let the system run on networkmanager alone?

jasonwryan · 2014-09-12 08:53:36

https://wiki.archlinux.org/index.php/Ne … orkManager

Arch Linux

#1 2014-09-11 15:32:43

Network(Manager) problems after messing with netctl

#2 2014-09-12 08:45:34

Re: Network(Manager) problems after messing with netctl

#3 2014-09-12 08:53:36

Re: Network(Manager) problems after messing with netctl

Board footer