[Solved] NetworkManager deauthenticating?

NetworkManager is not connecting, however I connect fine with
sudo ip link set wlp6s7 up && sudo wifi-menu
dmesg after trying to connect a few times:
156.025351] wlp6s7: authenticate with 00:0f:b3:48:5a:57
[ 156.030144] wlp6s7: send auth to 00:0f:b3:48:5a:57 (try 1/3)
[ 156.031577] wlp6s7: authenticated
[ 156.031786] rt2800pci 0000:06:07.0 wlp6s7: disabling HT/VHT due to WEP/TKIP use
[ 156.031794] rt2800pci 0000:06:07.0 wlp6s7: disabling HT as WMM/QoS is not supported by the AP
[ 156.031802] rt2800pci 0000:06:07.0 wlp6s7: disabling VHT as WMM/QoS is not supported by the AP
[ 156.034511] wlp6s7: associate with 00:0f:b3:48:5a:57 (try 1/3)
[ 156.036589] wlp6s7: RX AssocResp from 00:0f:b3:48:5a:57 (capab=0x471 status=0 aid=2)
[ 156.036943] wlp6s7: associated
[ 156.040422] IPv6: ADDRCONF(NETDEV_CHANGE): wlp6s7: link becomes ready
[ 156.079170] wlp6s7: deauthenticating from 00:0f:b3:48:5a:57 by local choice (reason=3)
[ 156.095143] cfg80211: Calling CRDA to update world regulatory domain
[ 159.411994] wlp6s7: authenticate with 00:0f:b3:48:5a:57
[ 159.416800] wlp6s7: send auth to 00:0f:b3:48:5a:57 (try 1/3)
[ 159.418114] wlp6s7: authenticated
[ 159.418314] rt2800pci 0000:06:07.0 wlp6s7: disabling HT/VHT due to WEP/TKIP use
[ 159.418321] rt2800pci 0000:06:07.0 wlp6s7: disabling HT as WMM/QoS is not supported by the AP
[ 159.418325] rt2800pci 0000:06:07.0 wlp6s7: disabling VHT as WMM/QoS is not supported by the AP
[ 159.420990] wlp6s7: associate with 00:0f:b3:48:5a:57 (try 1/3)
[ 159.422759] wlp6s7: RX AssocResp from 00:0f:b3:48:5a:57 (capab=0x471 status=0 aid=2)
[ 159.423087] wlp6s7: associated
[ 159.467443] wlp6s7: deauthenticating from 00:0f:b3:48:5a:57 by local choice (reason=3)
Anyone know what might be causing this? (or how to fix it?)
Last edited by gandalf3 (2013-06-02 21:28:40)

Nothing I have found so far has worked.
I don't have wicd or netcfg installed, and I don't think it's a drivers issue as I can connect with wifi-menu..
I'll keep searching..
Last edited by gandalf3 (2013-05-21 19:06:48)

Similar Messages

[SOLVED] NetworkManager dumped core

