Created attachment 527002 [details] Log output when connecting to WPA-EAP network Hi, when using NetworkManager 1.10.2 and dhcpcd I'm experiencing some weirdness. I've always used only WPA-PSK networks and have had no issues connecting to them. Today I added a WPA-EAP network and now notice some very weird things. I'm on KDE and as such using the KDE NM applet. The WPA-EAP connection comes up, obtains an IPv4, but fails on v6 and disconnects. According to the logging dhcpcd doesn't support v6. It's compiled with v6 support and 'dhcpcd -6 <interface>' works fine on the CLI. Please note that on all my PSK networks, as well as this WPA-EAP network, the settings on the IPv6 tab are the same. Set to automatic and the require IPv6 is *not* checked. So I started digging in my logs a bit and it doesn't log anything DHCPv6 related at all with regards to my PSK networks. This probably explains why these work without issues. Basically there seem to be more issues thus: 1) dhcpcd has support for v6, but NetworkManager seems to disagree. dhcpcd is at v7.1 though, maybe there have been API changes that cause NetworkManager to think differently. Haven't tested with a v6.x dhcpcd 2) DHCPv6 doesn't seem to start on PSK networks thus, whilst it does on EAP 3) One would expect NM/DHCP to behave exactly the same on PSK as EAP networks. Settings in the tabs don't differ, why would it act differently then... As I can't pinpoint what causes these issues I've filed it under NetworkManager for now. It might belong to dhcpcd and/or the KDE NM applet however. These 2 lines are notable from the eap.log: apr 10 11:47:35 flaptoppy NetworkManager[4427]: <info> [1523353655.2849] dhcp6 (wlp2s0): activation: beginning transaction (timeout in 45 seconds) apr 10 11:47:35 flaptoppy NetworkManager[4427]: <warn> [1523353655.2849] dhcp6 (wlp2s0): the dhcpcd backend does not support IPv6 As stated there are no lines in my logs that contain 'dhcp6' at all when connecting to WPA-PSK networks.
Created attachment 527004 [details] emerge --info
Do you have the same problem(s) when using dhclient or the built-in DHCP client?
Tested with internal. Logs are attached as well as the connection files for these SSID's (from /etc/NetworkManager/system-connections). Didn't test with dhclient as I think it's utter garbage (https://bugzilla.redhat.com/show_bug.cgi?id=1093803 4 yrs and still no fix...) The connection seems to remain stable with the internal client. That said, on PSK networks it still doesn't seem to request DHCPv6 so the behaviour still differs. Potential issues 2 and 3 still seem to apply thus. Thanks for you reply :).
Created attachment 527012 [details] Config file for EAP SSID
Created attachment 527014 [details] Config file for PSK SSID
Created attachment 527016 [details] Log when connecting to EAP SSID with internal DHCP client
Created attachment 527018 [details] Log when connecting to PSK SSID with internal DHCP client
Maybe I started redirecting the logs too late. The following lines are missing from the attached logs. To avoid confusion on the actual DHCP client, here they are :): apr 10 16:51:45 flaptoppy NetworkManager[11187]: <info> [1523371905.4696] dhcp-init: Using DHCP client 'internal' apr 10 16:53:00 flaptoppy NetworkManager[11263]: <info> [1523371980.0968] dhcp-init: Using DHCP client 'internal'
Sorry, I forgot to respond here. This seems like an issue that deserves an upstream bug report. I don't think I will be able to help by looking at your logs.
Unclear if any upstream bug report was ever made.
