我家里有多个计算设备（2 台 Ubuntu 笔记本电脑、2 台 Windows PC、智能电视、平板电脑、手机等）。
我只在一台 Ubuntu 设备上遇到问题（其他设备都没有问题，其他 Ubuntu 设备是 20.04），我定期取消身份验证，断开 WiFi 连接。它似乎在断开连接时尝试重新验证不同的 MAC 地址，但唯一的区别是最后一个位置（在 2b、2c 和 2d 之间切换）。我的理论是，我的 wifi 路由器使用 2.4G 和 5G SSID 自动提供连接，这就是不同 MAC 地址的来源，但我不明白为什么只有这台笔记本电脑收到“PREV_AUTH_NOT_VALID”。
注意：这台笔记本电脑几个月前更新至 22.04，从那时起就出现了这种现象。
笔记本电脑硬件：第五代联想 Thinkpad X1 Carbon
Ubuntu 版本：Ubuntu 22.04.1 LTS
输出请参阅lspci-knn| grep Net-A3
04:00.0 网络控制器 [0280]: Intel 公司无线 8265 / 8275 [8086:24fd] (rev 88)
子系统：英特尔公司无线 8265 / 8275 [8086:0130]
正在使用的内核驱动程序：iwlwifi
内核模块：iwlwifi
dmesg 日志：
[ 1870.651427] wlp4s0: send auth to xx:xx:xx:xx:xx:2b (try 1/3)
[ 1870.659866] wlp4s0: authenticated
[ 1870.663374] wlp4s0: associate with xx:xx:xx:xx:xx:2b (try 1/3)
[ 1870.669000] wlp4s0: RX ReassocResp from xx:xx:xx:xx:xx:2b (capab=0x1411 status=0 aid=2)
[ 1870.676917] wlp4s0: associated
[ 1870.748498] wlp4s0: Limiting TX power to 30 (30 - 0) dBm as advertised by xx:xx:xx:xx:xx:2b
[ 1904.099981] wlp4s0: disconnect from AP xx:xx:xx:xx:xx:2b for new auth to xx:xx:xx:xx:xx:2d
[ 1904.165004] wlp4s0: authenticate with xx:xx:xx:xx:xx:2d
[ 1904.175741] wlp4s0: send auth to xx:xx:xx:xx:xx:2d (try 1/3)
[ 1904.183957] wlp4s0: authenticated
[ 1904.186853] wlp4s0: associate with xx:xx:xx:xx:xx:2d (try 1/3)
[ 1904.190067] wlp4s0: RX ReassocResp from xx:xx:xx:xx:xx:2d (capab=0x1511 status=0 aid=1)
[ 1904.193381] wlp4s0: associated
[ 1904.230410] wlp4s0: Limiting TX power to 27 (30 - 3) dBm as advertised by xx:xx:xx:xx:xx:2d
[ 1907.494012] wlp4s0: deauthenticated from xx:xx:xx:xx:xx:2d (Reason: 2=PREV_AUTH_NOT_VALID)
Mon Jan 9 09:01:34 2023] wlp4s0: authenticate with xx:xx:xx:xx:xx:2c
[Mon Jan 9 09:01:34 2023] wlp4s0: send auth to xx:xx:xx:xx:xx:2c (try 1/3)
[Mon Jan 9 09:01:34 2023] wlp4s0: authenticated
[Mon Jan 9 09:01:34 2023] wlp4s0: associate with xx:xx:xx:xx:xx:2c (try 1/3)
[Mon Jan 9 09:01:34 2023] wlp4s0: RX AssocResp from xx:xx:xx:xx:xx:2c (capab=0x1511 status=0 aid=8)
[Mon Jan 9 09:01:34 2023] wlp4s0: associated
[Mon Jan 9 09:01:34 2023] IPv6: ADDRCONF(NETDEV_CHANGE): wlp4s0: link becomes ready
[Mon Jan 9 09:01:34 2023] wlp4s0: Limiting TX power to 27 (30 - 3) dBm as advertised by xx:xx:xx:xx:xx:2c
[Mon Jan 9 09:12:07 2023] wlp4s0: deauthenticating from xx:xx:xx:xx:xx:2c by local choice (Reason: 3=DEAUTH_LEAVING)
[Mon Jan 9 09:56:56 2023] wlp4s0: authenticate with xx:xx:xx:xx:xx:2c
[Mon Jan 9 09:56:56 2023] wlp4s0: send auth to xx:xx:xx:xx:xx:2c (try 1/3)
[Mon Jan 9 09:56:56 2023] wlp4s0: authenticated
[Mon Jan 9 09:56:56 2023] wlp4s0: associate with xx:xx:xx:xx:xx:2c (try 1/3)
[Mon Jan 9 09:56:56 2023] wlp4s0: RX AssocResp from xx:xx:xx:xx:xx:2c (capab=0x1511 status=0 aid=6)
[Mon Jan 9 09:56:56 2023] wlp4s0: associated
[Mon Jan 9 09:56:56 2023] IPv6: ADDRCONF(NETDEV_CHANGE): wlp4s0: link becomes ready
[Mon Jan 9 09:56:56 2023] wlp4s0: Limiting TX power to 27 (30 - 3) dBm as advertised by xx:xx:xx:xx:xx:2c
[Tue Jan 10 02:16:41 2023] wlp4s0: deauthenticated from xx:xx:xx:xx:xx:2c (Reason: 7=CLASS3_FRAME_FROM_NONASSOC_STA)
[Tue Jan 10 02:16:41 2023] wlp4s0: authenticate with xx:xx:xx:xx:xx:2c
[Tue Jan 10 02:16:41 2023] wlp4s0: send auth to xx:xx:xx:xx:xx:2c (try 1/3)
[Tue Jan 10 02:16:41 2023] wlp4s0: authenticated
[Tue Jan 10 02:16:41 2023] wlp4s0: associate with xx:xx:xx:xx:xx:2c (try 1/3)
[Tue Jan 10 02:16:41 2023] wlp4s0: RX AssocResp from xx:xx:xx:xx:xx:2c (capab=0x1511 status=0 aid=3)
[Tue Jan 10 02:16:41 2023] wlp4s0: associated
[Tue Jan 10 02:16:41 2023] wlp4s0: Limiting TX power to 27 (30 - 3) dBm as advertised by xx:xx:xx:xx:xx:2c
[Wed Jan 11 13:02:35 2023] wlp4s0: disconnect from AP xx:xx:xx:xx:xx:2c for new auth to xx:xx:xx:xx:xx:2d
[Wed Jan 11 13:02:35 2023] wlp4s0: authenticate with xx:xx:xx:xx:xx:2d
[Wed Jan 11 13:02:35 2023] wlp4s0: send auth to xx:xx:xx:xx:xx:2d (try 1/3)
[Wed Jan 11 13:02:35 2023] wlp4s0: authenticated
[Wed Jan 11 13:02:35 2023] wlp4s0: associate with xx:xx:xx:xx:xx:2d (try 1/3)
[Wed Jan 11 13:02:35 2023] wlp4s0: RX ReassocResp from xx:xx:xx:xx:xx:2d (capab=0x1511 status=0 aid=1)
[Wed Jan 11 13:02:35 2023] wlp4s0: associated
[Wed Jan 11 13:02:35 2023] wlp4s0: Limiting TX power to 27 (30 - 3) dBm as advertised by xx:xx:xx:xx:xx:2d
[Wed Jan 11 13:02:38 2023] wlp4s0: deauthenticated from xx:xx:xx:xx:xx:2d (Reason: 2=PREV_AUTH_NOT_VALID)
[Wed Jan 11 13:03:23 2023] wlp4s0: authenticate with xx:xx:xx:xx:xx:2c
[Wed Jan 11 13:03:23 2023] wlp4s0: send auth to xx:xx:xx:xx:xx:2c (try 1/3)
[Wed Jan 11 13:03:23 2023] wlp4s0: authenticated
[Wed Jan 11 13:03:23 2023] wlp4s0: associate with xx:xx:xx:xx:xx:2c (try 1/3)
[Wed Jan 11 13:03:23 2023] wlp4s0: RX AssocResp from xx:xx:xx:xx:xx:2c (capab=0x1511 status=0 aid=3)
[Wed Jan 11 13:03:23 2023] wlp4s0: associated
[Wed Jan 11 13:03:23 2023] wlp4s0: Limiting TX power to 27 (30 - 3) dBm as advertised by xx:xx:xx:xx:xx:2c
[Wed Jan 11 13:03:23 2023] IPv6: ADDRCONF(NETDEV_CHANGE): wlp4s0: link becomes ready
[Wed Jan 11 13:42:44 2023] wlp4s0: disconnect from AP xx:xx:xx:xx:xx:2c for new auth to xx:xx:xx:xx:xx:2d
[Wed Jan 11 13:42:45 2023] wlp4s0: authenticate with xx:xx:xx:xx:xx:2d
[Wed Jan 11 13:42:45 2023] wlp4s0: send auth to xx:xx:xx:xx:xx:2d (try 1/3)
[Wed Jan 11 13:42:45 2023] wlp4s0: authenticated
[Wed Jan 11 13:42:45 2023] wlp4s0: associate with xx:xx:xx:xx:xx:2d (try 1/3)
[Wed Jan 11 13:42:45 2023] wlp4s0: RX ReassocResp from xx:xx:xx:xx:xx:2d (capab=0x1511 status=0 aid=1)
[Wed Jan 11 13:42:45 2023] wlp4s0: associated
[Wed Jan 11 13:42:45 2023] wlp4s0: Limiting TX power to 27 (30 - 3) dBm as advertised by xx:xx:xx:xx:xx:2d
[Wed Jan 11 13:42:48 2023] wlp4s0: deauthenticated from xx:xx:xx:xx:xx:2d (Reason: 2=PREV_AUTH_NOT_VALID)
[Thu Jan 12 10:38:27 2023] wlp4s0: authenticate with xx:xx:xx:xx:xx:2c
[Thu Jan 12 10:38:27 2023] wlp4s0: send auth to xx:xx:xx:xx:xx:2c (try 1/3)
[Thu Jan 12 10:38:27 2023] wlp4s0: authenticated
[Thu Jan 12 10:38:27 2023] wlp4s0: associate with xx:xx:xx:xx:xx:2c (try 1/3)
[Thu Jan 12 10:38:27 2023] wlp4s0: RX AssocResp from xx:xx:xx:xx:xx:2c (capab=0x1511 status=0 aid=6)
[Thu Jan 12 10:38:27 2023] wlp4s0: associated
[Thu Jan 12 10:38:28 2023] IPv6: ADDRCONF(NETDEV_CHANGE): wlp4s0: link becomes ready
[Thu Jan 12 10:38:28 2023] wlp4s0: Limiting TX power to 27 (30 - 3) dBm as advertised by xx:xx:xx:xx:xx:2c
[Thu Jan 12 13:12:01 2023] wlp4s0: disconnect from AP xx:xx:xx:xx:xx:2c for new auth to xx:xx:xx:xx:xx:2d
[Thu Jan 12 13:12:01 2023] wlp4s0: authenticate with xx:xx:xx:xx:xx:2d
[Thu Jan 12 13:12:01 2023] wlp4s0: send auth to xx:xx:xx:xx:xx:2d (try 1/3)
[Thu Jan 12 13:12:01 2023] wlp4s0: authenticated
[Thu Jan 12 13:12:01 2023] wlp4s0: associate with xx:xx:xx:xx:xx:2d (try 1/3)
[Thu Jan 12 13:12:01 2023] wlp4s0: RX ReassocResp from xx:xx:xx:xx:xx:2d (capab=0x1511 status=0 aid=1)
[Thu Jan 12 13:12:01 2023] wlp4s0: associated
[Thu Jan 12 13:12:01 2023] wlp4s0: Limiting TX power to 27 (30 - 3) dBm as advertised by xx:xx:xx:xx:xx:2d
[Thu Jan 12 13:12:05 2023] wlp4s0: deauthenticated from xx:xx:xx:xx:xx:2d (Reason: 2=PREV_AUTH_NOT_VALID)```
答案1
我的理论是，我的 wifi 路由器同时使用 2.4G 和 5G SSID 自动提供连接，这就是不同的 MAC 地址的来源
我认为您说得很对。当您拥有同一路由器的 2.4 gHz 段和 5 gHz 段时，这种情况很常见。您的无线网络可能正在漫游，寻找更好的连接。如果是这种情况，我建议您重命名接入点；例如 myrouter2.4 和 myrouter5。
完成这些更改后，重新启动路由器。
如果您无法访问路由器的管理页面，请通过 MAC 地址将您的无线设备绑定到 5 gHz 段，如下所示：19.10 Ubuntu 自动连接到信号较弱的 Wi-Fi