FS#59645 - [networkmanager] Stopped connecting when using 802.1X

Attached to Project: Arch Linux
Opened by Luis (nohive) - Monday, 13 August 2018, 16:03 GMT
Last edited by Toolybird (Toolybird) - Monday, 29 May 2023, 03:36 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To Jan de Groot (JGC)
Jan Alexander Steffens (heftig)
Architecture All
Severity Medium
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:

After upgrading from extra/networkmanager 1.12.0-1 to version 1.12.3dev+1+g0a3755c17-1 the system can't connect to the network using a standard ethernet RJ45 wired connection that happens to use 802.1X security settings.

Before the upgrade, it used to work. I've tried to downgrade the package to 1.12.0-1 and I can confirm that it works in the old version.

A regular non-802.1X connection works fine with the 1.12.3dev+1+g0a3755c17-1 version.

802.1X settings tested: auhtentication PEAP with MSCHAPv2.

Additional info:
* package version(s): extra/networkmanager 1.12.3dev+1+g0a3755c17-1

Steps to reproduce:

1) Upgrade or install version 1.12.3dev+1+g0a3755c17-1
2) Try to connect to the wired network using either the "nmtui" command or the KDE Network Applet;
3) Observe that it takes a while and it fails.
This task depends upon

Closed by  Toolybird (Toolybird)
Monday, 29 May 2023, 03:36 GMT
Reason for closing:  No response
Additional comments about closing:  Plus it's old and stale. If still an issue, please report upstream.
Comment by Jonathon (jonathon) - Monday, 17 September 2018, 14:42 GMT
With network-manager-1.14.0-1, 802.1x configuration is no longer available via the network settings (nm-connection-editor) dialog box (editing existing or creating new). 802.1x auth will fail, though journalctl still shows 802.1x entries during the connection attempt for an existing connection.

(WPA2 Enterprise/PEAP still works fine over wifi.)
Comment by mattia (nTia89) - Friday, 25 February 2022, 16:10 GMT
Is this issue still valid with latest version of networkmanager?

Loading...