My machine has Wi-Fi Hotspot broken after upgrade to 22.04

[Kris]

* Impact
The hotspot feature fails to forward the data to the clients

* Test case
- log into an Ubuntu or GNOME session
- connect the machine to an eth cable for internet
- go to gnome-control-center -> wifi
- enable the hotspot from the menu in the headerbar
- connect another device to the wifi created
-> the client should connect and access to internet work correctly

Upon updating to 22.04, none of my machines can use the connection.

[Sebastien Bacher (seb128)]

Thank you for your bug report. Could you add the 'journalctl -b 0 > log' to the report after triggering the issue?

[Kris (kriscr)]

Add logging

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[Aurelijus Rinkevicius (odysei)]

I wonder if this is anyhow connected: https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1963834

[Muhammad Hafidz Pratama (inmy-darkzone)]

I'm kind of getting this bug but not sure if it's the same situation since I still able to connect using QR code.

Basically the difference from my case is :

...
- connect another device to the wifi created
- fail to connect after input password (already tried change password many time but still not working)
- success connecting after scan QR code (I'm using mobile device obviously)

Maybe there are some problem with the password security since Security type of the wi-fi hotspot can not be change and stuck at WPA (if I'm not wrong, the last config of my wi-fi hotspot security type before upgrade to 22.04 is WPA2-PSK).

[Jeremy Bícha (jbicha)]

As a workaround, open the installed app "Advanced Network Configuration"
Select Hotspot
Click the Gear button
Try changing Wi-Fi Security settings to something that works for you.

I was unable to duplicate your bug with 2 clients, an Android phone and an Ubuntu 22.04 LTS install. Both were able to connect to the hotspot without a problem.

[Miroslav Šimko (msimko81)]

I am not able to apply the workaround described by Jeremy.

I use KDE and there is no Advanced Network Configuration available. However, I can navigate to the System Settings - Connections - Configuration and the modal dialog with hotspot configuration pops up. The dialog enables to fill in Hotspot name and Hotspot password. However, even after I changed the settings (both name and password) and reenabled the hotspot, the new settings were not taken into the account. The hotspot with old name and without password was opened (my original settings).

I also tried to manually configure the hotspot related WiFi connection (same system settings view), with the same result - the new settings were not taken into the account. From my client, I can only see the original hotspot SSID, can connect to it without password, but there is no internet connection.

[Jeremy Bícha (jbicha)]

Miroslav, you can install the app I referred to with this command:

sudo apt install network-manager-gnome

I think it will show in your app launcher then. If not, the command to run the app is

nm-connection-editor

[Miroslav Šimko (msimko81)]

Thank you Jeremy for assistance. After installing network-manager-gnome, I was able to follow the steps you described.
However, even with configured hotspot wifi security, there is no internet connection on client's side. The client can connect to the hotspot wifi (using the changed security settings), but cannot connect to the internet. I tried the following two security settings with same result:
- None (my original setting)
- WPA/WPA2 Personal
(another security settings didn't worked for me at all)

Just to mention, I am able to ping my cell phone (wifi hotspot client) from my ubuntu host when connected.

[jorge (jorgemtds)]

I tried today to activate the Hotspot for the first time on 22.04... and got his exact problem... no connection is possible.

[Sebastien Bacher (seb128)]

Could someone having the issue report it upstream on https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/issues ?

[Sebastien Bacher (seb128)]

@jorge, by no connection do you mean not possible to connect or the client connect but doesn't have internet working?

the is bug #1972790 which is somehow similar

could someone having the issue do 'journalctl -f', try to connect a client and add the debug log (editing the wpa service to add the -d debug flag as described on bug #1958267 would be even nicer)

[Miroslav Šimko (msimko81)]

@seb128 here you are, the output of `journalctl -f`:

<pre>
Jul 06 12:46:39 miro-e495 kernel: rtw_8822be 0000:04:00.0: start vif 48:5f:99:6d:7c:bd on port 0
Jul 06 12:46:39 miro-e495 avahi-daemon[872]: Leaving mDNS multicast group on interface wlp4s0.IPv6 with address fe80::b96:ef70:3fb6:bd8a.
Jul 06 12:46:39 miro-e495 avahi-daemon[872]: Interface wlp4s0.IPv6 no longer relevant for mDNS.
Jul 06 12:46:39 miro-e495 dnsmasq[37445]: exiting on receipt of SIGTERM
Jul 06 12:46:39 miro-e495 avahi-daemon[872]: Withdrawing address record for 10.42.0.1 on wlp4s0.
Jul 06 12:46:39 miro-e495 avahi-daemon[872]: Leaving mDNS multicast group on interface wlp4s0.IPv4 with address 10.42.0.1.
Jul 06 12:46:39 miro-e495 avahi-daemon[872]: Interface wlp4s0.IPv4 no longer relevant for mDNS.
Jul 06 12:46:39 miro-e495 NetworkManager[879]: <info> [1657104399.1914] device (wlp4s0): supplicant interface state: completed -> disconnected
Jul 06 12:46:42 miro-e495 NetworkManager[879]: <info> [1657104402.9197] audit: op="statistics" interface="enp2s0" ifindex=2 args="0" pid=1423 uid=1000 result="success"
Jul 06 12:46:47 miro-e495 wpa_supplicant[913]: wlp4s0: Reject scan trigger since one is already pending
Jul 06 12:46:49 miro-e495 systemd[1]: NetworkManager-dispatcher.service: Deactivated successfully.
Jul 06 12:46:50 miro-e495 NetworkManager[879]: <info> [1657104410.7461] audit: op="statistics" interface="enp2s0" ifindex=2 args="2000" pid=1423 uid=1000 result="success"
Jul 06 12:46:52 miro-e495 NetworkManager[879]: <info> [1657104412.7524] device (wlp4s0): Activation: starting connection 'e495-hotspot' (d8c2e1e6-454b-452f-8f48-0c44829a51bd)
Jul 06 12:46:52 miro-e495 NetworkManager[879]: <info> [1657104412.7526] audit: op="connection-add-activate" uuid="d8c2e1e6-454b-452f-8f48-0c44829a51bd" name="e495-hotspot" pid=1423 uid=1000 result="success"
Jul 06 12:46:52 miro-e495 NetworkManager[879]: <info> [1657104412.7534] device (wlp4s0): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed')
Jul 06 12:46:52 miro-e495 NetworkManager[879]: <info> [1657104412.7549] device (wlp4s0): state change: prepare -> config (reason 'none', sys-iface-state: 'managed')
Jul 06 12:46:52 miro-e495 NetworkManager[879]: <info> [1657104412.7554] device (wlp4s0): Activation: (wifi) connection 'e495-hotspot' requires no security. No secrets needed.
Jul 06 12:46:52 miro-e495 NetworkManager[879]: <info> [1657104412.9712] Config: added 'ssid' value 'e495-hotspot'
Jul 06 12:46:52 miro-e495 NetworkManager[879]: <info> [1657104412.9713] Config: added 'mode' value '2'
Jul 06 12:46:52 miro-e495 NetworkManager[879]: <info> [1657104412.9713] Config: added 'frequency' value '2412'
Jul 06 12:46:52 miro-e495 NetworkManager[879]: <info> [1657104412.9714] Config: added 'key_mgmt' value 'NONE'
Jul 06 12:46:52 miro-e495 wpa_supplicant[913]: Note: nl80211 driver interface is not designed to be used with ap_scan=2; this can result in connection failures
Jul 06 12:46:56 miro-e495 kernel: rtw_8822be 0000:04:00.0: change vif 48:5f:99:6d:7c:bd (2)->(3), p2p (0)->(0)
Jul 06 12:46:56 miro-e495 kernel: rtw_8822be 0000:04:00.0: stop vif 48:5f:99:6d:7c:bd on port 0
Jul 06 12:46:56 miro-e495...

[Sebastien Bacher (seb128)]

Thank, there is a warning similar to bug #1886169 in that log, unsure if that's your issue though

[Umar B (mintprower)]

I seem to be having similar issues. I could connect my android phone for a bit then it just kinda stopped. My Ipad has never been able to join the network. sometimes with an error saying the channel is too busy (fixed that by starting with nmcli and selecting another channel). Otherwise, the Ipad gives the error "unable to join network" (A nice helpful message, thanks apple)

All devices can connect to other networks (android hotstpot and wifi router)

I've attached my log file if it'll be any help

This might be the wrong place to post, but it was the most recent relevant bug report.

[Samuel Rossille (samuel-rossille)]

I have a similar issue.
Here is what happens : I can connect to the hotspot just fine, but the connected devices don't have access to internet (tested with an android device and a windows device).
I tried all the wifi security options one by one, and there is the same behavior with each of them.
The hotspot worked fine with Ubuntu 21.10.
Hope this helps and sorry for the noise if it's unrelated.

[doan van thang (thang1160)]

I got a workaround by disabling the firewall. But the moment you turn it on (even if clients connected beforehand), the internet loses connection again. Quite annoying (also dangerous) for hotspot

[Jeremy Bícha (jbicha)]

doan van thang, please report a new bug for your issue.

[Rob Brown-Bayliss (rb8068)]

I have an issue. I can connect to the hotspot just fine, but the connected devices get disconnected almost immediately

I tried all the wifi security options one by one, and there is the same behavior with each of them.

from journalctrl output
Nov 11 08:36:29 tortuga wpa_supplicant[19131]: wlo2: AP-STA-CONNECTED a6:81:e8:e3:73:66
Nov 11 08:36:29 tortuga wpa_supplicant[19131]: wlo2: EAPOL-4WAY-HS-COMPLETED a6:81:e8:e3:73:66
Nov 11 08:36:47 tortuga wpa_supplicant[19131]: wlo2: AP-STA-DISCONNECTED a6:81:e8:e3:73:66

How do I get this to work? The Ubuntu 22.04 machine gets internet from a wired connection to the home router, the router provided DHCP and DNS services

[Dilip (dilip-meet)]

WiFi hotspot not working for me in 22.04

[Dilip (dilip-meet)]

I installed a fresh 22.04 still no luck. I check Gnome bug reports, they are asking to talk to the distro. Thanks.

[fabio andres pino gutierrez (fabpin04)]

My error is quite annoying to, already the hotspot work on the SO, the activated the wifi and detect the wifi, but when my cellphone connected to the hotspot assigned a public ip, for been exactly assigned by default the DHCP the ip 10.42.0.189 with a mask subred 255.255.255.0, but the computer than is working like service DHCP already had 192.168.1.56, i'm undestand if this hotspot is working like a bridge appliance, but, this time didnt is the case, because the default router has the 192.168.1.254, so the subred mask of the segment of the red is from 192.168.1.0 - 192.168.1.255 wtf, why assign me a public IP, jajajaj, i will send the evidence.

I dont know, if this error has connected, but, when turn on the Firewall (UFW), desconect the device wireless, restar my pc, connect again the wireless and shutdown the firewall again, next turn on the hostpot, just works LOL. all device connected and navigate.

[Christopher Pastore (cpastore)]

I have the same issue as Samuel.
I can connect to the hotspot just fine, but the connected devices don't have access to internet.

Strangely enough I did find one workaround that fixes the problem for me in this answer:

https://askubuntu.com/a/1444778

The -999 priority doesn't seem to matter, but if I set the hotspot to start automatically and then reboot, connected devices can access the internet. Also, if the hotspot is started automatically I can stop and re-start it and things still work.

[Mark Hampton (mark-hampton)]

I'm having similar issues. Following what Fabio mentioned, I think I had a firewall issue but disabling the firewall was not enough, I needed to restart the wifi after disabling the firewall. I guess that is the sequence which addresses the problem for Fabio too.