Your message dated Tue, 30 Nov 2021 15:25:07 +0100
with message-id <[email protected]>
and subject line Re: Bug#969319: wifi cannot connect after combined suspend &
gateway reboot
has caused the Debian Bug report #969319,
regarding hidden SSID connectivity broken
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
969319: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=969319
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: network-manager
Version: 1.26.2-1
Severity: important
I'm on Debian Sid, with network manager configured to use iwd. I have
an Intel AX200 wifi card.
Normally the wifi of my laptop connects to my home gateway
automatically, but there's a issue where it cannot connect until
rebooted after a combined suspending of the laptop and rebooting of the
router.
My normal daily routine involves turning the gateway on first (no point
wasting electricity leaving it on over night), then getting out the
laptop and turning that on. There's no problem in this scenario. If at
any time during the day I reboot the gateway, it handles this fine (or
at least if it doesn't automatically reconnect it connects fine on
manually selecting the network from the list Gnome provides). A lot of
the time when I go off to do something else, I leave the lid open, so
no suspending, but sometimes I do close the lid and thus let the laptop
sleep, and similarly, no real issues with connecting when I get back on
it. I can select the 'turn off' wifi option and turn it back on, and it
reconnects fine.
However, something I've done instead for the past couple of nights is
to lock the user account, close the lid to let it sleep, and then turn
off the gateway. The problem I'm experiencing is that after turning the
gateway back on, and then (minutes later) returning to the laptop, it's
impossible to reconnect without rebooting. Selecting the network from
the list Gnome provides, the wifi connecting icon appears for a few
seconds, then just disappears.
Checking dmesg, this is what I'm seeing (MAC censored):
[223484.493130] wlan0: authenticate with «MAC»
[223484.496051] wlan0: send auth to «MAC» (try 1/3)
[223485.395342] iwlwifi 0000:3a:00.0: No beacon heard and the session
protection is over already...
[223485.395383] wlan0: Connection to AP «MAC» lost
[223485.759776] wlan0: send auth to «MAC» (try 2/3)
[223486.658815] iwlwifi 0000:3a:00.0: No beacon heard and the session
protection is over already...
[223486.658853] wlan0: Connection to AP «MAC» lost
[223486.751809] wlan0: send auth to «MAC» (try 3/3)
[223487.650547] iwlwifi 0000:3a:00.0: No beacon heard and the session
protection is over already...
[223487.650625] wlan0: Connection to AP «MAC» lost
[223487.710943] wlan0: authentication with «MAC» timed out
[223503.680212] wlan0: authenticate with «MAC»
[223503.685609] wlan0: send auth to «MAC» (try 1/3)
[223504.585038] iwlwifi 0000:3a:00.0: No beacon heard and the session
protection is over already...
[223504.585098] wlan0: Connection to AP «MAC» lost
[223504.735885] wlan0: send auth to «MAC» (try 2/3)
[223505.634822] iwlwifi 0000:3a:00.0: No beacon heard and the session
protection is over already...
[223505.634869] wlan0: Connection to AP «MAC» lost
[223505.759800] wlan0: send auth to «MAC» (try 3/3)
[223506.658534] iwlwifi 0000:3a:00.0: No beacon heard and the session
protection is over already...
[223506.658564] wlan0: Connection to AP «MAC» lost
[223506.718845] wlan0: authentication with «MAC» timed out
[223803.377295] wlan0: authenticate with «MAC»
[223803.382092] wlan0: send auth to «MAC» (try 1/3)
[223804.281508] iwlwifi 0000:3a:00.0: No beacon heard and the session
protection is over already...
[223804.281602] wlan0: Connection to AP «MAC» lost
[223804.736105] wlan0: send auth to «MAC» (try 2/3)
[223805.635147] iwlwifi 0000:3a:00.0: No beacon heard and the session
protection is over already...
[223805.635194] wlan0: Connection to AP «MAC» lost
[223805.728010] wlan0: send auth to «MAC» (try 3/3)
[223806.627041] iwlwifi 0000:3a:00.0: No beacon heard and the session
protection is over already...
[223806.627081] wlan0: Connection to AP «MAC» lost
[223806.719201] wlan0: authentication with «MAC» timed out
[223878.248338] wlan0: authenticate with «MAC»
[223878.255331] wlan0: send auth to «MAC» (try 1/3)
[223879.154749] iwlwifi 0000:3a:00.0: No beacon heard and the session
protection is over already...
[223879.154801] wlan0: Connection to AP «MAC» lost
[223879.776037] wlan0: send auth to «MAC» (try 2/3)
[223880.675073] iwlwifi 0000:3a:00.0: No beacon heard and the session
protection is over already...
[223880.675113] wlan0: Connection to AP «MAC» lost
[223880.735862] wlan0: send auth to «MAC» (try 3/3)
[223881.634760] iwlwifi 0000:3a:00.0: No beacon heard and the session
protection is over already...
[223881.634804] wlan0: Connection to AP «MAC» lost
[223881.727233] wlan0: authentication with «MAC» timed out
I tried turning wifi off and back on again (via the Gnome menu) and
manually selecting the network, which did not help, same failure.
I have macchanger installed, and tried switching to a new random MAC to
see if that helped (with the wifi off temporarily, obviously), but it
did not help.
I tried rebooting the gateway again, which also did not help.
I tried closing the lid for a few moments to recycle through a sleep
state, which did not help.
So I rebooted, as I did the day before when this happened, and it
connected just fine afterwards:
[ 24.666063] wlan0: authenticate with «MAC»
[ 24.673802] wlan0: send auth to «MAC» (try 1/3)
[ 24.713133] wlan0: authenticated
[ 24.715554] wlan0: associating with AP with corrupt probe response
[ 24.718102] wlan0: associate with «MAC» (try 1/3)
[ 24.727776] wlan0: RX AssocResp from «MAC» (capab=0x411 status=0
aid=1)
[ 24.737612] wlan0: associated
[ 24.741395] wlan0: deauthenticating from «MAC» by local choice
(Reason: 3=DEAUTH_LEAVING)
[ 24.765394] wlan0: authenticate with «MAC»
[ 24.772846] wlan0: send auth to «MAC» (try 1/3)
[ 25.890312] wlan0: send auth to «MAC» (try 2/3)
[ 25.956600] Bluetooth: RFCOMM TTY layer initialized
[ 25.956607] Bluetooth: RFCOMM socket layer initialized
[ 25.956611] Bluetooth: RFCOMM ver 1.11
[ 26.789358] iwlwifi 0000:3a:00.0: No beacon heard and the session
protection is over already...
[ 26.789370] wlan0: Connection to AP «MAC» lost
[ 26.918350] wlan0: send auth to «MAC» (try 3/3)
[ 27.109371] rfkill: input handler disabled
[ 27.817472] iwlwifi 0000:3a:00.0: No beacon heard and the session
protection is over already...
[ 27.817513] wlan0: Connection to AP «MAC» lost
[ 27.905980] wlan0: authentication with «MAC» timed out
[ 45.317899] rfkill: input handler enabled
[ 47.253502] rfkill: input handler disabled
[ 77.128722] wlan0: authenticate with «MAC»
[ 77.132498] wlan0: send auth to «MAC» (try 1/3)
[ 77.158436] wlan0: authenticated
[ 77.158503] wlan0: associating with AP with corrupt probe response
[ 77.162061] wlan0: associate with «MAC» (try 1/3)
[ 77.173743] wlan0: RX AssocResp from «MAC» (capab=0x411 status=0
aid=1)
[ 77.195750] wlan0: associated
[ 77.367677] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
--- End Message ---
--- Begin Message ---
network-manager 1.30.0 where this issue is likely tied to was released
some time ago (and included in latest stable Debian release), so I
assume this issue is now resolved.
Please shout if that's not the case,
- Jonas
--
* Jonas Smedegaard - idealist & Internet-arkitekt
* Tlf.: +45 40843136 Website: http://dr.jones.dk/
[x] quote me freely [ ] ask before reusing [ ] keep private
signature.asc
Description: signature
--- End Message ---
