NetworkManager won't set wireless IP

herbert12345 · n00b Joined: 04 Sep 2007 Posts: 58

Hi,

I am somewhat stuck on my problem and sadly my ideas on what I can do or how to get meaningful debug output. Anyway, I had a running configuration for my home WLAN using NetworkManager. Now when NetworkManager tries to connect, it gets stuck and eventually fails at setting the network address (at least that is the last state the KDE NetworkManager plasmoid reports). nmcli just reports a timeout after 90 seconds. When use a LAN cable, NetworkManager works just fine (including dynamic IP address).

I think I have run an update and might have overlooked an information message that I should do something.

Connecting to the WLAN works fine from other devices and also via Windows from the same machine with the same network device. I have not changed anything on the WLAN settings.

NetworkManager shows the list of surrounding wireless networks, and wireless is activated.

I am running networkmanager-0.9.8.2 and my emerge --info is:

BillWho · Veteran Joined: 03 Mar 2012 Posts: 1600 Location: US

imaginasys · Posted: Fri Jun 21, 2013 3:11 am Post subject:

Can you show log of messages about your wlan interface.

e.g.

herbert12345 · n00b Joined: 04 Sep 2007 Posts: 58

Thank you for your replies. I tried genlop but found nothing relevant.

When trying to connect I get the following in my /var/log/messages

Velasticus · n00b Joined: 08 Jul 2013 Posts: 1

Note: I'm having the same exact problem after an upgrade to Gnome 3.8 (which updated NetworkManager in course).

If I turn off NM, nm-applet, etc. and run wpa_supplicant by itself then it works. However, when running under NetworkManager it reports that it cannot connect and gives the same (reason=3) error in the logs.

I've tried turning IPV6 off and setting it to link-local without success.

I'll attach logs if requested but they look nearly identical to herbert's logs.

Hopefully someone can point me in the right direction. In the meantime I'll try netctl to replace NetworkManager.

stens · Posted: Thu Jul 11, 2013 10:16 pm Post subject:

Hi,

I also experienced with the same issue.
NM is not able to connect to WiFi and strangely it can not connect to LAN at work, but LAN is fine at home

Everything pointed to DHCP, so I changed the use flags for networkmanager:

666threesixes666 · Posted: Fri Jul 12, 2013 2:39 am Post subject:

"everything pointed to dhcp" thats why i PM'ed to post what was loading upon init, and NM invokes dhcp not a rc script that should be removed. dhclient, dhcpcd, potato tomato.... im stumped, as his rc-update doesn't show dhcp scripts that need removed.

seems like reason3 went away for me when i moved up kernel versions to 3.9.9 & moved to udev ugly unreasonable names.

st3f4n2006 · n00b Joined: 07 Jul 2013 Posts: 8

what dhcpcd version you have and config you have? using the latest (5.99) i had problems getting an correct ip (it seems that the my dhcpcd was sending some weird MAC to the server - we use ipv4 and the client sent ipv6 unique id/ mac).
I had to disable "duid" in /etc/dhcpcd.conf and now everything works fine without any ipv6 configs (default NetworkManager)

Martux · Veteran Joined: 04 Feb 2005 Posts: 1917

Is there any fix for this yet? Having this issue now on two machines, with two different NICs and it's starting to get disgusting.
How does one set a static IP for wireless (with Networkmanager)? Troubleshooting and emerging different versions is pretty tough with no Internet...
_________________
"Coincidence is God's way of remaining anonymous."
Albert Einstein
"The road to success is always under construction"

666threesixes666 · Posted: Thu Jul 18, 2013 8:41 pm Post subject:

manually assign ip address for nm-applet (and i imagine kde's networkmanagement) attempt to connect to access point, cancel.... right click "edit connections" nm-applet.... click ap name, edit...

could you mask the newer versions, and revert back to 5.6.4 (where im not experiencing these problems?)