From 72135ce531a3303e7efb23c8c24c41bc3607b37f Mon Sep 17 00:00:00 2001 From: Maxim Devaev Date: Fri, 6 Jun 2025 17:04:17 +0300 Subject: [PATCH] update --- docs/faq.md | 63 ++-------------------------------------------------- docs/wifi.md | 59 ++++++++++++++++++++++++++++++++++-------------- 2 files changed, 44 insertions(+), 78 deletions(-) diff --git a/docs/faq.md b/docs/faq.md index d19c52e1..919e5fb1 100644 --- a/docs/faq.md +++ b/docs/faq.md @@ -513,69 +513,10 @@ As a first step, we recommend carefully reading our documentation on [GitHub](ht ??? question "I can't connect to Wi-Fi at all!" + * If your device is unable to connect to the Wi-Fi network that you have set up, check the 2.4 GHz Wi-Fi channel used by your Wi-Fi access point. - If channels 12 to 14 are used (some countries have banned these channels) try to use a channel between 1 and 11. - -??? question "How do I connect to multiple Wi-Fi networks?" - There are two ways to do this. - - Recommended: - - You can stack wifi networks in `/etc/wpa_supplicant/wpa_supplicant-wlan0.conf` - - Example: - - ```c - update_config=1 - - network={ - ssid="SSID1" - psk=abcdef0123456789 - } - - network={ - ssid="SSID2" - psk=abcdef0123456789 - } - - network={ - ssid="SSID3" - psk=abcdef0123456789 - } - ``` - - Create your PSK using this command: `wpa_passphrase 'MyNetwork' 'P@assw0rd' >> /etc/wpa_supplicant/wpa_supplicant-wlan0.conf` - - The second way is to use NetworkManager which is an alternitive but not recommended - - ```console - # rw - # su - - # pacman -S networkmanager - # nmcli device wifi list - # nmcli device wifi connect SSID1 password PASSWORD # Is needed to make the initial wifi connection - # nmcli device wifi connect SSID2 password PASSWORD # Is needed to make the seconadry wifi connection - # nmcli connection up SSID1/SSID2 # You can switch from 1 wifi network to another - # nmcli connection show # This shows a list of the correct connections / green shows connected state, white shows disconnected state - # nmcli connection modify SSID1 connection.autoconnect-priority 1 # This will make the first SSID the main one if you are in range of both - # nmcli connection modify SSID2 connection.autoconnect-priority 2 # If this is disconnected, it will switch to the first and visa versa - ``` - - Here are some additional commands and caveats - - ```console - # nmcli device wifi list - ``` - - ??? note "if you type nmcli and get the following error" - "nmcli (1.44.0) and NetworkManager (Unknown) versions don't match. Restarting NetworkManager is advised. Error: NetworkManager is not running." - - ```console - # systemctl list-unit-files --all #look for networkmanager, if its disabled, enable it and start the service - # systemctl enable NetworkManager.service - # systemctl start NetworkManager.service - ``` + * If channels 12 to 14 are used (some countries have banned these channels) try to use a channel between 1 and 11. ??? question "LEDs/Switches do not work in ATX control" Double check your wiring. Make sure you placed the relays (G3VM-61A1) in the correct orientation. The relays for switches (Power, Reset) have a different orientation than the ones for LEDs. diff --git a/docs/wifi.md b/docs/wifi.md index 1d578f52..c7bf37df 100644 --- a/docs/wifi.md +++ b/docs/wifi.md @@ -1,7 +1,8 @@ # Setting up Wi-Fi !!! tip - There is nothing more reliable than wired Ethernet, so it's better to use it. Wi-Fi with the steel case (on PiKVM V3 and V4) results in poor performance. But who are we to stop you... :) + * There is nothing more reliable than wired Ethernet, so it's better to use it. Wi-Fi with the steel case (on PiKVM V3 and V4) results in poor performance. But who are we to stop you... :) + * Devices based on Raspberry Pi Zero 2 W does not support 5GHz Wi-Fi. The following describes how to setup a Wi-Fi connection. We recommend to do this while having a display and keyboard @@ -12,10 +13,8 @@ Alternatively you can connect to the PiKVM via SSH. The built-in Web Terminal (a This guide describes how to manually set up a Wi-Fi. An easier way is to use [On-boot config](on_boot_config.md). It is also mandatory for Zero 2 W board. -!!! note - Devices based on Raspberry Pi Zero 2 W does not support 5GHz Wi-Fi. - +----- ## Setting up Wi-Fi manually 1. Make filesystem writable using `rw` command. @@ -37,9 +36,9 @@ Alternatively you can connect to the PiKVM via SSH. The built-in Web Terminal (a 3. Set network ESSID and password: - ``` - # wpa_passphrase 'MyNetwork' 'P@assw0rd' > /etc/wpa_supplicant/wpa_supplicant-wlan0.conf - # chmod 640 /etc/wpa_supplicant/wpa_supplicant-wlan0.conf + ```console + [root@pikvm ~]# wpa_passphrase 'MyNetwork' 'P@assw0rd' > /etc/wpa_supplicant/wpa_supplicant-wlan0.conf + [root@pikvm ~]# chmod 640 /etc/wpa_supplicant/wpa_supplicant-wlan0.conf ``` !!! note "WPA2 and WPA3 support" @@ -56,13 +55,38 @@ Alternatively you can connect to the PiKVM via SSH. The built-in Web Terminal (a 5. Enable WPA-supplicant service: - ``` - systemctl enable wpa_supplicant@wlan0.service + + ```console + [root@pikvm ~]# systemctl enable wpa_supplicant@wlan0.service ``` 6. Make filesystem read-only again using `ro` command +----- +## Multiple Wi-Fi networks + +You can configure PiKVM to connect to one of several known Wi-Fi networks. +To do this, just simply add the configuration of these networks. +Pay attention to the symbol `>>`, it is used to append at the end of configuration, +while a single `>` will overwrite the entire configuration. + +1. Make the filesystem writeble with `rw` command. + +2. Add some new networks: + + ```console + [root@pikvm ~]# wpa_passphrase 'Wifi1' 'P@assw0rd' >> /etc/wpa_supplicant/wpa_supplicant-wlan0.conf + [root@pikvm ~]# wpa_passphrase 'Wifi2' 'P@assw0rd' >> /etc/wpa_supplicant/wpa_supplicant-wlan0.conf + [root@pikvm ~]# wpa_passphrase 'Wifi3' 'P@assw0rd' >> /etc/wpa_supplicant/wpa_supplicant-wlan0.conf + ``` + +3. Restart the service: `systemctl restart wpa_supplicant@wlan0.service`. + +4. Make the filesystem read-only again using `ro` command + + +----- ## Useful console commands * `iwconfig` - Manipulate the basic wireless parameters. @@ -71,20 +95,21 @@ Alternatively you can connect to the PiKVM via SSH. The built-in Web Terminal (a * `iwpriv` - Allow's you to manipulate the Wireless Extensions specific to a driver (private). ??? example "Some examples" + ```console + [root@pikvm ~]# iw dev wlan0 scan | egrep "signal:|SSID:" | sed -e "s/\tsignal: //" -e "s/\tSSID: //" | awk '{ORS = (NR % 2 == 0)? "\n" : " "; print}' | sort ``` - # iw dev wlan0 scan | egrep "signal:|SSID:" | sed -e "s/\tsignal: //" -e "s/\tSSID: //" | awk '{ORS = (NR % 2 == 0)? "\n" : " "; print}' | sort + ```console + [root@pikvm ~]# iwlist wlan0 scan | egrep "Cell|ESSID|Signal|Rates" ``` + ```console + [root@pikvm ~]# iwlist wlan0 scan ``` - # iwlist wlan0 scan | egrep "Cell|ESSID|Signal|Rates" - ``` - ``` - # iwlist wlan0 scan - ``` - ``` - # iw wlan0 info + ```console + [root@pikvm ~]# iw wlan0 info ``` +----- ## Additional resources * [Arch Linux Wiki for systemd-networkd](https://wiki.archlinux.org/title/systemd-networkd)