Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

feat: radxa-os: add a Q&A for ap #610

Merged
merged 1 commit into from
Dec 20, 2024
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
13 changes: 12 additions & 1 deletion docs/common/radxa-os/_ap.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -75,6 +75,17 @@ sudo nmcli connection up AP

## 常见问题

### 无法开启 5G 热点
### 1. 无法开启 5G 热点

尝试指定 `Channel` 参数为 `<A (5 GHz)> 36`

### 2. 客户端能扫描到热点但是连接失败

这是因为 `NetworkManager` 的前端描述错误导致的,加密方式选择了 `WPA2` 但是其实实际开启的的是 `WPA3`,
又因为部分网卡不支持 `WPA3`,导致只能扫描到热点但是连接失败,可通过添加以下参数关闭 `WPA3` 能力。

```
sudo nmcli connection modify <CONNECTION NAME> wifi-sec.key-mgmt wpa-psk
sudo nmcli connection down <CONNECTION NAME> connection
sudo nmcli connection up <CONNECTION NAME> connection --ask
```
Original file line number Diff line number Diff line change
Expand Up @@ -75,6 +75,20 @@ sudo nmcli connection up AP

## Q&A

### Can't turn on 5G hotspot
### 1. Can't turn on 5G hotspot

Try specifying the `Channel` parameter as `<A (5 GHz)> 36`.

### 2. The client can scan the hotspot but connection fails.

This is because the front-end of `NetworkManager` is wrongly described,
and the encryption method selected is `WPA2`, but the actual encryption method is `WPA3`,
and some WIFI devices do not support `WPA3`.
Because some WIFI devices don't support `WPA3`, it can only scan the hotspot but fail to connect,
you can disable `WPA3` by adding the following parameter.

```
sudo nmcli connection modify <CONNECTION NAME> wifi-sec.key-mgmt wpa-psk
sudo nmcli connection down <CONNECTION NAME> connection
sudo nmcli connection up <CONNECTION NAME> connection --ask
```
Loading