Latest Fedora Hotspot no longer accepting connections

I have the latest Fedora 35 update and since about the last 2 “updates” the Wifi Hotspot no longer accepts connections, I’ve google and searched this forum. I tried the “trusted” fix, etc. Hotspot starts and runs without issue, but I can’t connect to it from Android or iOS.

Anyone have any ideas?

thank you in advance,
Smoke

I cannot see the config you have for your network, so am not certain of this answer but it may be reasonable.

My network is 100% wifi.
With my android phone connected to wifi, if I decide to activate the phone as a hotspot it disables all wifi to the phone and the phone becomes an AP and uses my cellular data for the wifi hotspot. Other than using my cellular data my phone has no internet connections in this config.

If you are using the PC as a wifi hotspot, does that mean that you have ethernet to the pc then the PC is the hotspot for wifi? Or is the router a wifi hotspot (AP) and you are also trying to use the PC as an additional hotspot?

Please provide a bit more detail so we can understand the layout and what you are trying to achieve.

Hi Jeff,

Let me clarify, I have an ASUS Zenith Extreme Alpha board with on board Wifi and 2 Ethernet ports (connected to LAN). I have no other Wifi in my location (this is by design). If I need to update my phones I usually toggle on the Fedora / Gnome Hotspot and the phones connect and update as required. I’ve been doing this since around Fedora 32. About an update or 2 ago, the Hotspot still starts and looks fine (no errors I can see) but it no longer accepts connections from ANY of my Android or iOS devices (I have about 6 phones old/new). Thinking it was something with my install over time, I reinstalled Fedora 35 last weekend and the same problem persists. I’ve also tried Fedora 34 again (to rule out any recent HW failure) and it works as it did before.

Thank you!
smoke

Ok, thanks for the clarification.

This likely to be a regression in code (but may be something else). Please post the output of inxi -Nxx followed by dmesg | grep -i wl so we can see the hardware config and what the system is doing during boot with the wifi interface.

It may be helpful if you do the same both when it is working and when it is not so we can see the differences in what is reported…

Blockquote
[smoke@rogtr ~]$ inxi -Nxx
Network:
Device-1: Intel Wireless-AC 9260 driver: iwlwifi v: kernel bus-ID: 03:00.0
chip-ID: 8086:2526
Device-2: Intel I211 Gigabit Network vendor: ASUSTeK driver: igb
v: kernel port: 2000 bus-ID: 05:00.0 chip-ID: 8086:1539
Device-3: Aquantia AQC107 NBase-T/IEEE 802.3bz Ethernet [AQtion]
vendor: ASUSTeK driver: atlantic v: kernel port: N/A bus-ID: 09:00.0
chip-ID: 1d6a:07b1
Device-4: Intel Wireless-AC 9260 Bluetooth Adapter type: USB
driver: btusb bus-ID: 1-2:4 chip-ID: 8087:0025

Blockquote
[smoke@rogtr ~]$ dmesg | grep -i wl
[ 8.666483] iwlwifi 0000:03:00.0: enabling device (0000 → 0002)
[ 8.705209] iwlwifi 0000:03:00.0: WRT: Overriding region id 0
[ 8.705214] iwlwifi 0000:03:00.0: WRT: Overriding region id 1
[ 8.705216] iwlwifi 0000:03:00.0: WRT: Overriding region id 2
[ 8.705217] iwlwifi 0000:03:00.0: WRT: Overriding region id 3
[ 8.705219] iwlwifi 0000:03:00.0: WRT: Overriding region id 4
[ 8.705220] iwlwifi 0000:03:00.0: WRT: Overriding region id 6
[ 8.705221] iwlwifi 0000:03:00.0: WRT: Overriding region id 8
[ 8.705222] iwlwifi 0000:03:00.0: WRT: Overriding region id 9
[ 8.705222] iwlwifi 0000:03:00.0: WRT: Overriding region id 10
[ 8.705223] iwlwifi 0000:03:00.0: WRT: Overriding region id 11
[ 8.705224] iwlwifi 0000:03:00.0: WRT: Overriding region id 15
[ 8.705225] iwlwifi 0000:03:00.0: WRT: Overriding region id 16
[ 8.705226] iwlwifi 0000:03:00.0: WRT: Overriding region id 18
[ 8.705227] iwlwifi 0000:03:00.0: WRT: Overriding region id 19
[ 8.705228] iwlwifi 0000:03:00.0: WRT: Overriding region id 20
[ 8.705229] iwlwifi 0000:03:00.0: WRT: Overriding region id 21
[ 8.705230] iwlwifi 0000:03:00.0: WRT: Overriding region id 28
[ 8.705434] iwlwifi 0000:03:00.0: loaded firmware version 46.4e1ceb39.0 9260-th-b0-jf-b0-46.ucode op_mode iwlmvm
[ 8.971969] iwlwifi 0000:03:00.0: Detected Intel(R) Wireless-AC 9260 160MHz, REV=0x324
[ 9.019764] iwlwifi 0000:03:00.0: base HW address: 18:56:80:6a:59:78
[ 9.089508] ieee80211 phy0: Selected rate control algorithm ‘iwl-mvm-rs’
[ 9.095156] iwlwifi 0000:03:00.0 wlp3s0: renamed from wlan0
[ 706.481643] IPv6: ADDRCONF(NETDEV_CHANGE): wlp3s0: link becomes ready
[ 1021.137649] IPv6: ADDRCONF(NETDEV_CHANGE): wlp3s0: link becomes ready
[ 3858.211859] IPv6: ADDRCONF(NETDEV_CHANGE): wlp3s0: link becomes ready
[ 3946.287114] IPv6: ADDRCONF(NETDEV_CHANGE): wlp3s0: link becomes ready
[ 6399.415866] IPv6: ADDRCONF(NETDEV_CHANGE): wlp3s0: link becomes ready

