NetworkManager dhclient wpa_supp & ath10k kde-plasma no IP

stardotstar

Hi guys,

I am opening this thread because the original one was in Installing Gentoo and dealt with the problems I had initially with the ath10k wifi card on my Dell XPS15 9560.

These problems appear to be mostly resolved since I now have a KDE-Plasma desktop that is using NetworkManager and DHClient (having removed dhcpcd and netifrc in favour of a wpa_supp+NetworkManager and plasma-nm arrangement).

The current state of play is as follows:

1) When I boot and startx I have the Pasma NetworkManager in the system tray and can "see" the available ssids and when I attemtp to "connect" and enter the password (wpa/psk2) I am prompted for the kde keychain manager and then the password for the relevant ssid. The systray shows NM trying to associate but eventually it just pops up another dialogue asking for the password over and over.

2) When I use the konsole to start wpa_gui (as regular user) I am able to see the association through to all but the acquisition of an IP. I found this thread https://forums.gentoo.org/viewtopic-t-896510-start-0.html which seems to relate a similar story and when I manually execute dhclient wlp2s0 I get an IP and all is well (via the wpa_gui method) but then I am not using the plasma nm configuration

here is some of the info relevant to this:

the ifconfig showing my available interfaces:

charles17 · Advocate Joined: 02 Mar 2008 Posts: 3664

NeddySeagoon · Posted: Mon Jul 17, 2017 8:45 am Post subject:

charles17,

You are correct but if no /etc/init.d/net.* are defited (other than net.lo), it will be ignored
_________________
Regards,

NeddySeagoon

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

charles17 · Advocate Joined: 02 Mar 2008 Posts: 3664

eccerr0r · Posted: Mon Jul 17, 2017 8:55 am Post subject:

Yes, if using networkmanager, /etc/conf.d/net isn't needed; but the default /etc/init.d/net.lo is still needed.

Usually when I see the endless password prompt, it's one of these things:

- the key is wrong (possibly causing dhcp to fail)
- the key is having problems being saved (if the entry is user only, I believe it has a different password storage mechanism than if it's a systemwide entry) - usually due to consolekit/polkit problems.

Are you getting a consolekit session properly (does it work when using a consolekit enabled display manager?)
_________________
Intel Core i7 2700K/Radeon R7 250/24GB DDR3/256GB SSD
What am I supposed watching?

stardotstar · Posted: Mon Jul 17, 2017 9:05 am Post subject:

OK, I've removed conf.d/net and only had it in there because there is mention of it in what I could only see as independent of netifrc somewhere - but I've lost the wiki page in the reboots I've done. (If I can find this ill reference it but in the mean time)

I have found that if I stop the NetworkManager service and proceed to launch wpa_gui the interface is seen but no control signal can be sent from the gui until I bring the interface up with ifconfig and then initiate a scan with the wpa_cli...

stardotstar · Posted: Mon Jul 17, 2017 9:10 am Post subject:

charles17 · Advocate Joined: 02 Mar 2008 Posts: 3664

Use the -t (--tree) option for emerge.

Have you set sys-apps/openrc -netifrc in /etc/portage/package.use?

stardotstar · Posted: Mon Jul 17, 2017 9:42 am Post subject:

OK, I'll set that -netifrc now.

I'll add the tree tack and I can confirm that I have started with consolekit running (used the method for startx here (exec ck-launch-session dbus-launch --sh-syntax --exit-with-session <WINDOW_MANAGER>) and got no errors that I could see. This was after a reboot.

NetworkManager is just timing out as Inactive on boot and elsewhere from what I can see as I added timeout=100 to the conf.d/NetworkManager file and it just ticked down during boot up

When I stop NetworkManager I can then use wpa_gui / cli promptly but I still have to execute dhclient manually after assoc/auth

here's my latest dmesg
https://paste.pound-python.org/show/aNsoQUIldYzLwP4J28ft/

portage warns that I have no network management in built

eccerr0r · Posted: Mon Jul 17, 2017 9:49 am Post subject:

What happens if you simply create that directory /var/run/dhcp (though it's kind of strange it's not automatically being created...)

I'm using USE=dhclient with my networkmanager at the moment, though it shouldn't matter (but it uses different dhcp status files.)
_________________
Intel Core i7 2700K/Radeon R7 250/24GB DDR3/256GB SSD
What am I supposed watching?

NeddySeagoon · Posted: Mon Jul 17, 2017 9:51 am Post subject:

eccerr0r,

/var/run is normally a symlink to /run, if it exists at all.
/run won't appear if tmpfs is missing from the kernel but there is usually much more breakage if thats the case.
_________________
Regards,

NeddySeagoon

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

stardotstar · Posted: Mon Jul 17, 2017 10:59 am Post subject:

stardotstar · Posted: Mon Jul 17, 2017 1:34 pm Post subject:

for what it's worth I see the system-connection entry for the disARRAY ssid is populated but makes no mention of the passkey - I am assuming this is because, unlike the simple wpa_supp config where it is in plain text (readable by root/wheel) it is handled by the passwork keychain in NetworkManager and the Plasma-NM

eccerr0r · Posted: Mon Jul 17, 2017 2:56 pm Post subject:

Did you mark this network as "available to all users" or is this only available to current user?
The PSK should be stored in system-connections only if available to all users (but it should work either way...)

These system-connections should not be readable by the world... not sure what happened there?

Networkmanager calls wpa-supplicant eventually to handle the passkeys though I don't recall if it saves these files temporarily somewhere or not...
_________________
Intel Core i7 2700K/Radeon R7 250/24GB DDR3/256GB SSD
What am I supposed watching?

charles17 · Advocate Joined: 02 Mar 2008 Posts: 3664

stardotstar

Would you please show

your complete /etc/conf.d/wpa_supplicant if any
your /var/log/rc.log from last shutdown + reboot
output of rc-config show --all
output of rc-status --all

So we can see which services get started.

P.S.:
https://wiki.debian.org/WiFi/HowToUse#network-manager