正如标题所述，在使用 eduroam 时，我的互联网连接会在一段时间后断开（通常在流量很大时（例如 zoom 会议）几分钟后断开，流量较少时可能会保持一个小时）。笔记本电脑保持连接到 wifi，但无法访问任何网站，我也无法 ping 任何 DNS 服务器（尽管与 Netflix 等的现有连接有时仍可工作）。我在 Windows 上没有遇到这个问题。
发生这种情况时的 journalctl 输出是
Sep 02 22:40:19 carlos-linux wpa_supplicant[1062]: wlo1: SME: Trying to authenticate with f0:9e:63:05:60:71 (SSID='eduroam' freq=2412 MHz)
Sep 02 22:40:19 carlos-linux kernel: wlo1: disconnect from AP 34:6f:90:34:24:8e for new auth to f0:9e:63:05:60:71
Sep 02 22:40:19 carlos-linux kernel: wlo1: authenticate with f0:9e:63:05:60:71
Sep 02 22:40:19 carlos-linux NetworkManager[1239]: <info> [1599111619.1322] device (wlo1): supplicant interface state: completed -> authenticating
Sep 02 22:40:19 carlos-linux NetworkManager[1239]: <info> [1599111619.1323] device (p2p-dev-wlo1): supplicant management interface state: completed -> authenticating
Sep 02 22:40:19 carlos-linux kernel: wlo1: send auth to f0:9e:63:05:60:71 (try 1/3)
Sep 02 22:40:19 carlos-linux wpa_supplicant[1062]: wlo1: Trying to associate with f0:9e:63:05:60:71 (SSID='eduroam' freq=2412 MHz)
Sep 02 22:40:19 carlos-linux NetworkManager[1239]: <info> [1599111619.1582] device (wlo1): supplicant interface state: authenticating -> associating
Sep 02 22:40:19 carlos-linux NetworkManager[1239]: <info> [1599111619.1582] device (p2p-dev-wlo1): supplicant management interface state: authenticating -> associating
Sep 02 22:40:19 carlos-linux kernel: wlo1: authenticated
Sep 02 22:40:19 carlos-linux kernel: wlo1: associate with f0:9e:63:05:60:71 (try 1/3)
Sep 02 22:40:19 carlos-linux kernel: wlo1: RX ReassocResp from f0:9e:63:05:60:71 (capab=0x421 status=17 aid=0)
Sep 02 22:40:19 carlos-linux kernel: wlo1: f0:9e:63:05:60:71 denied association (code=17)
Sep 02 22:40:19 carlos-linux wpa_supplicant[1062]: wlo1: CTRL-EVENT-ASSOC-REJECT bssid=f0:9e:63:05:60:71 status_code=17
Sep 02 22:40:19 carlos-linux wpa_supplicant[1062]: wlo1: SME: Deauth request to the driver failed
Sep 02 22:40:19 carlos-linux NetworkManager[1239]: <info> [1599111619.2197] device (wlo1): supplicant interface state: associating -> disconnected
Sep 02 22:40:19 carlos-linux NetworkManager[1239]: <info> [1599111619.2198] device (p2p-dev-wlo1): supplicant management interface state: associating -> disconnected
Sep 02 22:40:19 carlos-linux NetworkManager[1239]: <info> [1599111619.3201] device (wlo1): supplicant interface state: disconnected -> scanning
Sep 02 22:40:19 carlos-linux NetworkManager[1239]: <info> [1599111619.3202] device (p2p-dev-wlo1): supplicant management interface state: disconnected -> scanning
Sep 02 22:40:19 carlos-linux wpa_supplicant[1062]: wlo1: SME: Trying to authenticate with 34:6f:90:34:24:8e (SSID='eduroam' freq=5240 MHz)
Sep 02 22:40:19 carlos-linux kernel: wlo1: authenticate with 34:6f:90:34:24:8e
Sep 02 22:40:19 carlos-linux kernel: wlo1: send auth to 34:6f:90:34:24:8e (try 1/3)
Sep 02 22:40:19 carlos-linux NetworkManager[1239]: <info> [1599111619.4885] device (wlo1): supplicant interface state: scanning -> authenticating
Sep 02 22:40:19 carlos-linux NetworkManager[1239]: <info> [1599111619.4886] device (p2p-dev-wlo1): supplicant management interface state: scanning -> authenticating
Sep 02 22:40:19 carlos-linux wpa_supplicant[1062]: wlo1: Trying to associate with 34:6f:90:34:24:8e (SSID='eduroam' freq=5240 MHz)
Sep 02 22:40:19 carlos-linux NetworkManager[1239]: <info> [1599111619.5025] device (wlo1): supplicant interface state: authenticating -> associating
Sep 02 22:40:19 carlos-linux NetworkManager[1239]: <info> [1599111619.5025] device (p2p-dev-wlo1): supplicant management interface state: authenticating -> associating
Sep 02 22:40:19 carlos-linux kernel: wlo1: authenticated
Sep 02 22:40:19 carlos-linux kernel: wlo1: associate with 34:6f:90:34:24:8e (try 1/3)
Sep 02 22:40:19 carlos-linux kernel: wlo1: RX AssocResp from 34:6f:90:34:24:8e (capab=0x101 status=30 aid=0)
Sep 02 22:40:19 carlos-linux kernel: wlo1: 34:6f:90:34:24:8e rejected association temporarily; comeback duration 1000 TU (1024 ms)
Sep 02 22:40:19 carlos-linux kernel: iwlwifi 0000:00:14.3: Unhandled alg: 0x707
Sep 02 22:40:19 carlos-linux kernel: iwlwifi 0000:00:14.3: Unhandled alg: 0x707
Sep 02 22:40:19 carlos-linux kernel: iwlwifi 0000:00:14.3: Unhandled alg: 0x707
Sep 02 22:40:19 carlos-linux kernel: iwlwifi 0000:00:14.3: Unhandled alg: 0x707
Sep 02 22:40:20 carlos-linux kernel: iwlwifi 0000:00:14.3: No beacon heard and the time event is over already...
Sep 02 22:40:20 carlos-linux kernel: wlo1: Connection to AP 34:6f:90:34:24:8e lost
Sep 02 22:40:20 carlos-linux kernel: wlo1: associate with 34:6f:90:34:24:8e (try 2/3)
Sep 02 22:40:20 carlos-linux kernel: wlo1: RX AssocResp from 34:6f:90:34:24:8e (capab=0x101 status=30 aid=0)
Sep 02 22:40:20 carlos-linux kernel: wlo1: 34:6f:90:34:24:8e rejected association temporarily; comeback duration 1000 TU (1024 ms)
Sep 02 22:40:20 carlos-linux kernel: iwlwifi 0000:00:14.3: Unhandled alg: 0x707
Sep 02 22:40:20 carlos-linux kernel: iwlwifi 0000:00:14.3: Unhandled alg: 0x707
Sep 02 22:40:21 carlos-linux kernel: iwlwifi 0000:00:14.3: No beacon heard and the time event is over already...
Sep 02 22:40:21 carlos-linux kernel: wlo1: Connection to AP 34:6f:90:34:24:8e lost
Sep 02 22:40:21 carlos-linux kernel: wlo1: associate with 34:6f:90:34:24:8e (try 3/3)
Sep 02 22:40:21 carlos-linux kernel: wlo1: RX AssocResp from 34:6f:90:34:24:8e (capab=0x1101 status=17 aid=0)
Sep 02 22:40:21 carlos-linux kernel: wlo1: 34:6f:90:34:24:8e denied association (code=17)
Sep 02 22:40:21 carlos-linux wpa_supplicant[1062]: wlo1: CTRL-EVENT-ASSOC-REJECT bssid=34:6f:90:34:24:8e status_code=17
Sep 02 22:40:21 carlos-linux wpa_supplicant[1062]: wlo1: SME: Deauth request to the driver failed
Sep 02 22:40:21 carlos-linux NetworkManager[1239]: <info> [1599111621.6374] device (wlo1): supplicant interface state: associating -> disconnected
Sep 02 22:40:21 carlos-linux NetworkManager[1239]: <info> [1599111621.6374] device (p2p-dev-wlo1): supplicant management interface state: associating -> disconnected
Sep 02 22:40:21 carlos-linux NetworkManager[1239]: <info> [1599111621.7377] device (wlo1): supplicant interface state: disconnected -> scanning
Sep 02 22:40:21 carlos-linux NetworkManager[1239]: <info> [1599111621.7378] device (p2p-dev-wlo1): supplicant management interface state: disconnected -> scanning
Sep 02 22:40:21 carlos-linux wpa_supplicant[1062]: wlo1: SME: Trying to authenticate with 34:6f:90:34:24:81 (SSID='eduroam' freq=2462 MHz)
Sep 02 22:40:21 carlos-linux NetworkManager[1239]: <info> [1599111621.8833] device (wlo1): supplicant interface state: scanning -> authenticating
Sep 02 22:40:21 carlos-linux kernel: wlo1: authenticate with 34:6f:90:34:24:81
Sep 02 22:40:21 carlos-linux kernel: wlo1: send auth to 34:6f:90:34:24:81 (try 1/3)
Sep 02 22:40:21 carlos-linux NetworkManager[1239]: <info> [1599111621.8834] device (p2p-dev-wlo1): supplicant management interface state: scanning -> authenticating
Sep 02 22:40:21 carlos-linux wpa_supplicant[1062]: wlo1: Trying to associate with 34:6f:90:34:24:81 (SSID='eduroam' freq=2462 MHz)
Sep 02 22:40:21 carlos-linux NetworkManager[1239]: <info> [1599111621.9074] device (wlo1): supplicant interface state: authenticating -> associating
Sep 02 22:40:21 carlos-linux kernel: wlo1: authenticated
这与描述的问题相同这里，但那里的修复对我不起作用。我猜是因为我的 Ubuntu 网络配置与他们的 Arch 配置不同，所以如果有人能告诉我在我的配置中要更改什么才能使其与 Arch 的（“默认”）配置相匹配，我也会很感激。
编辑：该问题是由切换 AP 引起的，因此修复 Gnome 配置中的网络 BSSID 可以解决断开连接的问题，但这可能不是最佳选择......
编辑2：看来我的 wifi 适配器即使Killer Wi-Fi 6 AX1650i 160MHz Wireless Network Adapter (201NGW)它是英特尔 AX201 也能被识别。我还在 dmesg 中发现了以下几行：
[ 4.382504] iwlwifi 0000:00:14.3: Direct firmware load for iwlwifi-Qu-c0-hr-b0-56.ucode failed with error -2
[ 4.387696] iwlwifi 0000:00:14.3: loaded firmware version 55.d9698065.0 Qu-c0-hr-b0-55.ucode op_mode iwlmvm
[ 4.387716] iwlwifi 0000:00:14.3: Direct firmware load for iwl-debug-yoyo.bin failed with error -2
这是否意味着设备正在加载错误的固件？
诊断：
- 当发生这种情况时
mtr会显示“没有到达主机的路线” pgrep -a dh给出两个条目：
995171 /sbin/dhclient -d -q -sf /usr/lib/NetworkManager/nm-dhcp-helper -pf /run/NetworkManager/dhclient-wlo1.pid -lf /var/lib/NetworkManager/dhclient-85e18157-cc78-4948-a5fb-300853e6bb8b-wlo1.lease -cf /var/lib/NetworkManager/dhclient-wlo1.conf wlo1
995228 /sbin/dhclient -d -q -6 -S -sf /usr/lib/NetworkManager/nm-dhcp-helper -pf /run/NetworkManager/dhclient6-wlo1.pid -lf /var/lib/NetworkManager/dhclient6-85e18157-cc78-4948-a5fb-300853e6bb8b-wlo1.lease -cf /var/lib/NetworkManager/dhclient6-wlo1.conf wlo1
答案1
我在网上找到了一个似乎有效的解决方案，至少对我来说是这样：
https://bbs.archlinux.org/viewtopic.php?id=230963&p=2
我跟着恩斯塔克利克斯的过程并删除了一些在 Ubuntu 中不可能实现的步骤。以下是对我有用的方法：
首先，修改文件/etc/NetworkManager/NetworkManager.conf并添加以下几行：
[main]
dhcp=dhclient
（另外，请确保您已经安装了 dhclient，我相信它是 Ubuntu 的默认设置）
然后检查文件/etc/resolv.conf，你应该将名称服务器设置为127.0.0.53，它似乎是默认的
然后执行以下命令：
sudo systemctl enable systemd-resolved.service
sudo systemctl disable systemd-networkd.service
现在重新启动，希望一切都能正常工作，尽管我还没有尝试过这个解决方案很长一段时间。
答案2
请原谅我的抱怨。在 ubuntu 上搜索并尝试了 hp elitebook 640 g9 的各种方法后，修复方法似乎是更新 BIOS。
（eduroam 不断出现丢失问题）