According to the output you posted, wlp3s0 is only being configured with IPv6. I suspect you may need to look at the config for your hotspot and verify that it is properly set up for IPv4. I should also have asked for the output of ip a so we could see the ip config on that interface as well, but the dmesg output confirms it is only being configured as IPv6.

[smoke@rogtr ~]$ ip a
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
valid_lft forever preferred_lft forever
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
2: enp9s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000
link/ether 40:b0:76:d7:fb:2f brd ff:ff:ff:ff:ff:ff
inet 192.168.1.198/24 brd 192.168.1.255 scope global dynamic noprefixroute enp9s0
valid_lft 86296sec preferred_lft 86296sec
inet6 fe80::7096:3f01:4d11:e0fe/64 scope link noprefixroute
valid_lft forever preferred_lft forever
3: enp5s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000
link/ether 40:b0:76:d7:fb:2e brd ff:ff:ff:ff:ff:ff
inet 192.168.1.196/24 brd 192.168.1.255 scope global dynamic noprefixroute enp5s0
valid_lft 86189sec preferred_lft 86189sec
inet6 fe80::ed13:9160:22f4:ef0b/64 scope link noprefixroute
valid_lft forever preferred_lft forever
4: wlp3s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
link/ether 18:56:80:6a:59:78 brd ff:ff:ff:ff:ff:ff
inet 10.42.0.1/24 brd 10.42.0.255 scope global noprefixroute wlp3s0
valid_lft forever preferred_lft forever
inet6 fe80::680a:5ba8:a584:941f/64 scope link noprefixroute
valid_lft forever preferred_lft forever

reran the original 2 with the hotspot running

[smoke@rogtr ~]$ dmesg | grep -i wl
[ 8.539300] iwlwifi 0000:03:00.0: enabling device (0000 → 0002)
[ 8.590330] iwlwifi 0000:03:00.0: WRT: Overriding region id 0
[ 8.590336] iwlwifi 0000:03:00.0: WRT: Overriding region id 1
[ 8.590338] iwlwifi 0000:03:00.0: WRT: Overriding region id 2
[ 8.590340] iwlwifi 0000:03:00.0: WRT: Overriding region id 3
[ 8.590342] iwlwifi 0000:03:00.0: WRT: Overriding region id 4
[ 8.590343] iwlwifi 0000:03:00.0: WRT: Overriding region id 6
[ 8.590344] iwlwifi 0000:03:00.0: WRT: Overriding region id 8
[ 8.590346] iwlwifi 0000:03:00.0: WRT: Overriding region id 9
[ 8.590347] iwlwifi 0000:03:00.0: WRT: Overriding region id 10
[ 8.590348] iwlwifi 0000:03:00.0: WRT: Overriding region id 11
[ 8.590349] iwlwifi 0000:03:00.0: WRT: Overriding region id 15
[ 8.590351] iwlwifi 0000:03:00.0: WRT: Overriding region id 16
[ 8.590352] iwlwifi 0000:03:00.0: WRT: Overriding region id 18
[ 8.590353] iwlwifi 0000:03:00.0: WRT: Overriding region id 19
[ 8.590354] iwlwifi 0000:03:00.0: WRT: Overriding region id 20
[ 8.590355] iwlwifi 0000:03:00.0: WRT: Overriding region id 21
[ 8.590356] iwlwifi 0000:03:00.0: WRT: Overriding region id 28
[ 8.590573] iwlwifi 0000:03:00.0: loaded firmware version 46.4e1ceb39.0 9260-th-b0-jf-b0-46.ucode op_mode iwlmvm
[ 9.026672] iwlwifi 0000:03:00.0: Detected Intel(R) Wireless-AC 9260 160MHz, REV=0x324
[ 9.073742] iwlwifi 0000:03:00.0: base HW address: 18:56:80:6a:59:78
[ 9.141237] ieee80211 phy0: Selected rate control algorithm ‘iwl-mvm-rs’
[ 9.199292] iwlwifi 0000:03:00.0 wlp3s0: renamed from wlan0
[ 117.071995] IPv6: ADDRCONF(NETDEV_CHANGE): wlp3s0: link becomes ready

smoke@rogtr ~]$ inxi -Nxx
Network:
Device-1: Intel Wireless-AC 9260 driver: iwlwifi v: kernel bus-ID: 03:00.0
chip-ID: 8086:2526
Device-2: Intel I211 Gigabit Network vendor: ASUSTeK driver: igb
v: kernel port: 2000 bus-ID: 05:00.0 chip-ID: 8086:1539
Device-3: Aquantia AQC107 NBase-T/IEEE 802.3bz Ethernet [AQtion]
vendor: ASUSTeK driver: atlantic v: kernel port: N/A bus-ID: 09:00.0
chip-ID: 1d6a:07b1
Device-4: Intel Wireless-AC 9260 Bluetooth Adapter type: USB
driver: btusb bus-ID: 1-2:2 chip-ID: 8087:0025