wifi connection on hotspot with wpa enterprise on 22.04

[VAN LAETHEM]

With 20.04 I used a wifi connection with a hotspot Telenet with following parametres:
security : WPA2 entreprise
authentification : tunneled TLS
no AC certificat drequired
inner authentication : MSCHAPV2(non EAP)
user name: my id
password : my pswd

with 22.04 it doesn’t work anymore nor with the internal broadcom wifi nor with dongles (nor my Dlink 140 nor TP-link WN7200)

This problem is only present with hotspot requesting an identification (user+pswd) awith hotspots without identification everything is OK

in appendice some infos
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu82
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: michelvlt 1725 F.... pulseaudio
 /dev/snd/pcmC0D0p: michelvlt 1725 F...m pulseaudio
CasperMD5CheckResult: pass
CurrentDesktop: MATE
DistroRelease: Ubuntu 22.04
IfupdownConfig:
 # interfaces(5) file used by ifup(8) and ifdown(8)
 # Include files from /etc/network/interfaces.d:
 source /etc/network/interfaces.d/*
InstallationDate: Installed on 2022-04-21 (7 days ago)
InstallationMedia: Ubuntu-MATE 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419)
IpRoute:
 default via 192.168.86.254 dev wlp3s0 proto dhcp metric 600
 10.101.9.0/24 dev pan1 proto kernel scope link src 10.101.9.1 linkdown
 169.254.0.0/16 dev pan1 scope link metric 1000 linkdown
 192.168.86.0/24 dev wlp3s0 proto kernel scope link src 192.168.86.157 metric 600
MachineType: Apple Inc. MacBookPro8,1
NonfreeKernelModules: wl
Package: wpa
PackageArchitecture: amd64
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-25-generic root=UUID=90724096-caa9-4e64-820f-c775b9de339c ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30
RelatedPackageVersions:
 linux-restricted-modules-5.15.0-25-generic N/A
 linux-backports-modules-5.15.0-25-generic N/A
 linux-firmware 20220329.git681281e4-0ubuntu1
Tags: jammy
Uname: Linux 5.15.0-25-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
_MarkForUpload: True
dmi.bios.date: 06/13/2019
dmi.bios.release: 0.1
dmi.bios.vendor: Apple Inc.
dmi.bios.version: 87.0.0.0.0
dmi.board.asset.tag: Base Board Asset Tag#
dmi.board.name: Mac-94245B3640C91C81
dmi.board.vendor: Apple Inc.
dmi.board.version: MacBookPro8,1
dmi.chassis.type: 10
dmi.chassis.vendor: Apple Inc.
dmi.chassis.version: Mac-94245B3640C91C81
dmi.modalias: dmi:bvnAppleInc.:bvr87.0.0.0.0:bd06/13/2019:br0.1:svnAppleInc.:pnMacBookPro8,1:pvr1.0:rvnAppleInc.:rnMac-94245B3640C91C81:rvrMacBookPro8,1:cvnAppleInc.:ct10:cvrMac-94245B3640C91C81:skuSystemSKU#:
dmi.product.family: MacBook Pro
dmi.product.name: MacBookPro8,1
dmi.product.sku: System SKU#
dmi.product.version: 1.0
dmi.sys.vendor: Apple Inc.
nmcli-nm:
 RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN
 running 1.36.4 connected started full enabled enabled enabled enabled enabled

[Norbert (nrbrtx)]

Please run

apport-collect 1970799

[Ubuntu Kernel Bot (ubuntu-kernel-bot)]

This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:

apport-collect 1970799

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.

[VAN LAETHEM (macavlt)]

apport information

[VAN LAETHEM (macavlt)]

apport information

[VAN LAETHEM (macavlt)]

apport information

[VAN LAETHEM (macavlt)]

apport information

[VAN LAETHEM (macavlt)]

apport information

[VAN LAETHEM (macavlt)]

apport information

[VAN LAETHEM (macavlt)]

apport information

[VAN LAETHEM (macavlt)]

apport information

[VAN LAETHEM (macavlt)]

apport information

[VAN LAETHEM (macavlt)]

apport information

[VAN LAETHEM (macavlt)]

apport information

[VAN LAETHEM (macavlt)]

apport information

[VAN LAETHEM (macavlt)]

apport information

[VAN LAETHEM (macavlt)]

apport information

[VAN LAETHEM (macavlt)]

apport information

[VAN LAETHEM (macavlt)]

apport information

[VAN LAETHEM (macavlt)]

apport information

[VAN LAETHEM (macavlt)]

apport information

[VAN LAETHEM (macavlt)]

apport information

[VAN LAETHEM (macavlt)]

apport information

[VAN LAETHEM (macavlt)]

apport information

[VAN LAETHEM (macavlt)]

apport information

[VAN LAETHEM (macavlt)]

apport information

[VAN LAETHEM (macavlt)]

apport information

[VAN LAETHEM (macavlt)]

apport information

[VAN LAETHEM (macavlt)]

apport information

[VAN LAETHEM (macavlt)]

apport information

[VAN LAETHEM (macavlt)]

apport information

[VAN LAETHEM (macavlt)]

apport information

[Sebastien Bacher (seb128)]

Thank you for your bug report. Could you edit /lib/systemd/system/wpa_supplicant.service to add a '-d' to the ExecStart cmd, restart, try to connect and share the 'journalctl -b 0' log from the system?

It would also be worth trying if https://launchpad.net/ubuntu/+source/wpa/2:2.10-6ubuntu1 makes a difference for you, could be the same issue with legacy server

[VAN LAETHEM (macavlt)]

here is the result of the journalctl

[VAN LAETHEM (macavlt)]

I already tried to apply
https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1963834
but this doesn't help.

I also tried
https://ubuntuforums.org/showthread.php?t=2474436
but doesn't help neither

[VAN LAETHEM (macavlt)]

for https://launchpad.net/ubuntu/+source/wpa/2:2.10-6ubuntu1

i'm a bit lost! What do I have to do with the 3 available files?

[Oibaf (oibaf)]

Just update your Ubuntu and make sure to have wpasupplicant version 2.10-6ubuntu1.

In a shell you should see:

$ dpkg -l | grep wpasupplicant
ii wpasupplicant 2:2.10-6ubuntu1

[VAN LAETHEM (macavlt)]

Dear,

my ubuntu is already uptodate and the result of the command is :

$ dpkg -l | grep wpasupplicant
ii wpasupplicant 2:2.10-6ubuntu1 amd64 client support for WPA and WPA2 (IEEE 802.11i)

for the moment I use a 18.04.6 version when i need to be connected to this hotspot
(all other recent efi Linux version I have tested present the same problem (fedora 35; debian 11.3; freeBSD)

thanks for your support

[Sebastien Bacher (seb128)]

The update on bug #1974428 fixed an issue where only WPA3 compatible devices would be able to connect to the hotspot, https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/commit/6a82dd18, could you try if the update is improving things for you? bug #1972790 is another similar report

[VAN LAETHEM (macavlt)]

I read https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/commit/6a82dd18
and identified the 4 files that must be adapted but ..... there is not directory /src/core or supplicant on my disk and so no files that i can adapt.

I don't identify what i have to do, sorry!

[Sebastien Bacher (seb128)]

you don't need to patch, just install the standard Ubuntu update provided on bug #1974428

[VAN LAETHEM (macavlt)]

update installed and
~$ NetworkManager -V
1.36.6

To test i need to be at another location. Feedback Thursday
Thanks

[VAN LAETHEM (macavlt)]

I'm in the location where i can test the hotspot (for 3 days)......

dammed ... it doesn't work !

is there any additional info you need?

[Sebastien Bacher (seb128)]

is that still an issue? is your issue connecting to a wifi or creating an hotspot? the 'hotspot' the description is a bit unclear

[VAN LAETHEM (macavlt)]

the issue is in the usage of an existing hotspot. Telenet is an ISP present in Belgium and every customer box is potentially an hotspot for the other customers of the brand.
When I'm on holiday I always try to used that interesting system.

i will be on holiday (again :-) ) in 2/3 days and will check if there is progress.

thanks for your support

[Sebastien Bacher (seb128)]

Ok, thanks. Could you also try to get a journal log again? The one you had only included the first page of the log, you probably want to do

$ journalctl -b 0 > journal.log

and attach the journal.log to the report. Or just 'journalctl -f' and then try to connect and add the lines printed

[VAN LAETHEM (macavlt)]

OK, I'm now on site ... and it works

here is the journal log

thanks for the efforts of the team

[Sebastien Bacher (seb128)]

oh great, let's close the bug then, thanks!