Symptoms: WiFi randomly drops out.
More specifically: NetworkManager core dumps and network-manager-applet stops (Gnome 3.8)
If anyone has suggestions, I'd be grateful. I'm at a loss, other than disabling NetworkManager and enabling netctl. Details follow below.
Thanks so much!
uname -r
3.9.0-2-ARCH
uname -m
x86_64
lspci -v
Network controller: Intel Corporation Centrino Advanced-N 6205
rfkill list
0: tpacpi_bluetooth_sw: Bluetooth
Soft blocked: no
Hard blocked: no
1: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
2: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
iwconfig
enp0s25 no wireless extensions.
wlp3s0 IEEE 802.11abgn ESSID:"The Way 5GHz"
Mode:Managed Frequency:5.18 GHz Access Point: 00:26:F2:F2:E7:D5
Bit Rate=65 Mb/s Tx-Power=15 dBm
Retry long limit:7 RTS thr:off Fragment thr:off
Power Management:off
Link Quality=54/70 Signal level=-56 dBm
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:230 Invalid misc:113 Missed beacon:0
lo no wireless extensions.
journalctl -u NetworkManager --since=today
-- Reboot --
May 04 14:04:19 arch systemd[1]: Starting Network Manager...
May 04 14:04:20 arch NetworkManager[284]: <info> NetworkManager (version 0.9.8.0) is starting...
May 04 14:04:20 arch NetworkManager[284]: <info> Read config file /etc/NetworkManager/NetworkManager.conf
May 04 14:04:20 arch NetworkManager[284]: <info> WEXT support is enabled
May 04 14:04:21 arch NetworkManager[284]: <info> Loaded plugin keyfile: (c) 2007 - 2010 Red Hat, Inc. To report bugs please use the NetworkManager ma
May 04 14:04:21 arch NetworkManager[284]: keyfile: parsing Auto The Way 5GHz ...
May 04 14:04:21 arch NetworkManager[284]: keyfile: read connection 'Auto The Way 5GHz'
May 04 14:04:21 arch NetworkManager[284]: <info> monitoring kernel firmware directory '/lib/firmware'.
May 04 14:04:21 arch NetworkManager[284]: <info> rfkill1: found WiFi radio killswitch (at /sys/devices/pci0000:00/0000:00:1c.1/0000:03:00.0/ieee80211/
May 04 14:04:21 arch NetworkManager[284]: <info> WiFi hardware radio set enabled
May 04 14:04:21 arch systemd[1]: Started Network Manager.
May 04 14:04:21 arch NetworkManager[284]: <info> WiFi enabled by radio killswitch; enabled by state file
May 04 14:04:21 arch NetworkManager[284]: <info> WWAN enabled by radio killswitch; enabled by state file
May 04 14:04:21 arch NetworkManager[284]: <info> WiMAX enabled by radio killswitch; enabled by state file
May 04 14:04:21 arch NetworkManager[284]: <info> Networking is enabled by state file
May 04 14:04:21 arch NetworkManager[284]: <warn> failed to allocate link cache: (-10) Operation not supported
May 04 14:04:21 arch NetworkManager[284]: <info> (enp0s25): carrier is OFF
May 04 14:04:21 arch NetworkManager[284]: <info> (enp0s25): new Ethernet device (driver: 'e1000e' ifindex: 3)
May 04 14:04:21 arch NetworkManager[284]: <info> (enp0s25): exported as /org/freedesktop/NetworkManager/Devices/0
May 04 14:04:21 arch NetworkManager[284]: <info> (enp0s25): device state change: unmanaged -> unavailable (reason 'managed') [10 20 2]
May 04 14:04:21 arch NetworkManager[284]: <info> (enp0s25): bringing up device.
May 04 14:04:21 arch NetworkManager[284]: <info> (enp0s25): preparing device.
May 04 14:04:21 arch NetworkManager[284]: <info> (enp0s25): deactivating device (reason 'managed') [2]
May 04 14:04:21 arch NetworkManager[284]: <info> Added default wired connection 'Wired connection 1' for /sys/devices/pci0000:00/0000:00:19.0/net/enp0
May 04 14:04:21 arch NetworkManager[284]: <info> (wlp3s0): using nl80211 for WiFi device control
May 04 14:04:21 arch NetworkManager[284]: <info> (wlp3s0): driver supports Access Point (AP) mode
May 04 14:04:21 arch NetworkManager[284]: <info> (wlp3s0): new 802.11 WiFi device (driver: 'iwlwifi' ifindex: 2)
May 04 14:04:21 arch NetworkManager[284]: <info> (wlp3s0): exported as /org/freedesktop/NetworkManager/Devices/1
May 04 14:04:21 arch NetworkManager[284]: <info> (wlp3s0): device state change: unmanaged -> unavailable (reason 'managed') [10 20 2]
May 04 14:04:21 arch NetworkManager[284]: <info> (wlp3s0): bringing up device.
May 04 14:04:21 arch NetworkManager[284]: <info> (wlp3s0): preparing device.
May 04 14:04:21 arch NetworkManager[284]: <info> (wlp3s0): deactivating device (reason 'managed') [2]
May 04 14:04:21 arch NetworkManager[284]: <warn> /sys/devices/virtual/net/lo: couldn't determine device driver; ignoring...
May 04 14:04:21 arch NetworkManager[284]: <warn> /sys/devices/virtual/net/lo: couldn't determine device driver; ignoring...
May 04 14:04:21 arch NetworkManager[284]: <warn> error poking ModemManager: GDBus.Error:org.freedesktop.systemd1.LoadFailed: Unit dbus-org.freedesktop
May 04 14:04:21 arch NetworkManager[284]: <info> wpa_supplicant started
May 04 14:04:21 arch NetworkManager[284]: <info> (wlp3s0) supports 5 scan SSIDs
May 04 14:04:21 arch NetworkManager[284]: <warn> Trying to remove a non-existant call id.
May 04 14:04:21 arch NetworkManager[284]: <info> (wlp3s0): supplicant interface state: starting -> ready
May 04 14:04:21 arch NetworkManager[284]: <info> (wlp3s0): device state change: unavailable -> disconnected (reason 'supplicant-available') [20 30 42]
May 04 14:04:21 arch NetworkManager[284]: <info> (wlp3s0): supplicant interface state: ready -> disconnected
May 04 14:04:21 arch NetworkManager[284]: <info> (wlp3s0) supports 5 scan SSIDs
May 04 14:04:25 arch NetworkManager[284]: <info> (wlp3s0): supplicant interface state: disconnected -> inactive
May 04 14:04:25 arch NetworkManager[284]: <info> Auto-activating connection 'Auto The Way 5GHz'.
May 04 14:04:25 arch NetworkManager[284]: <info> Activation (wlp3s0) starting connection 'Auto The Way 5GHz'
May 04 14:04:25 arch NetworkManager[284]: <info> (wlp3s0): device state change: disconnected -> prepare (reason 'none') [30 40 0]
May 04 14:04:25 arch NetworkManager[284]: <info> Activation (wlp3s0) Stage 1 of 5 (Device Prepare) scheduled...
May 04 14:04:25 arch NetworkManager[284]: <info> Activation (wlp3s0) Stage 1 of 5 (Device Prepare) started...
May 04 14:04:25 arch NetworkManager[284]: <info> Activation (wlp3s0) Stage 2 of 5 (Device Configure) scheduled...
May 04 14:04:25 arch NetworkManager[284]: <info> Activation (wlp3s0) Stage 1 of 5 (Device Prepare) complete.
May 04 14:04:25 arch NetworkManager[284]: <info> Activation (wlp3s0) Stage 2 of 5 (Device Configure) starting...
May 04 14:04:25 arch NetworkManager[284]: <info> (wlp3s0): device state change: prepare -> config (reason 'none') [40 50 0]
May 04 14:04:25 arch NetworkManager[284]: <info> Activation (wlp3s0/wireless): connection 'Auto The Way 5GHz' has security, and secrets exist. No new
May 04 14:04:25 arch NetworkManager[284]: <info> Config: added 'ssid' value 'The Way 5GHz'
May 04 14:04:25 arch NetworkManager[284]: <info> Config: added 'scan_ssid' value '1'
May 04 14:04:25 arch NetworkManager[284]: <info> Config: added 'key_mgmt' value 'WPA-PSK'
May 04 14:04:25 arch NetworkManager[284]: <info> Config: added 'auth_alg' value 'OPEN'
May 04 14:04:25 arch NetworkManager[284]: <info> Config: added 'psk' value '<omitted>'
May 04 14:04:25 arch NetworkManager[284]: <info> Activation (wlp3s0) Stage 2 of 5 (Device Configure) complete.
May 04 14:04:25 arch NetworkManager[284]: <info> Config: set interface ap_scan to 1
May 04 14:04:25 arch NetworkManager[284]: <info> (wlp3s0): supplicant interface state: inactive -> scanning
May 04 14:04:28 arch NetworkManager[284]: <info> (wlp3s0): supplicant interface state: scanning -> authenticating
May 04 14:04:28 arch NetworkManager[284]: <info> (wlp3s0): supplicant interface state: authenticating -> associating
May 04 14:04:28 arch NetworkManager[284]: <info> (wlp3s0): supplicant interface state: associating -> associated
May 04 14:04:28 arch NetworkManager[284]: <info> (wlp3s0): supplicant interface state: associated -> completed
May 04 14:04:28 arch NetworkManager[284]: <info> Activation (wlp3s0/wireless) Stage 2 of 5 (Device Configure) successful. Connected to wireless netwo
May 04 14:04:28 arch NetworkManager[284]: <info> Activation (wlp3s0) Stage 3 of 5 (IP Configure Start) scheduled.
May 04 14:04:28 arch NetworkManager[284]: <info> Activation (wlp3s0) Stage 3 of 5 (IP Configure Start) started...
May 04 14:04:28 arch NetworkManager[284]: <info> (wlp3s0): device state change: config -> ip-config (reason 'none') [50 70 0]
May 04 14:04:28 arch NetworkManager[284]: <info> Activation (wlp3s0) Beginning DHCPv4 transaction (timeout in 45 seconds)
May 04 14:04:28 arch NetworkManager[284]: <info> dhcpcd started with pid 447
May 04 14:04:28 arch NetworkManager[284]: <info> Activation (wlp3s0) Beginning IP6 addrconf.
May 04 14:04:28 arch NetworkManager[284]: <info> Activation (wlp3s0) Stage 3 of 5 (IP Configure Start) complete.
May 04 14:04:28 arch dhcpcd[447]: version 5.6.8 starting
May 04 14:04:28 arch dhcpcd[447]: wlp3s0: sending IPv6 Router Solicitation
May 04 14:04:28 arch dhcpcd[447]: [color=#FF0000]wlp3s0: sendmsg: Cannot assign requested address[/color]
May 04 14:04:28 arch dhcpcd[447]: wlp3s0: rebinding lease of 192.168.10.59
May 04 14:04:28 arch NetworkManager[284]: <info> (wlp3s0): DHCPv4 state changed nbi -> preinit
May 04 14:04:28 arch dhcpcd[447]: wlp3s0: acknowledged 192.168.10.59 from 192.168.10.1
May 04 14:04:28 arch dhcpcd[447]: wlp3s0: checking for 192.168.10.59
May 04 14:04:32 arch dhcpcd[447]: wlp3s0: sending IPv6 Router Solicitation
May 04 14:04:33 arch dhcpcd[447]: wlp3s0: leased 192.168.10.59 for 86400 seconds
May 04 14:04:33 arch NetworkManager[284]: <info> (wlp3s0): DHCPv4 state changed preinit -> bound
May 04 14:04:33 arch NetworkManager[284]: <info> address 192.168.10.59
May 04 14:04:33 arch NetworkManager[284]: <info> prefix 24 (255.255.255.0)
May 04 14:04:33 arch NetworkManager[284]: <info> gateway 192.168.10.1
May 04 14:04:33 arch NetworkManager[284]: <info> nameserver '192.168.10.1'
May 04 14:04:33 arch NetworkManager[284]: <info> Activation (wlp3s0) Stage 5 of 5 (IPv4 Configure Commit) scheduled...
May 04 14:04:33 arch NetworkManager[284]: <info> Activation (wlp3s0) Stage 5 of 5 (IPv4 Commit) started...
May 04 14:04:34 arch NetworkManager[284]: <info> (wlp3s0): device state change: ip-config -> secondaries (reason 'none') [70 90 0]
May 04 14:04:34 arch NetworkManager[284]: <info> Activation (wlp3s0) Stage 5 of 5 (IPv4 Commit) complete.
May 04 14:04:34 arch NetworkManager[284]: <info> (wlp3s0): device state change: secondaries -> activated (reason 'none') [90 100 0]
May 04 14:04:34 arch NetworkManager[284]: <info> Policy set 'Auto The Way 5GHz' (wlp3s0) as default for IPv4 routing and DNS.
May 04 14:04:34 arch NetworkManager[284]: <info> Writing DNS information to /usr/sbin/resolvconf
May 04 14:04:34 arch NetworkManager[284]: <info> (wlp3s0): roamed from BSSID 90:27:E4:5E:98:24 (The Way 5GHz) to 00:26:F2:F2:E7:D5 (The Way 5GHz)
May 04 14:04:34 arch NetworkManager[284]: <info> Activation (wlp3s0) successful, device activated.
May 04 14:04:36 arch dhcpcd[447]: wlp3s0: sending IPv6 Router Solicitation
May 04 14:04:40 arch dhcpcd[447]: wlp3s0: sending IPv6 Router Solicitation
May 04 14:04:40 arch dhcpcd[447]: wlp3s0: no IPv6 Routers available
May 04 21:04:49 arch NetworkManager[284]: <info> (wlp3s0): IP6 addrconf timed out or failed.
May 04 21:04:49 arch NetworkManager[284]: <info> Activation (wlp3s0) Stage 4 of 5 (IPv6 Configure Timeout) scheduled...
May 04 21:04:49 arch NetworkManager[284]: <info> Activation (wlp3s0) Stage 4 of 5 (IPv6 Configure Timeout) started...
May 04 21:04:50 arch systemd[1]: NetworkManager.service: main process exited, code=dumped, status=6/ABRT
May 04 21:04:50 arch systemd[1]: MESSAGE=Unit NetworkManager.service entered failed state.
May 04 21:04:50 arch systemd-coredump[1036]: [color=#FF0000]Process 284 (NetworkManager) dumped core.[/color]
journalctl -u wpa_supplicant --since=today
-- Reboot --
May 04 14:04:21 arch systemd[1]: Starting WPA supplicant...
See dmesg at Pastebin
[edited May 7, 2013]
I'm marking this topic SOLVED, though more accurately, I should say that I've worked around the problem.
I achieved a stable wireless connection by changing APs, which leads me to believe that the underlying problem is upstream. Specifically, the problem is most likely that NetworkManager is not compatible with all APs. In my case, when I connect to a Netgear NDR3700v1 running dd-wrt, NetworkManager and nn-applet crashed randomly and frequently. However, after changing to an Apple Airport AP, I achieved a stable connection without crashes.
Bottomline: if you experience wireless connection troubles with NetworkManager and nm-applet, the problem may be that NetworkManager is not "compatible" with your AP hardware.
Last edited by hcra (2013-05-07 20:50:36)

b1tgl0w wrote:Is it normal for crond to run as the root user?
Completely normal. I'd be asking the question "was I hacked" if I found cron NOT running as root.
I'd say your computer just crashed.

[Solved] NetworkManager, DHCPC, LIBNL : NoIP error ?

Since few, I have problems getting IP adress with NetworkManager, so I switch to WiCD which works well.
I found this error with journalctl :
avril 10 09:37:01 x200 NetworkManager[537]: <error> [1397115421.4269] [nm-system.c:287] sync_addresses(): (enp0s25): error -7 returned from rtnl_addr_add():
Does anybody know how to solve this issue ? I need to switch back to NM because it allows me to manage a 3G/UMTS connection.
[EDIT]
it looks quite similar to this bug :
https://bugzilla.redhat.com/show_bug.cgi?id=1063885
Last edited by dR0o7 (2014-04-15 07:55:35)

Doing a fresh re-install of the package seems to have solved the problem
Using wicd as connection manager
sudo pacman -Rnsc networkmanager
reboot then
sudo pacman -Sy networkmanager network-manager-applet
with all the systemctl enable/disable needed
networkmanager also seems to use dhcpcd to get ip now instead of dhclient
dr0o7@x200 ~% sudo journalctl -n 2000 | grep dhc
avril 15 09:49:21 x200 NetworkManager[506]: <info> dhcpcd started with pid 2135
avril 15 09:49:21 x200 dhcpcd[2135]: version 6.3.2 starting
avril 15 09:49:21 x200 dhcpcd[2135]: DUID 00:01:00:01:1a:cf:ca:8c:00:1f:16:1a:f3:70
avril 15 09:49:21 x200 dhcpcd[2135]: enp0s25: IAID 16:1a:f3:70
avril 15 09:49:21 x200 dhcpcd[2135]: enp0s25: soliciting an IPv6 router
avril 15 09:49:21 x200 dhcpcd[2135]: enp0s25: rebinding lease of 10.219.5.11
avril 15 09:49:26 x200 dhcpcd[2135]: enp0s25: leased 10.219.5.11 for 691200 seconds
avril 15 09:49:26 x200 dhcpcd[2135]: enp0s25: adding route to 10.219.5.0/24
avril 15 09:49:27 x200 dhcpcd[2135]: enp0s25: removing route to 10.219.5.0/24
avril 15 09:49:33 x200 dhcpcd[2135]: enp0s25: no IPv6 Routers available

[solved] networkmanager-vpnc

Hello everyone,
I added a vpnc using networkmanager-vpnc but when i try to activate it i get the following message:
Jun 27 19:35:55 himmel NetworkManager[333]: <warn> connection /org/freedesktop/NetworkManager/Settings/2 failed to activate: (2) The VPN service 'org.freedesktop.NetworkManager.vpnc' was not installed.
i checked the boards but couldn't find anything to help me solve this issue, has anyone encountered this before?
Thanks in advanced for your time and assistance.
Zerosoul.
Last edited by zerosoul13 (2012-06-29 03:52:41)

this is odd, seems that those packages were already installed on the machine
[angel@himmel ~]$ sudo pacman -S networkmanager-vpnc vpnc
warning: networkmanager-vpnc-0.9.4.0-1 is up to date -- reinstalling
warning: vpnc-0.5.3.svn516-2 is up to date -- reinstalling
resolving dependencies...
looking for inter-conflicts...
Targets (2): networkmanager-vpnc-0.9.4.0-1 vpnc-0.5.3.svn516-2
Total Installed Size: 0.80 MiB
Net Upgrade Size: 0.00 MiB
Proceed with installation? [Y/n] Y
(2/2) checking package integrity [--------------------------------------------------------] 100%
(2/2) loading package files [--------------------------------------------------------] 100%
(2/2) checking for file conflicts [--------------------------------------------------------] 100%
(2/2) checking available disk space [--------------------------------------------------------] 100%
(1/2) upgrading vpnc [--------------------------------------------------------] 100%
(2/2) upgrading networkmanager-vpnc [--------------------------------------------------------] 100%
[angel@himmel ~]$ sudo /etc/rc.d/networkmanager restart
:: Stopping NetworkManager [DONE]
:: Starting NetworkManager
After this, i was able to connect to VPN, ill do a reboot and see if it works without having to restart the networkmanager daemon.
# Issue solved.
Last edited by zerosoul13 (2012-06-29 03:52:02)

[SOLVED] NetworkManager and UMTS/3G

I have a problem with NetworkManager and its Applet (the GNOME one)
In Ubuntu 10.04 it works fine with NM and in Archlinux it works flawless with wvdial but not with NetworkManager
It just tells me that i dont have any UMTS/3G devices (which is just nonsense)
Is that a bug in NetworkManager or am i doing something wrong?
//Edit: Oh damm i just forget the optional dependency "modemmanager"... solved
Last edited by Vamp898 (2010-06-14 00:43:24)

Your edit got me one step further, now I see that device also in networkmanager here finally. Thank you!
If someone tries to click onto "configure" for "mobile broadband" and its greyed out: Click "configure" for wired, leave that window open and just click "configure" in the main networkmanager window again. Then the network connections box from gnome 2 comes up and allows to configure 3G entries. (not a gnome bug, but a feature;)

[SOLVED] Networkmanager - Network Managment Disabled

I had a bad resume from suspend and had to restart computer, After that my networkmanager cant connect and KDE icon says viz subject. Trying to find some solution here I used google to find this : http://osdir.com/ml/debian-bugs-dist/20 … 07864.html
Stopping networkmanager daemon, rm /var/lib/NetworkManager/NetworkManager.state and starting again solved this problem.
However, this behavior looks very bad for me. If every daemon works like this, after bad resume u can throw the computer from window... And BTW I think this should be at wiki in Troubleshooting 'cause this can happen to everyone
Last edited by LukynZ (2010-02-22 20:29:35)

I fix it myself by adding rm line to /etc/rc.d/networkmanager where start script is, now its fixed automatically
PID=`pidof -o %PPID $NETWORKMANAGER_BIN`
case "$1" in
start)
rm /var/lib/NetworkManager/NetworkManager.state
stat_busy "Starting NetworkManager"
if [ -z "$PID" ]; then
$NETWORKMANAGER_BIN
fi
if [ ! -z "$PID" -o $? -gt 0 ]; then
stat_fail
else
add_daemon networkmanager
stat_done
fi
stop)
I am not sure how much is this solution clear, but it works and thats all I need

[SOLVED] NetworkManager and DNS

Hello,
Is there any way to set and make permanent DNS adress with NetworkManager? I'd like to use OpenDNS so I edited /etc/resolv.conf and it works till next system restart. What am I supposed to do to make DNS adress permanent?:/
EDIT: Something gone wrong.
EDIT: Solved, it's new NetworkManager 0.7.
Last edited by MilosC (2009-03-08 02:10:32)

My all time favorite way to do this is to put your isp (or OpenDNS addresses, etc) into your router via it's own configuration page. I've never had to mess around with resolv.conf, dhclient etc this way for over 5 years and let the box pick it up from your router.
After making the change in the router, restart networking, or reboot.

[SOLVED] NetworkManager keeps on reconnecting

My NetworkManager keeps on reconnecting no matter whether I use wired or wireless network. This annoys me a few days.
I find that `sudo systemctl restart NetworkManager` could solve this problem temporarily. After reboot the problem arises again.
My system is up to date. And I am using Gnome 3.
Any idea why does it happen and how could I get rid of it?
Last edited by vanitas (2015-02-04 04:01:10)

@frank604, I didn't enabled dhcpcd, netctl, or wicd.
I ran `journalctl -u NetworkManager.service` and noticed these lines:
Feb 04 10:36:52 xbull NetworkManager[4339]: <warn> the dhcpcd backend does not support IPv6.
Feb 04 10:36:52 xbull NetworkManager[4339]: <info> (enp4s0): device state change: activated -> failed (reason 'dhcp-start-failed') [100 120 15]
After some googling, I find this post: dhcpcd not work with NetworkManager 1.0.
Someone metions that NetworkManager 1.0 embed an internal DHCP client, and the DHCP client does not support IPv6 yet.
I edit the connection and disable IPv6, then the problem disappears.
Thanks for your help!

[Solved] NetworkManager does not connect wlan interface to my WLAN

Hi,
I don't know what I am missing. Connecting to my WLAN using wifi-menu does work fine. But if I try to use nm-applet it doesn't connect (see journalctl below)
I use i3 as a GUI and enabled its tray. I can see the nm-applet but its loading forever without connectivity.
Mar 29 14:03:19 <hostname> NetworkManager[3024]: get_secret_flags: assertion `is_secret_prop (setting, secret_name, error)' failed
Mar 29 14:03:19 <hostname> NetworkManager[3024]: <info> Activation (wlp3s0) Stage 1 of 5 (Device Prepare) scheduled...
Mar 29 14:03:19 <hostname> NetworkManager[3024]: <info> Activation (wlp3s0) Stage 1 of 5 (Device Prepare) started...
Mar 29 14:03:19 <hostname> NetworkManager[3024]: <info> (wlp3s0): device state change: need-auth -> prepare (reason 'none') [60 40 0]
Mar 29 14:03:19 <hostname> NetworkManager[3024]: <info> Activation (wlp3s0) Stage 2 of 5 (Device Configure) scheduled...
Mar 29 14:03:19 <hostname> NetworkManager[3024]: <info> Activation (wlp3s0) Stage 1 of 5 (Device Prepare) complete.
Mar 29 14:03:19 <hostname> NetworkManager[3024]: <info> Activation (wlp3s0) Stage 2 of 5 (Device Configure) starting...
Mar 29 14:03:19 <hostname> NetworkManager[3024]: <info> (wlp3s0): device state change: prepare -> config (reason 'none') [40 50 0]
Mar 29 14:03:19 <hostname> NetworkManager[3024]: <info> Activation (wlp3s0/wireless): connection '<My ESSID>' has security, and secrets exist. No new secrets needed.
Mar 29 14:03:19 <hostname> NetworkManager[3024]: <info> Config: added 'ssid' value '<My ESSID>'
Mar 29 14:03:19 <hostname> NetworkManager[3024]: <info> Config: added 'scan_ssid' value '1'
Mar 29 14:03:19 <hostname> NetworkManager[3024]: <info> Config: added 'key_mgmt' value 'WPA-PSK'
Mar 29 14:03:19 <hostname> NetworkManager[3024]: <info> Config: added 'auth_alg' value 'OPEN'
Mar 29 14:03:19 <hostname> NetworkManager[3024]: <info> Config: added 'psk' value '<omitted>'
Mar 29 14:03:19 <hostname> NetworkManager[3024]: <info> Activation (wlp3s0) Stage 2 of 5 (Device Configure) complete.
Mar 29 14:03:19 <hostname> NetworkManager[3024]: <info> Config: set interface ap_scan to 1
Mar 29 14:03:19 <hostname> NetworkManager[3024]: <info> (wlp3s0): supplicant interface state: inactive -> scanning
Mar 29 14:03:22 <hostname> kernel: wlp3s0: deauthenticating from <MAC address> by local choice (reason=2)
Mar 29 14:03:22 <hostname> kernel: wlp3s0: deauthenticating from <MAC address> by local choice (reason=2)
Mar 29 14:03:22 <hostname> NetworkManager[3024]: <info> (wlp3s0): supplicant interface state: scanning -> disconnected
Mar 29 14:03:22 <hostname> NetworkManager[3024]: <info> (wlp3s0): supplicant interface state: disconnected -> scanning
Mar 29 14:03:26 <hostname> kernel: wlp3s0: deauthenticating from <MAC address> by local choice (reason=2)
Mar 29 14:03:26 <hostname> kernel: wlp3s0: deauthenticating from <MAC address> by local choice (reason=2)
Mar 29 14:03:26 <hostname> NetworkManager[3024]: <info> (wlp3s0): supplicant interface state: scanning -> disconnected
Mar 29 14:03:26 <hostname> NetworkManager[3024]: <info> (wlp3s0): supplicant interface state: disconnected -> scanning
Mar 29 14:03:29 <hostname> kernel: wlp3s0: deauthenticating from <MAC address> by local choice (reason=2)
Mar 29 14:03:29 <hostname> kernel: wlp3s0: deauthenticating from <MAC address> by local choice (reason=2)
Mar 29 14:03:29 <hostname> NetworkManager[3024]: <info> (wlp3s0): supplicant interface state: scanning -> disconnected
Mar 29 14:03:30 <hostname> NetworkManager[3024]: <info> (wlp3s0): supplicant interface state: disconnected -> scanning
Mar 29 14:03:34 <hostname> kernel: wlp3s0: deauthenticating from <MAC address> by local choice (reason=2)
Mar 29 14:03:34 <hostname> kernel: wlp3s0: deauthenticating from <MAC address> by local choice (reason=2)
Mar 29 14:03:34 <hostname> NetworkManager[3024]: <info> (wlp3s0): supplicant interface state: scanning -> disconnected
Mar 29 14:03:39 <hostname> NetworkManager[3024]: <info> (wlp3s0): supplicant interface state: disconnected -> scanning
Mar 29 14:03:42 <hostname> kernel: wlp3s0: deauthenticating from <MAC address> by local choice (reason=2)
Mar 29 14:03:42 <hostname> kernel: wlp3s0: deauthenticating from <MAC address> by local choice (reason=2)
Mar 29 14:03:42 <hostname> NetworkManager[3024]: <info> (wlp3s0): supplicant interface state: scanning -> disconnected
Mar 29 14:03:44 <hostname> NetworkManager[3024]: <warn> Activation (wlp3s0/wireless): association took too long, failing activation.
Mar 29 14:03:44 <hostname> NetworkManager[3024]: <info> (wlp3s0): device state change: config -> failed (reason 'SSID not found') [50 120 53]
Mar 29 14:03:44 <hostname> NetworkManager[3024]: <warn> Activation (wlp3s0) failed for connection '<My ESSID>'
Mar 29 14:03:45 <hostname> NetworkManager[3024]: <info> (wlp3s0): device state change: failed -> disconnected (reason 'none') [120 30 0]
Mar 29 14:03:45 <hostname> NetworkManager[3024]: <info> (wlp3s0): deactivating device (reason 'none') [0]
Mar 29 14:03:48 <hostname> kernel: wlp3s0: deauthenticating from <MAC address> by local choice (reason=2)
Mar 29 14:03:48 <hostname> NetworkManager[3024]: <info> (wlp3s0): supplicant interface state: disconnected -> inactive
Mar 29 14:04:05 <hostname> systemd[1]: Stopping Network Manager...
Mar 29 14:04:05 <hostname> NetworkManager[3024]: <info> caught signal 15, shutting down normally.
Mar 29 14:04:05 <hostname> NetworkManager[3024]: <info> (enp0s25): device state change: unavailable -> unmanaged (reason 'removed') [20 10 36]
Mar 29 14:04:05 <hostname> NetworkManager[3024]: <info> (enp0s25): cleaning up...
Mar 29 14:04:05 <hostname> NetworkManager[3024]: <info> (enp0s25): taking down device.
Mar 29 14:04:05 <hostname> kernel: e1000e 0000:00:19.0: irq 45 for MSI/MSI-X
Mar 29 14:04:05 <hostname> NetworkManager[3024]: <info> (wlp3s0): device state change: disconnected -> unmanaged (reason 'removed') [30 10 36]
Mar 29 14:04:05 <hostname> NetworkManager[3024]: <info> (wlp3s0): cleaning up...
Mar 29 14:04:05 <hostname> NetworkManager[3024]: <info> (wlp3s0): taking down device.
Mar 29 14:04:05 <hostname> kernel: wlp3s0: deauthenticating from <MAC address> by local choice (reason=3)
Mar 29 14:04:05 <hostname> NetworkManager[3024]: <info> exiting (success)
I would be really glad if you could help me.
Best regards,
Christian
Last edited by Watnuss (2013-03-29 13:58:40)

Watnuss wrote:Ok I found the issue. net-auto-wireless was started automatically and thus NetworkManager couldn't be started properly. Disabling net-auto-wireless and enabling NetworkManager worked for me.
Don't worry, I have done this before too. It is horribly frustrating until you realize the problem, at which time I always think, "Ah crap, I need to pay attention to what I'm doing more..."

[SOLVED] NetworkManager will not connect to Mobile Broadband (o2)

I cannot get Networkmanager to connect to mobile broadband (o2).
Everything works fine if I open a terminal, do "sudo wvdial o2", minimize it, and then open Firefox.
Networkmanager (nm-applet) shows the connection to o2, but if I select it, it just instantly responds with "Network Disconnected". I have checked the settings for the mobile broadband connection, and they are the same as in wvdial.
I have also tried logging in as root, and tried from there, but I still get the same resuilt.
I would be very grateful for any help with this problem.
Last edited by myrlin (2011-03-17 20:00:29)

As if by magic, the latest updates have solved the problem. I've no idea how, but everything is now working perfectly.
Thanks to everyone who has taken the time to think about this problem for me.

[SOLVED] NetworkManager does not connect to WiFi networks

I'm using `networkmanager` to connect WiFi.
I have selected WiFi Name through `networkmanager`.
Next, enter WiFi Password.
But the problem is, `networkmanager` asks me about password again and again and over again and does not connect to WiFi never !!!!
I'm sure WiFi password that I entered is correct.
Last edited by kamrava (2014-02-22 05:46:37)

orschiro wrote:Maybe not satisfying, but can you instead use Wicd?
My problem was solved. `wicd` was not installed on my system.
My Problem solved through :
I have Installed `wicd` and then NetworkManager works like a charm now
$ sudo pacman -S wicd wicd-gtk
Thank you all.
Last edited by kamrava (2014-02-21 11:29:17)

[SOLVED] NetworkManager unable to enable Wifi

Edit: Finally solved. Disabling the "acer_wmi" module did the trick.
I've been using NetworkManager on my laptop for quite some time now, and it always did a good job... until now!
And in the middle of quite a busy week as well! Damn Murphy...
I noticed there was an update for it and Archer as I am, I of course updated from networkmanager-0.8.1-1-x86_64 and network-manager-applet-0.8.1-2-x86_64, to networkmanager-0.8.2-3-x86_64 and network-manager-applet-0.8.2-2-x86_64.
When updating I got a message that filesystem permissions of /var/lib/NetworkManager we're set to 755, and the package expected 700.
Should not be a problem, but I set the permissions to 700 for good measure.
Next boot, using the new version, I was unable to get NetworkManager to engage my Wifi. "Enable Wireless" just did nothing. It's not turning on my Wifi and nm-applet is not marking it as active either, no matter how many times I click it. I also tried disabling Networking and re-enabling it all, no luck.
Reloaded nm-applet a couple of times, no dice. Restarted the networkmanager deamon as well, still nothing.
nm-applet does not produce any error messages for me to check out, only things it tells me when I kill and start it:
** Message: applet now removed from the notification area
** Message: applet now embedded in the notification area
It only talks about placing itself in the notification area, which is in working order.
My laptop is a Sony Vaio VPCY11S1E (know as Sony Vaio Y series, first model), Wifi card is an Atheros AR9285 (ath9k) and it runs up-to-date Arch x86_64. I run a hand configured -ck patched kernel and also the Arch regular kernel.
Come to think of it, I did not try the stock kernel yet, but I doubt it's the cause of the problem.
Because I reverted back to NetworkManager 0.8.1 and it's working like it always did again.
So I got working Wifi with NM 0.8.1, no working Wifi with 0.8.2.
Any pointers or insights you might have are greatly appreciated!
Last edited by Ultraman (2011-03-06 00:48:32)

Oh sorry. I did do that, a bit.
I have a tail of the everything.log outputted to my desktop, and noticed NetworkManager is deactivating the Wifi (Reason 2).
I'm gonna check out what "Reason 2" might mean, and i'll see if I can post a nice snippet of the log here...
Log snippet
Nov 23 15:01:03 localhost NetworkManager[7888]: <info> NetworkManager (version 0.8.2) is starting...
Nov 23 15:01:03 localhost NetworkManager[7888]: <info> Read config file /etc/NetworkManager/nm-system-settings.conf
Nov 23 15:01:03 localhost NetworkManager[7888]: <info> trying to start the modem manager...
Nov 23 15:01:03 localhost NetworkManager[7888]: <info> monitoring kernel firmware directory '/lib/firmware'.
Nov 23 15:01:03 localhost NetworkManager[7888]: <info> Loaded plugin keyfile: (c) 2007 - 2010 Red Hat, Inc. To report bugs please use the NetworkManager mailing list.
Nov 23 15:01:03 localhost NetworkManager[7888]: <info> found WiFi radio killswitch rfkill1 (at /sys/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/device:0d/SNY5001:00/rfkill/rfkill1) (driver Sony Notebook Control Driver)
Nov 23 15:01:03 localhost NetworkManager[7888]: <info> found WiFi radio killswitch rfkill4 (at /sys/devices/pci0000:00/0000:00:1c.1/0000:02:00.0/ieee80211/phy0/rfkill4) (driver <unknown>)
Nov 23 15:01:03 localhost NetworkManager[7888]: <info> found WiFi radio killswitch rfkill3 (at /sys/devices/platform/acer-wmi/rfkill/rfkill3) (driver acer-wmi)
Nov 23 15:01:03 localhost NetworkManager[7888]: <info> WiFi disabled by radio killswitch; enabled by state file
Nov 23 15:01:03 localhost NetworkManager[7888]: <info> WWAN enabled by radio killswitch; enabled by state file
Nov 23 15:01:03 localhost NetworkManager[7888]: <info> WiMAX enabled by radio killswitch; enabled by state file
Nov 23 15:01:03 localhost NetworkManager[7888]: <info> Networking is enabled by state file
Nov 23 15:01:03 localhost NetworkManager[7888]: <info> (eth0): carrier is OFF
Nov 23 15:01:03 localhost NetworkManager[7888]: <info> (eth0): new Ethernet device (driver: 'atl1c' ifindex: 2)
Nov 23 15:01:03 localhost NetworkManager[7888]: <info> (eth0): exported as /org/freedesktop/NetworkManager/Devices/0
Nov 23 15:01:03 localhost NetworkManager[7888]: <info> (eth0): now managed
Nov 23 15:01:03 localhost NetworkManager[7888]: <info> (eth0): device state change: 1 -> 2 (reason 2)
Nov 23 15:01:03 localhost NetworkManager[7888]: <info> (eth0): bringing up device.
Nov 23 15:01:03 localhost NetworkManager[7888]: <info> (eth0): preparing device.
Nov 23 15:01:03 localhost NetworkManager[7888]: <info> (eth0): deactivating device (reason: 2).
Nov 23 15:01:03 localhost NetworkManager[7888]: <info> Added default wired connection 'Auto eth0' for /sys/devices/pci0000:00/0000:00:1c.0/0000:01:00.0/net/eth0
Nov 23 15:01:03 localhost NetworkManager[7888]: <info> (wlan0): driver supports SSID scans (scan_capa 0x01).
Nov 23 15:01:03 localhost NetworkManager[7888]: <info> (wlan0): new 802.11 WiFi device (driver: 'ath9k' ifindex: 3)
Nov 23 15:01:03 localhost NetworkManager[7888]: <info> (wlan0): exported as /org/freedesktop/NetworkManager/Devices/1
Nov 23 15:01:03 localhost NetworkManager[7888]: <info> (wlan0): now managed
Nov 23 15:01:03 localhost NetworkManager[7888]: <info> (wlan0): device state change: 1 -> 2 (reason 2)
Nov 23 15:01:03 localhost NetworkManager[7888]: <info> (wlan0): bringing up device.
Nov 23 15:01:03 localhost NetworkManager[7888]: <info> (wlan0): deactivating device (reason: 2).
And that's where it ends.
What jumps out is: "Nov 23 15:01:03 localhost NetworkManager[7888]: <info> WiFi disabled by radio killswitch; enabled by state file"
Which is incorrect, the switch is ON. I also tried switching it OFF and ON again (IT Crowd! ). No effect.
I also see it's seeing multiple killswitches, where I only have one. But that's not the real problem here.
Somehow NM 0.8.2 is thinking my Wifi killswitch is turned off when it isn't.
To see if NM 0.8.1 does anything different, I checked out it's log, which looks like this:
Nov 23 15:03:49 localhost NetworkManager[8714]: <info> NetworkManager (version 0.8.1) is starting...
Nov 23 15:03:49 localhost NetworkManager[8714]: <info> Read config file /etc/NetworkManager/nm-system-settings.conf
Nov 23 15:03:49 localhost NetworkManager[8714]: <info> trying to start the modem manager...
Nov 23 15:03:49 localhost NetworkManager[8714]: <info> Loaded plugin keyfile: (c) 2007 - 2008 Red Hat, Inc. To report bugs please use the NetworkManager mailing list.
Nov 23 15:03:49 localhost NetworkManager[8714]: <info> found WiFi radio killswitch rfkill1 (at /sys/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/device:0d/SNY5001:00/rfkill/rfkill1) (driver Sony Notebook Control Driver)
Nov 23 15:03:49 localhost NetworkManager[8714]: <info> found WiFi radio killswitch rfkill4 (at /sys/devices/pci0000:00/0000:00:1c.1/0000:02:00.0/ieee80211/phy0/rfkill4) (driver <unknown>)
Nov 23 15:03:49 localhost NetworkManager[8714]: <info> found WiFi radio killswitch rfkill3 (at /sys/devices/platform/acer-wmi/rfkill/rfkill3) (driver acer-wmi)
Nov 23 15:03:49 localhost NetworkManager[8714]: <info> WiFi disabled by radio killswitch; enabled by state file
Nov 23 15:03:49 localhost NetworkManager[8714]: <info> WWAN enabled by radio killswitch; enabled by state file
Nov 23 15:03:49 localhost NetworkManager[8714]: <info> WiMAX enabled by radio killswitch; enabled by state file
Nov 23 15:03:49 localhost NetworkManager[8714]: <info> Networking is enabled by state file
Nov 23 15:03:49 localhost NetworkManager[8714]: <info> (eth0): carrier is OFF
Nov 23 15:03:49 localhost NetworkManager[8714]: <info> (eth0): new Ethernet device (driver: 'atl1c' ifindex: 2)
Nov 23 15:03:49 localhost NetworkManager[8714]: <info> (eth0): exported as /org/freedesktop/NetworkManager/Devices/0
Nov 23 15:03:49 localhost NetworkManager[8714]: <info> (eth0): now managed
Nov 23 15:03:49 localhost NetworkManager[8714]: <info> (eth0): device state change: 1 -> 2 (reason 2)
Nov 23 15:03:49 localhost NetworkManager[8714]: <info> (eth0): bringing up device.
Nov 23 15:03:49 localhost NetworkManager[8714]: <info> (eth0): preparing device.
Nov 23 15:03:49 localhost NetworkManager[8714]: <info> (eth0): deactivating device (reason: 2).
Nov 23 15:03:49 localhost NetworkManager[8714]: <info> Added default wired connection 'Auto eth0' for /sys/devices/pci0000:00/0000:00:1c.0/0000:01:00.0/net/eth0
Nov 23 15:03:49 localhost NetworkManager[8714]: <info> (wlan0): driver supports SSID scans (scan_capa 0x01).
Nov 23 15:03:49 localhost NetworkManager[8714]: <info> (wlan0): new 802.11 WiFi device (driver: 'ath9k' ifindex: 3)
Nov 23 15:03:49 localhost NetworkManager[8714]: <info> (wlan0): exported as /org/freedesktop/NetworkManager/Devices/1
Nov 23 15:03:49 localhost NetworkManager[8714]: <info> (wlan0): now managed
Nov 23 15:03:49 localhost NetworkManager[8714]: <info> (wlan0): device state change: 1 -> 2 (reason 2)
Nov 23 15:03:49 localhost NetworkManager[8714]: <info> (wlan0): bringing up device.
Nov 23 15:03:49 localhost NetworkManager[8714]: <info> (wlan0): deactivating device (reason: 2).
Nov 23 15:03:54 localhost NetworkManager[8714]: <info> (wlan0): bringing up device.
Nov 23 15:03:54 localhost NetworkManager[8714]: <info> (wlan0): supplicant interface state: starting -> ready
Nov 23 15:03:54 localhost NetworkManager[8714]: <info> (wlan0): device state change: 2 -> 3 (reason 42)
Nov 23 15:03:55 localhost NetworkManager[8714]: <info> Activation (wlan0) starting connection 'JoostenWL'
Nov 23 15:03:55 localhost NetworkManager[8714]: <info> (wlan0): device state change: 3 -> 4 (reason 0)
Nov 23 15:03:55 localhost NetworkManager[8714]: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) scheduled...
Nov 23 15:03:55 localhost NetworkManager[8714]: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) started...
Nov 23 15:03:55 localhost NetworkManager[8714]: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) scheduled...
It's doing the exact same thing as NM 0.8.2 is it not?
Only it does bring up the interface by trying again by the looks of it.
Note the following behaviour of 0.8.1:
Nov 23 15:03:49 localhost NetworkManager[8714]: <info> (wlan0): exported as /org/freedesktop/NetworkManager/Devices/1
Nov 23 15:03:49 localhost NetworkManager[8714]: <info> (wlan0): now managed
Nov 23 15:03:49 localhost NetworkManager[8714]: <info> (wlan0): device state change: 1 -> 2 (reason 2)
Nov 23 15:03:49 localhost NetworkManager[8714]: <info> (wlan0): bringing up device.
Nov 23 15:03:49 localhost NetworkManager[8714]: <info> (wlan0): deactivating device (reason: 2).
Nov 23 15:03:54 localhost NetworkManager[8714]: <info> (wlan0): bringing up device.
Nov 23 15:03:54 localhost NetworkManager[8714]: <info> (wlan0): supplicant interface state: starting -> ready
NM 0.8.2 stops after the message "deactivating the device (reason: 2)."
Last edited by Ultraman (2010-11-23 15:01:44)

[Solved] Networkmanager not removing properly

I installed networkmanager 0.6.5 via pacman but later decide to remove it.
I'm using KDE 3.5.4 and the Don't Panic Kernel.
Now always I shutdown or boot I receive the following error:
On shutdown:
/etc/rc.shutdown: Line 30 /etc/rc.d/networkmanager No such file or directory
On boot:
/etc/rc.multi: /etc/rc.d/networkmanager No such file or directory
This is annoying. Is there anyway to completely remove networkmanager?
Thanks in advance for any suggestions.
[EDIT]: Oops. I forgot to check rc.conf. Removing networkmanager from daemons list solved the problem.
Last edited by Vieira (2007-08-30 12:32:11)

nevermind... ii'm blind...
Last edited by klixon (2007-09-07 09:36:02)

[SOLVED] NetworkManager not letting me connect to the internet.

Hello everyone,
I normally connect to my WiFi using wifi-menu each start-up, but since I'm coming from Ubuntu in this laptop, and want the NetworkManager integration in GNOME, as well as automatically connecting to my preferred network on startup, I decided to install NetworkManager and network-manager-applet, as well as networkmanager-openvpn and networkmanager-pptp for vpn support.
Unfortunately, enabling the NetworkManager service and starting the NetworkManager service (first disabling the netctl@wlo1\x2dCasa.service and wpa_supplicant.service) disconnects me from WiFi, and connecting to my network asks for the password (WPA2 Personal), after 50 seconds it asks for the password again, and goes on forever, unless one presses "Cancel" and it disconnects.
I'm new to Arch Linux (not to Linux in general, as I actually used Ubuntu since 2009, and have some command-line experience), so if this seems like an easy task, or a rookie mistake, please bear with me.
Is any more info required? Log files?
-Jonathan
Last edited by Jonathan Precise (2015-04-04 13:36:19)

Yes, you are indeed right Xabre, I stopped netctl@wlo1\x2dCasa.service, but not wpa_supplicant.service, and enabled that last one. Now NetworkManager runs perfect!
EDIT: I'm imagining that's how you mark this thread as solved? Or is there another method?
-Jonathan
Last edited by Jonathan Precise (2015-04-04 13:37:19)

[Solved] NetworkManager-pptp VPN not working after update to 0.9.10

Hello,
I have a PPTP VPN set up and it's been working for a long time. However, after I updated last night to networkmanager-0.9.10, it is no longer able to connect to the remote network. I can activate the VPN connection, enter my password, but after a short period of time, the connection reports: "Error: Connection activation failed: the VPN service returned invalid configuration." As I mentioned before, this VPN was working right before the update and I didn't change the configuration on either my computer or the destination network so I'm pretty sure that this is something to do with the update. I'm wondering if anybody else has run into this problem and if they've been able to find a solution. I've been searching all over these forums and the internet for some hours now and I haven't found anything yet. I'm hoping that somebody might be able to point me in the right direction or maybe know of something that might have changed with the new update.
Here is my VPN configuration (using NetworkManager-PPTP. I've also obscured the public IP address):
[connection]
id=MyVPN
uuid=fe6e6265-1a79-4a69-b6d1-8b47e9d4c948
type=vpn
permissions=user:greyseal96:;
autoconnect=false
timestamp=1408950986
[vpn]
service-type=org.freedesktop.NetworkManager.pptp
gateway=192.168.146.114
require-mppe=yes
user=greyseal96
password-flags=3
[ipv6]
method=auto
[ipv4]
method=auto
route1=10.17.0.0/16,10.17.1.1,1
never-default=true
Here are my logs during the time that I tried to connect:
Aug 24 23:44:15 MyArchBox NetworkManager[578]: <info> Starting VPN service 'pptp'...
Aug 24 23:44:15 MyArchBox NetworkManager[578]: <info> VPN service 'pptp' started (org.freedesktop.NetworkManager.pptp), PID 1938
Aug 24 23:44:15 MyArchBox NetworkManager[578]: <info> VPN service 'pptp' appeared; activating connections
Aug 24 23:44:21 MyArchBox NetworkManager[578]: <info> VPN connection 'MyVPN' (ConnectInteractive) reply received.
Aug 24 23:44:21 MyArchBox NetworkManager[578]: <info> VPN plugin state changed: starting (3)
Aug 24 23:44:21 MyArchBox NetworkManager[578]: ** Message: pppd started with pid 1945
Aug 24 23:44:21 MyArchBox NetworkManager[578]: <info> VPN connection 'MyVPN' (Connect) reply received.
Aug 24 23:44:21 MyArchBox pppd[1945]: Plugin /usr/lib/pppd/2.4.6/nm-pptp-pppd-plugin.so loaded.
Aug 24 23:44:21 MyArchBox NetworkManager[578]: Plugin /usr/lib/pppd/2.4.6/nm-pptp-pppd-plugin.so loaded.
Aug 24 23:44:21 MyArchBox NetworkManager[578]: ** Message: nm-pptp-ppp-plugin: (plugin_init): initializing
Aug 24 23:44:21 MyArchBox pppd[1945]: pppd 2.4.6 started by root, uid 0
Aug 24 23:44:21 MyArchBox NetworkManager[578]: ** Message: nm-pptp-ppp-plugin: (nm_phasechange): status 3 / phase 'serial connection'
Aug 24 23:44:21 MyArchBox pppd[1945]: Using interface ppp0
Aug 24 23:44:21 MyArchBox pppd[1945]: Connect: ppp0 <--> /dev/pts/2
Aug 24 23:44:21 MyArchBox NetworkManager[578]: Using interface ppp0
Aug 24 23:44:21 MyArchBox NetworkManager[578]: Connect: ppp0 <--> /dev/pts/2
Aug 24 23:44:21 MyArchBox NetworkManager[578]: ** Message: nm-pptp-ppp-plugin: (nm_phasechange): status 5 / phase 'establish'
Aug 24 23:44:21 MyArchBox NetworkManager[578]: <info> (ppp0): new Generic device (driver: 'unknown' ifindex: 10)
Aug 24 23:44:21 MyArchBox NetworkManager[578]: <info> (ppp0): exported as /org/freedesktop/NetworkManager/Devices/9
Aug 24 23:44:21 MyArchBox pptp[1947]: nm-pptp-service-1938 log[main:pptp.c:333]: The synchronous pptp option is NOT activated
Aug 24 23:44:21 MyArchBox pptp[1954]: nm-pptp-service-1938 log[ctrlp_rep:pptp_ctrl.c:258]: Sent control packet type is 1 'Start-Control-Connection-Request'
Aug 24 23:44:21 MyArchBox pptp[1954]: nm-pptp-service-1938 log[ctrlp_disp:pptp_ctrl.c:758]: Received Start Control Connection Reply
Aug 24 23:44:21 MyArchBox pptp[1954]: nm-pptp-service-1938 log[ctrlp_disp:pptp_ctrl.c:792]: Client connection established.
Aug 24 23:44:22 MyArchBox pptp[1954]: nm-pptp-service-1938 log[ctrlp_rep:pptp_ctrl.c:258]: Sent control packet type is 7 'Outgoing-Call-Request'
Aug 24 23:44:22 MyArchBox pptp[1954]: nm-pptp-service-1938 log[ctrlp_disp:pptp_ctrl.c:877]: Received Outgoing Call Reply.
Aug 24 23:44:22 MyArchBox pptp[1954]: nm-pptp-service-1938 log[ctrlp_disp:pptp_ctrl.c:916]: Outgoing call established (call ID 0, peer's call ID 50048).
Aug 24 23:44:25 MyArchBox NetworkManager[578]: ** Message: nm-pptp-ppp-plugin: (nm_phasechange): status 6 / phase 'authenticate'
Aug 24 23:44:25 MyArchBox NetworkManager[578]: ** Message: nm-pptp-ppp-plugin: (get_credentials): passwd-hook, requesting credentials...
Aug 24 23:44:25 MyArchBox NetworkManager[578]: ** Message: nm-pptp-ppp-plugin: (get_credentials): got credentials from NetworkManager-pptp
Aug 24 23:44:25 MyArchBox pppd[1945]: CHAP authentication succeeded
Aug 24 23:44:25 MyArchBox NetworkManager[578]: CHAP authentication succeeded
Aug 24 23:44:25 MyArchBox NetworkManager[578]: ** Message: nm-pptp-ppp-plugin: (nm_phasechange): status 8 / phase 'network'
Aug 24 23:44:25 MyArchBox pppd[1945]: MPPE 128-bit stateless compression enabled
Aug 24 23:44:25 MyArchBox NetworkManager[578]: MPPE 128-bit stateless compression enabled
Aug 24 23:44:25 MyArchBox pppd[1945]: Cannot determine ethernet address for proxy ARP
Aug 24 23:44:25 MyArchBox pppd[1945]: local IP address 10.17.10.3
Aug 24 23:44:25 MyArchBox pppd[1945]: remote IP address 10.17.10.1
Aug 24 23:44:25 MyArchBox pppd[1945]: primary DNS address 10.17.2.22
Aug 24 23:44:25 MyArchBox pppd[1945]: secondary DNS address 10.17.2.23
Aug 24 23:44:25 MyArchBox NetworkManager[578]: <info> VPN connection 'MyVPN' (IP4 Config Get) reply received from old-style plugin.
Aug 24 23:44:25 MyArchBox NetworkManager[578]: <info> VPN Gateway: 192.168.146.114
Aug 24 23:44:25 MyArchBox NetworkManager[578]: <info> Tunnel Device: ppp0
Aug 24 23:44:25 MyArchBox NetworkManager[578]: <info> IPv4 configuration:
Aug 24 23:44:25 MyArchBox NetworkManager[578]: <info> Internal Address: 10.17.10.3
Aug 24 23:44:25 MyArchBox NetworkManager[578]: <info> Internal Prefix: 32
Aug 24 23:44:25 MyArchBox NetworkManager[578]: <info> Internal Point-to-Point Address: 10.17.10.1
Aug 24 23:44:25 MyArchBox NetworkManager[578]: <info> Maximum Segment Size (MSS): 0
Aug 24 23:44:25 MyArchBox NetworkManager[578]: <info> Static Route: 10.17.0.0/16 Next Hop: 10.17.1.1
Aug 24 23:44:25 MyArchBox NetworkManager[578]: <info> Forbid Default Route: yes
Aug 24 23:44:25 MyArchBox NetworkManager[578]: <info> Internal DNS: 10.17.2.22
Aug 24 23:44:25 MyArchBox NetworkManager[578]: <info> Internal DNS: 10.17.2.23
Aug 24 23:44:25 MyArchBox NetworkManager[578]: <info> DNS Domain: '(none)'
Aug 24 23:44:25 MyArchBox NetworkManager[578]: <info> No IPv6 configuration
Aug 24 23:44:25 MyArchBox NetworkManager[578]: <error> [1408949065.481618] [platform/nm-linux-platform.c:1716] add_object(): Netlink error adding 10.17.0.0/16 via 10.17.1.1 dev ppp0 metric 1 mss 0 src user: Unspecific failure
Aug 24 23:44:25 MyArchBox NetworkManager[578]: <warn> VPN connection 'MyVPN' did not receive valid IP config information.
Aug 24 23:44:25 MyArchBox NetworkManager[578]: Cannot determine ethernet address for proxy ARP
Aug 24 23:44:25 MyArchBox NetworkManager[578]: local IP address 10.17.10.3
Aug 24 23:44:25 MyArchBox NetworkManager[578]: remote IP address 10.17.10.1
Aug 24 23:44:25 MyArchBox NetworkManager[578]: primary DNS address 10.17.2.22
Aug 24 23:44:25 MyArchBox NetworkManager[578]: secondary DNS address 10.17.2.23
Aug 24 23:44:25 MyArchBox NetworkManager[578]: ** Message: nm-pptp-ppp-plugin: (nm_phasechange): status 9 / phase 'running'
Aug 24 23:44:25 MyArchBox NetworkManager[578]: ** Message: nm-pptp-ppp-plugin: (nm_ip_up): ip-up event
Aug 24 23:44:25 MyArchBox NetworkManager[578]: ** Message: nm-pptp-ppp-plugin: (nm_ip_up): sending Ip4Config to NetworkManager-pptp...
Aug 24 23:44:25 MyArchBox NetworkManager[578]: ** Message: PPTP service (IP Config Get) reply received.
Aug 24 23:44:25 MyArchBox pppd[1945]: Terminating on signal 15
Aug 24 23:44:25 MyArchBox pppd[1945]: Modem hangup
Aug 24 23:44:25 MyArchBox pptp[1954]: nm-pptp-service-1938 log[callmgr_main:pptp_callmgr.c:245]: Closing connection (unhandled)
Aug 24 23:44:25 MyArchBox pptp[1954]: nm-pptp-service-1938 log[ctrlp_rep:pptp_ctrl.c:258]: Sent control packet type is 12 'Call-Clear-Request'
Aug 24 23:44:25 MyArchBox pptp[1954]: nm-pptp-service-1938 log[call_callback:pptp_callmgr.c:84]: Closing connection (call state)
Aug 24 23:44:25 MyArchBox pppd[1945]: Connect time 0.0 minutes.
Aug 24 23:44:25 MyArchBox pppd[1945]: Sent 0 bytes, received 0 bytes.
Aug 24 23:44:25 MyArchBox pppd[1945]: MPPE disabled
Aug 24 23:44:25 MyArchBox pppd[1945]: Connection terminated.
Aug 24 23:44:25 MyArchBox dbus[579]: [system] Rejected send message, 10 matched rules; type="error", sender=":1.51" (uid=0 pid=1938 comm="/usr/lib/networkmanager/nm-pptp-service ") interface="(unset)" member="(unset)" error name="org.freedesktop.DBus.Error.UnknownMethod" requested_reply="0" destination=":1.52" (uid=0 pid=1945 comm="/sbin/pppd pty /sbin/pptp 192.168.146.114 --nolaunc")
Aug 24 23:44:25 MyArchBox dbus[579]: [system] Rejected send message, 10 matched rules; type="error", sender=":1.51" (uid=0 pid=1938 comm="/usr/lib/networkmanager/nm-pptp-service ") interface="(unset)" member="(unset)" error name="org.freedesktop.DBus.Error.UnknownMethod" requested_reply="0" destination=":1.52" (uid=0 pid=1945 comm="/sbin/pppd pty /sbin/pptp 192.168.146.114 --nolaunc")
Aug 24 23:44:25 MyArchBox dbus[579]: [system] Rejected send message, 10 matched rules; type="error", sender=":1.51" (uid=0 pid=1938 comm="/usr/lib/networkmanager/nm-pptp-service ") interface="(unset)" member="(unset)" error name="org.freedesktop.DBus.Error.UnknownMethod" requested_reply="0" destination=":1.52" (uid=0 pid=1945 comm="/sbin/pppd pty /sbin/pptp 192.168.146.114 --nolaunc")
Aug 24 23:44:25 MyArchBox dbus[579]: [system] Rejected send message, 10 matched rules; type="error", sender=":1.51" (uid=0 pid=1938 comm="/usr/lib/networkmanager/nm-pptp-service ") interface="(unset)" member="(unset)" error name="org.freedesktop.DBus.Error.UnknownMethod" requested_reply="0" destination=":1.52" (uid=0 pid=1945 comm="/sbin/pppd pty /sbin/pptp 192.168.146.114 --nolaunc")
Aug 24 23:44:25 MyArchBox dbus[579]: [system] Rejected send message, 10 matched rules; type="error", sender=":1.51" (uid=0 pid=1938 comm="/usr/lib/networkmanager/nm-pptp-service ") interface="(unset)" member="(unset)" error name="org.freedesktop.DBus.Error.UnknownMethod" requested_reply="0" destination=":1.52" (uid=0 pid=1945 comm="/sbin/pppd pty /sbin/pptp 192.168.146.114 --nolaunc")
Aug 24 23:44:25 MyArchBox NetworkManager[578]: inet 10.17.0.0/16 table main
Aug 24 23:44:25 MyArchBox NetworkManager[578]: priority 0x1 protocol static
Aug 24 23:44:25 MyArchBox NetworkManager[578]: nexthop via 10.17.1.1 dev 10
Aug 24 23:44:25 MyArchBox NetworkManager[578]: <error> [1408949065.487073] [platform/nm-linux-platform.c:2252] link_change(): Netlink error changing link 10: <DOWN> mtu 0 (1) driver 'unknown' udi '/sys/devices/virtual/net/ppp0': No such device
Aug 24 23:44:25 MyArchBox NetworkManager[578]: <error> [1408949065.487153] [platform/nm-linux-platform.c:1777] delete_object(): Netlink error deleting 10.17.10.3/32 lft forever pref forever lifetime 1862-0[4294967295,4294967295] dev ppp0 src kernel: No such device (-31)
Aug 24 23:44:25 MyArchBox NetworkManager[578]: ** Message: Terminated ppp daemon with PID 1945.
Aug 24 23:44:25 MyArchBox kernel: Loading kernel module for a network device with CAP_SYS_MODULE (deprecated). Use CAP_NET_ADMIN and alias netdev- instead.
Aug 24 23:44:25 MyArchBox NetworkManager[578]: Terminating on signal 15
Aug 24 23:44:25 MyArchBox NetworkManager[578]: Modem hangup
Aug 24 23:44:25 MyArchBox NetworkManager[578]: ** Message: nm-pptp-ppp-plugin: (nm_phasechange): status 8 / phase 'network'
Aug 24 23:44:25 MyArchBox NetworkManager[578]: Connect time 0.0 minutes.
Aug 24 23:44:25 MyArchBox NetworkManager[578]: Sent 0 bytes, received 0 bytes.
Aug 24 23:44:25 MyArchBox NetworkManager[578]: MPPE disabled
Aug 24 23:44:25 MyArchBox NetworkManager[578]: ** Message: nm-pptp-ppp-plugin: (nm_phasechange): status 10 / phase 'terminate'
Aug 24 23:44:25 MyArchBox NetworkManager[578]: ** Message: nm-pptp-ppp-plugin: (nm_phasechange): status 5 / phase 'establish'
Aug 24 23:44:25 MyArchBox NetworkManager[578]: ** Message: nm-pptp-ppp-plugin: (nm_phasechange): status 5 / phase 'establish'
Aug 24 23:44:25 MyArchBox NetworkManager[578]: ** Message: nm-pptp-ppp-plugin: (nm_phasechange): status 11 / phase 'disconnect'
Aug 24 23:44:25 MyArchBox NetworkManager[578]: Connection terminated.
Aug 24 23:44:25 MyArchBox NetworkManager[578]: ** Message: nm-pptp-ppp-plugin: (nm_phasechange): status 1 / phase 'dead'
Aug 24 23:44:25 MyArchBox dbus[579]: [system] Rejected send message, 10 matched rules; type="error", sender=":1.51" (uid=0 pid=1938 comm="/usr/lib/networkmanager/nm-pptp-service ") interface="(unset)" member="(unset)" error name="org.freedesktop.DBus.Error.UnknownMethod" requested_reply="0" destination=":1.52" (uid=0 pid=1945 comm="/sbin/pppd pty /sbin/pptp 192.168.146.114 --nolaunc")
Aug 24 23:44:25 MyArchBox NetworkManager[578]: ** Message: nm-pptp-ppp-plugin: (nm_exit_notify): cleaning up
Aug 24 23:44:25 MyArchBox pppd[1945]: Exit.
Aug 24 23:44:25 MyArchBox NetworkManager[578]: ** (nm-pptp-service:1938): WARNING **: pppd exited with error code 16
Aug 24 23:44:45 MyArchBox NetworkManager[578]: <info> VPN service 'pptp' disappeared
If you've gotten this far, thank you for taking the time to read through all this! Any help that you can give would be much appreciated.
Last edited by greyseal96 (2014-08-27 15:20:02)

Hmm, not sure about the 3.16 series kernel, but I found that when I upgraded to kernel 3.18 the PPTP VPN also stopped working. This time, though, it was because, for some reason, there was a change in kernel 3.18 where the firewall kernel modules necessary for the VPN don't get loaded so the firewall won't allow some of the PPTP traffic from the remote side back in. Since the firewall is stateful, these modules need to be loaded so that the firewall can know that the incoming PPTP traffic from the remote side is part of an existing connection. Here's what my network manager logs looked like:
NetworkManager[619]: <info> Starting VPN service 'pptp'...
NetworkManager[619]: <info> VPN service 'pptp' started (org.freedesktop.NetworkManager.pptp), PID 31139
NetworkManager[619]: <info> VPN service 'pptp' appeared; activating connections
NetworkManager[619]: <info> VPN connection 'MyVPN' (ConnectInteractive) reply received.
NetworkManager[619]: <info> VPN plugin state changed: starting (3)
NetworkManager[619]: ** Message: pppd started with pid 31148
NetworkManager[619]: <info> VPN connection 'MyVPN' (Connect) reply received.
pppd[31148]: Plugin /usr/lib/pppd/2.4.7/nm-pptp-pppd-plugin.so loaded.
NetworkManager[619]: Plugin /usr/lib/pppd/2.4.7/nm-pptp-pppd-plugin.so loaded.
NetworkManager[619]: ** Message: nm-pptp-ppp-plugin: (plugin_init): initializing
pppd[31148]: pppd 2.4.7 started by root, uid 0
NetworkManager[619]: ** Message: nm-pptp-ppp-plugin: (nm_phasechange): status 3 / phase 'serial connection'
pppd[31148]: Using interface ppp0
pppd[31148]: Connect: ppp0 <--> /dev/pts/5
NetworkManager[619]: Using interface ppp0
NetworkManager[619]: Connect: ppp0 <--> /dev/pts/5
NetworkManager[619]: ** Message: nm-pptp-ppp-plugin: (nm_phasechange): status 5 / phase 'establish'
NetworkManager[619]: <info> (ppp0): new Generic device (driver: 'unknown' ifindex: 7)
NetworkManager[619]: <info> (ppp0): exported as /org/freedesktop/NetworkManager/Devices/6
pptp[31150]: nm-pptp-service-31139 log[main:pptp.c:333]: The synchronous pptp option is NOT activated
pptp[31157]: nm-pptp-service-31139 log[ctrlp_rep:pptp_ctrl.c:258]: Sent control packet type is 1 'Start-Control-Connection-Request'
pptp[31157]: nm-pptp-service-31139 log[ctrlp_disp:pptp_ctrl.c:758]: Received Start Control Connection Reply
pptp[31157]: nm-pptp-service-31139 log[ctrlp_disp:pptp_ctrl.c:792]: Client connection established.
pptp[31157]: nm-pptp-service-31139 log[ctrlp_rep:pptp_ctrl.c:258]: Sent control packet type is 7 'Outgoing-Call-Request'
pptp[31157]: nm-pptp-service-31139 log[ctrlp_disp:pptp_ctrl.c:877]: Received Outgoing Call Reply.
pptp[31157]: nm-pptp-service-31139 log[ctrlp_disp:pptp_ctrl.c:916]: Outgoing call established (call ID 0, peer's call ID 25344).
pppd[31148]: LCP: timeout sending Config-Requests <===HERE IS WHERE THE CONNECTION FAILS BECAUSE THE MODULES AREN'T LOADED.
pppd[31148]: Connection terminated.
NetworkManager[619]: LCP: timeout sending Config-Requests
NetworkManager[619]: ** Message: nm-pptp-ppp-plugin: (nm_phasechange): status 11 / phase 'disconnect'
NetworkManager[619]: Connection terminated.
NetworkManager[619]: <warn> VPN plugin failed: connect-failed (1)
NetworkManager[619]: ** Message: nm-pptp-ppp-plugin: (nm_phasechange): status 1 / phase 'dead'
pppd[31148]: Modem hangup
pppd[31148]: Exit.
NetworkManager[619]: <warn> VPN plugin failed: connect-failed (1)
NetworkManager[619]: Modem hangup
NetworkManager[619]: ** Message: nm-pptp-ppp-plugin: (nm_exit_notify): cleaning up
NetworkManager[619]: <warn> VPN plugin failed: connect-failed (1)
NetworkManager[619]: <info> VPN plugin state changed: stopped (6)
NetworkManager[619]: <info> VPN plugin state change reason: unknown (0)
NetworkManager[619]: <warn> error disconnecting VPN: Could not process the request because no VPN connection was active.
NetworkManager[619]: ** (nm-pptp-service:31139): WARNING **: pppd exited with error code 16
NetworkManager[619]: <info> VPN service 'pptp' disappeared
To fix this, I had to add a file to the /etc/modules-load.d directory to have the modules loaded into the kernel at boot. I just created a file called netfilter.conf and put the following in it:
nf_nat_pptp
nf_conntrack_pptp
nf_conntrack_proto_gre
Not sure if this addresses your problem or not, but maybe it's worth a look.

[Solved] NetworkManager deauthenticating?

Similar Messages

Maybe you are looking for