[Solved] Can't connect wifi with networkmanager

[Waterdevil]

Hello world,

every time I want to connect to a wifi access point with Network Manager I get this message:

[LIsLinuxIsSogood]

You probably just need the correct kernel configuration. Since you are using iwlwifi, I think that means you are in the clear once that is the case. Personally, because of my "less than adequate" NIC use proprietary drivers from Broadcom (wouldn't recommend doing btw), but still, this will give you an idea. I think for the open source drivers (iwlwifi, theres another couple ones missing here). Try checking the kernel for mac80211 and cfg80211 first and get back with those settings first.

[LIsLinuxIsSogood]

Also, just so you are aware it is probably better in the future to get your kernel config from the /proc filesystem location since that is gauranteed to be the one your running.

Here's the settings for kernel 4.12.10.

[LIsLinuxIsSogood]

And here's one more thing in case all that seems to check out...

IF you are going to use wpa_supplicant with NetworkManager, you will want to uncomment this section of the conf.d/net file. I believe

[Waterdevil]

My mods:

[LIsLinuxIsSogood]

waterdevil, check these two options as well...just in case...

This is for udev to function with NetworkManager as a "host"

[Waterdevil]

I can't find config.gz in the filesystem /, /boot or /boot/efi.
_________________
_____________________
Aut semper aut numquam

Main-Sys: LianLi modded Big Cube 8000,X11DPG-QT,MEM:64G,LSI 9305,HDD:102TB(16x3T,8x6T,4x1T,1x0,5Tm.2,4x0,5TSSD),nVidia GTX1060,NIC:2x10GbSFP+,Fans:20,PSU:1200W+500W,UPS:APC1500VA,FibreChannel,Tandberg LTO-6

[Waterdevil]

-*- Unix domain sockets
_________________
_____________________
Aut semper aut numquam

Main-Sys: LianLi modded Big Cube 8000,X11DPG-QT,MEM:64G,LSI 9305,HDD:102TB(16x3T,8x6T,4x1T,1x0,5Tm.2,4x0,5TSSD),nVidia GTX1060,NIC:2x10GbSFP+,Fans:20,PSU:1200W+500W,UPS:APC1500VA,FibreChannel,Tandberg LTO-6

[Waterdevil]

[LIsLinuxIsSogood]

How about these?

[LIsLinuxIsSogood]

Do you have dhclient installed? It is installed as part of package net-misc/dhcp-4.3.6 , if 'client' USE flag is in use.

[LIsLinuxIsSogood]

From the original post, what I'm trying to figure out, and that's something you may want to look into, which is why it attempts IPV6 connection The answer may be that either your kernel does not have ipv6 support enabled, and that could be one potential solution if that is the problem. Otherwise, the configuration of dhclient with NetworkManager needs to specify to use the x.x.x.x or ip version 4 protocol...do you get what i mean. If you can look first at the kernel, because it is the easier fix, then later at the configuration files. Try and see if the kernel is configured for IPV6. I think the kernel setting is CONFIG_IPV6, if not then change the N to a Y or M, and see what happens after you reboot. I'm running out of good things to offer here. But I believe you followed all the instructions when setting it up. By the way, how did you configure NetworkManager, or did you use the configuration out of the box so to speak.

[NeddySeagoon]

Waterdevil,

It looks like your kernel and wpa_supplicant settings are correct as your log shows that that your wifi associates and authenticates.
Then does it all over again.

This usually inhicates that you have several WiFi control systems fighting over the wifi, so at best, it works very briefly, then cycles.

First of all stop all the wifi controler you have running. This can be difficult if you think you only have one.
You can tell when you are successful as your wifi will not start automatically, further, when you start it manually, it will work.

As a first step, remove NetworkManager from the default runlevel and reboot.
_________________
Regards,

NeddySeagoon

Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail.

[LIsLinuxIsSogood]

I agree with Neddy, get a baseline first by getting it to work before you add it to the system default level.

Do you know if you are purposefully trying to connect via ipv4 or ipv6?

[charles17]

[NeddySeagoon]

There are two parts to getting wifi working.

The first part is getting associated and authenticated. That's the extra steps for Wifi.
After that's complete, the wifi interface can pass packets, just like a wired interface.

The second part is using the standard wired tools to set up the interface.
They work for both IPv4 and IPv6.

At the moment, the logs show that the getting associated and authenticated step is cycling forever, so the second step cannot complete.
_________________
Regards,

NeddySeagoon

Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail.

[LIsLinuxIsSogood]

Neddy, while that may be true, the info provided about the IEEE802.1X failed attempt seems to suggest that the issue is not something that cycles, but i am not positive.

I would still check kernel, for correct 80211 options, and then definitely take a chance to shut off other networking services. Then try starting NetworkManager.

[charles17]

[NeddySeagoon]

LIsLinuxIsSogood,

[Waterdevil]

Hi,

very good analysed - many thanks to all of you.

I had the wrong mac address in my wifi macfilter whitelist. Now it's the right and so it's working.

And sorry for long response, because I was at work.

Have a good time (with gentoo)
Andy
_________________
_____________________
Aut semper aut numquam

Main-Sys: LianLi modded Big Cube 8000,X11DPG-QT,MEM:64G,LSI 9305,HDD:102TB(16x3T,8x6T,4x1T,1x0,5Tm.2,4x0,5TSSD),nVidia GTX1060,NIC:2x10GbSFP+,Fans:20,PSU:1200W+500W,UPS:APC1500VA,FibreChannel,Tandberg LTO-6

[LIsLinuxIsSogood]

Ha, that certainly does go to show that these messages can only take you so far. Since there's no such message in most software that says something like, "Duh, you added the wrong address to that"...but seriously good luck as well (with gentoo) and HAVE FUN!