documentation updates

This commit is contained in:
morrownr 2021-11-03 12:29:15 -05:00
parent 1c8bdd7ef5
commit 79da24c9bd
3 changed files with 88 additions and 50 deletions

View File

@ -3,7 +3,7 @@
# Purpose: Allow easy access to specific driver options. # Purpose: Allow easy access to specific driver options.
# #
# Edit the following line to change, add or delete options: # Edit the following line to change, add or delete options:
options 88x2bu rtw_drv_log_level=0 rtw_led_ctrl=1 rtw_vht_enable=1 rtw_power_mgnt=1 rtw_beamform_cap=10 rtw_dfs_region_domain=0 rtw_switch_usb_mode=2 options 88x2bu rtw_drv_log_level=0 rtw_led_ctrl=1 rtw_vht_enable=1 rtw_power_mgnt=1 rtw_beamform_cap=0 rtw_dfs_region_domain=0 rtw_switch_usb_mode=2
# #
# After editing is complete, save this file (if using nano: Ctrl+X, Y, Enter) # After editing is complete, save this file (if using nano: Ctrl+X, Y, Enter)
# and reboot to activate the changes. # and reboot to activate the changes.
@ -62,11 +62,11 @@ options 88x2bu rtw_drv_log_level=0 rtw_led_ctrl=1 rtw_vht_enable=1 rtw_power_mgn
# #
# Beamforming options: ( rtw_beamform_cap ) # Beamforming options: ( rtw_beamform_cap )
# #
# 0 = Disable # 0 = Disable (default) (recommended for AP mode)
# 1 = SU Beamformer (recommended for AP mode) # 1 = SU Beamformer
# 2 = SU Beamformee # 2 = SU Beamformee
# 3 = SU Beamformer and SU Beamformee # 3 = SU Beamformer and SU Beamformee
# 10= SU Beamformee and MU Beamformee (default) (recommended for managed mode) # 10= SU Beamformee and MU Beamformee
# 11= SU Beamformer and SU Beamformee and MU Beamformee # 11= SU Beamformer and SU Beamformee and MU Beamformee
# #
# Note: MU Beamformer not supported. # Note: MU Beamformer not supported.
@ -91,10 +91,12 @@ options 88x2bu rtw_drv_log_level=0 rtw_led_ctrl=1 rtw_vht_enable=1 rtw_power_mgn
# USB options: ( rtw_switch_usb_mode ) # USB options: ( rtw_switch_usb_mode )
# #
# 0 = No switch # 0 = No switch
# 1 = Switch from usb 2.0 to usb 3.0 (recommended for managed mode) # 1 = Switch from usb 2.0 to usb 3.0
# 2 = Switch from usb 3.0 to usb 2.0 (default) (recommended for AP mode) # 2 = Switch from usb 3.0 to usb 2.0 (default)
# #
# Note: The 88x2bu driver needs to stay in USB2 mode for AP mode operations. # Note: This driver may need to stay in USB2 mode for AP mode operations
# on some platforms in order to avoid dropping offline. This issue has been
# observed on 32 bit Raspberry Pi OS.
# #
# #
# ----- # -----

View File

@ -1,4 +1,4 @@
2021-10-24 2021-11-03
## Bridged Wireless Access Point ## Bridged Wireless Access Point
@ -9,8 +9,8 @@ the WiFi signal is weak or otherwise does not meet expectations.
#### Single Band or Dual Band - Your Choice #### Single Band or Dual Band - Your Choice
This document outlines single band and dual band WiFi setups using a This document outlines single band and dual band WiFi setups using a Raspberry
Raspberry Pi 3B, 3B+ or 4B with an AC1200 or above USB 3 WiFi adapter for 5 GHz Pi 3B, 3B+ or 4B with an AC600 USB2 or AC1200 USB3 WiFi adapter for 5 GHz
band and either an additional external WiFi adapter or internal WiFi for 2.4 GHz band and either an additional external WiFi adapter or internal WiFi for 2.4 GHz
band. There is a lot of flexibility and capability available with this type of band. There is a lot of flexibility and capability available with this type of
setup. setup.
@ -19,9 +19,12 @@ setup.
This setup supports WPA3-SAE. It is disabled by default. This setup supports WPA3-SAE. It is disabled by default.
WPA3-SAE will not work with Realtek 88xx chipset based USB WiFi adapters. WPA3-SAE will not work with some Realtek 88xx drivers. Let's just say that this
issue is in progress.
WPA3-SAE will work with Mediatek 761x chipset based USB WiFI adapters. WPA3-SAE works with Mediatek 761x chipset based USB WiFI adapters and, as far as
I can tell, with all usb wifi adapters that use Linux in-kernel drivers and I
have tested many..
Note: This guide uses systemd-networkd for network management. If your Linux Note: This guide uses systemd-networkd for network management. If your Linux
distro uses Network Manager or Netplan, they must be disabled. Sections that distro uses Network Manager or Netplan, they must be disabled. Sections that
@ -54,9 +57,9 @@ Ethernet connection providing internet
Note: I use the case upside down. There are several little things that Note: I use the case upside down. There are several little things that
work better with the case upside down and no negatives that I can find. work better with the case upside down and no negatives that I can find.
Note: Very few Powered USB 3 Hubs will work well with Raspberry Pi Note: Very few Powered USB 3 Hubs will work well with Raspberry Pi hardware. The
hardware. The primary problem has to do with the backfeeding of primary problem has to do with the backfeeding of current into the Raspberry Pi.
current into the Raspberry Pi. One that seems to work well here is: One that seems to work well here is:
[Transcend USB 3.0 4-Port Hub TS-HUB3K](https://www.amazon.com/gp/product/B005D69QD8) [Transcend USB 3.0 4-Port Hub TS-HUB3K](https://www.amazon.com/gp/product/B005D69QD8)
@ -78,23 +81,49 @@ which makes this adapter a good choice for a Raspberry Pi based access point.
USB WiFi adapter driver installation, if required, should be performed and tested USB WiFi adapter driver installation, if required, should be performed and tested
prior to continuing. prior to continuing.
Note: For USB3 adapters based on the Realtek rtl8812au, rtl8814au, and rtl8812bu Note: For USB3 adapters based on the Realtek rtl8812au, rtl8812bu and rtl8814au
chipsets, the following module parameters may be needed for best performance chipsets, the following module parameters may be needed for best performance
when the adapter is set to support 5 GHz band: when the adapter is set to support 5 GHz band:
``` ```
rtw_vht_enable=2 rtw_switch_usb_mode=1 rtw_beamform_cap=1 rtw_vht_enable=2 rtw_switch_usb_mode=1
``` ```
Note: For USB2 adapters based on the Realtek rtl8811au chipset, the following
module parameters may be needed for best performance when the adapter is set to
support 5 GHz band:
```
rtw_vht_enable=2
```
Note: For USB3 adapters based on the Realtek rtl8812au, rtl8814au, and rtl8812bu Note: For USB3 adapters based on the Realtek rtl8812au, rtl8814au, and rtl8812bu
chipsets, the following module parameters may be needed for best performance chipsets, the following module parameters may be needed for best performance
when the adapter is set to support 2.4 GHz band: when the adapter is set to support 2.4 GHz band:
``` ```
rtw_vht_enable=1 rtw_switch_usb_mode=2 rtw_beamform_cap=0 rtw_vht_enable=1 rtw_switch_usb_mode=2
``` ```
Note: For USB3 adapters based on Mediatek mt7612u or my7612un chipsets, the
following module parameter may be needed for best performance: Note: For USB2 adapters based on the Realtek rtl8811au chipset, the following
module parameters may be needed for best performance when the adapter is set to
support 2.4 GHz band:
```
rtw_vht_enable=1
```
Note: For USB3 or USB2 adapters based on Mediatek mt7612u or my7610u chipsets,
the following module parameter may be needed for best performance:
``` ```
disable_usb_sg=1 disable_usb_sg=1
``` ```
Note: More information is available at the following site:
https://github.com/morrownr/7612u
Note: For this access point setup to support WPA3-SAE in a dual band setup, two Note: For this access point setup to support WPA3-SAE in a dual band setup, two
USB WiFi adapters with Mediatek or Atheros chipsets are required as the Realtek USB WiFi adapters with Mediatek or Atheros chipsets are required as the Realtek
and internal Raspberry Pi WiFi drivers do not support WPA3-SAE as of the date and internal Raspberry Pi WiFi drivers do not support WPA3-SAE as of the date
@ -251,7 +280,7 @@ ctrl_interface=/var/run/hostapd
ctrl_interface_group=0 ctrl_interface_group=0
ieee80211d=1 ieee80211d=1
# The below line is not needed as USB WiFi adapters do not support DFS channels # Support DFS channels
#ieee80211h=1 #ieee80211h=1
beacon_int=100 beacon_int=100
@ -299,8 +328,10 @@ wmm_enabled=1
# mt7612u - mt7610u # mt7612u - mt7610u
#ht_capab=[HT40+][HT40-][GF][SHORT-GI-20][SHORT-GI-40] #ht_capab=[HT40+][HT40-][GF][SHORT-GI-20][SHORT-GI-40]
# #
# rtl8812au - rtl8811au - rtl8812bu - rtl8811cu - rtl8814au # rtl8812au - rtl8814au - rtl8811au
ht_capab=[HT40+][HT40-][SHORT-GI-20][SHORT-GI-40][MAX-AMSDU-7935] #ht_capab=[HT40+][HT40-][SHORT-GI-20][SHORT-GI-40][MAX-AMSDU-7935]
# rtl8812bu
ht_capab=[LDPC][HT40+][HT40-][SHORT-GI-20][SHORT-GI-40][RX-STBC1][MAX-AMSDU-7935]
# #
# IEEE 802.11ac # IEEE 802.11ac
@ -311,9 +342,16 @@ ieee80211ac=1
# mt7612u # mt7612u
#vht_capab=[RXLDPC][SHORT-GI-80][TX-STBC-2BY1][RX-STBC-1][MAX-A-MPDU-LEN-EXP3][RX-ANTENNA-PATTERN][TX-ANTENNA-PATTERN] #vht_capab=[RXLDPC][SHORT-GI-80][TX-STBC-2BY1][RX-STBC-1][MAX-A-MPDU-LEN-EXP3][RX-ANTENNA-PATTERN][TX-ANTENNA-PATTERN]
# #
# rtl8812au - rtl8811au - rtl8812bu - rtl8811cu - rtl8814au # rtl8812au
vht_capab=[MAX-MPDU-11454][SHORT-GI-80][SU-BEAMFORMER][HTC-VHT] #vht_capab=[MAX-MPDU-11454][SHORT-GI-80][TX-STBC-2BY1][RX-STBC-1][SU-BEAMFORMER][SOUNDING-DIMENSION-2][HTC-VHT][MAX-A-MPDU-EXP7]
# Note: [TX-STBC-2BY1] causes problems # rtl8812bu
vht_capab=[MAX-MPDU-11454][RXLDPC][SHORT-GI-80][TX-STBC-2BY1][RX-STBC-1][HTC-VHT][MAX-A-MPDU-LEN-EXP7]
# rtl8814au
#vht_capab=[MAX-MPDU-11454][SHORT-GI-80][SU-BEAMFORMER][HTC-VHT]
# rtl8811au
#vht_capab=[MAX-MPDU-11454][SHORT-GI-80][RX-STBC-1][HTC-VHT][MAX-A-MPDU-LEN-EXP7]
#
# Note: [TX-STBC-2BY1] may cause problems
# #
# Required for 80 MHz width channel operation # Required for 80 MHz width channel operation
vht_oper_chwidth=1 vht_oper_chwidth=1
@ -383,8 +421,7 @@ File contents
``` ```
# /etc/hostapd/hostapd-2g.conf # /etc/hostapd/hostapd-2g.conf
# Documentation: https://w1.fi/cgit/hostap/plain/hostapd/hostapd.conf # Documentation: https://w1.fi/cgit/hostap/plain/hostapd/hostapd.conf
# 2021-10-24 # 2021-11-02
# SSID # SSID
ssid=myPI-2g ssid=myPI-2g
# PASSPHRASE # PASSPHRASE
@ -439,6 +476,11 @@ wmm_enabled=1
# Note: Only one ht_capab= line should be active. The content of these lines is # Note: Only one ht_capab= line should be active. The content of these lines is
# determined by the capabilities of your adapter. # determined by the capabilities of your adapter.
# #
# Need to add RasPi4B internal wifi information
#
# RasPi4B internal wifi
ht_capab=[HT40+][HT40-][SHORT-GI-20][SHORT-GI-40][DSSS_CCK-40]
#
# ar9271 # ar9271
#ht_capab=[HT40+][HT40-][SHORT-GI-20][SHORT-GI-40][RX-STBC1][DSSS_CCK-40] #ht_capab=[HT40+][HT40-][SHORT-GI-20][SHORT-GI-40][RX-STBC1][DSSS_CCK-40]
# #
@ -446,7 +488,7 @@ wmm_enabled=1
#ht_capab=[HT40+][HT40-][GF][SHORT-GI-20][SHORT-GI-40] #ht_capab=[HT40+][HT40-][GF][SHORT-GI-20][SHORT-GI-40]
# #
# rtl8812au - rtl8811au - rtl8812bu - rtl8811cu - rtl8814au # rtl8812au - rtl8811au - rtl8812bu - rtl8811cu - rtl8814au
ht_capab=[HT40+][HT40-][SHORT-GI-20][SHORT-GI-40][MAX-AMSDU-7935] #ht_capab=[HT40+][HT40-][SHORT-GI-20][SHORT-GI-40][MAX-AMSDU-7935]
# Event logger - as desired # Event logger - as desired
#logger_syslog=-1 #logger_syslog=-1
@ -559,11 +601,11 @@ sudo nano /etc/dhcpcd.conf
``` ```
Add the following line above the first `interface xxx` line, if any, for dual band setup Add the following line above the first `interface xxx` line, if any, for dual band setup
``` ```
denyinterfaces eth0 wlan0 wlan1 denyinterfaces eth0 <wlan0> <wlan1>
``` ```
Add the following line above the first `interface xxx` line, if any, for single band setup Add the following line above the first `interface xxx` line, if any, for single band setup
``` ```
denyinterfaces eth0 wlan0 denyinterfaces eth0 <wlan0>
``` ```
Go to the end of the file and add the following line Go to the end of the file and add the following line
``` ```
@ -639,7 +681,7 @@ End of installation.
----- -----
Notes: Notes: The following sections contain good to know information
----- -----

View File

@ -130,43 +130,37 @@ There is no need to disable Secure Mode to install this driver. If Secure Mode i
### Installation Steps ### Installation Steps
Step 1: Open a terminal (e.g. Ctrl+Alt+T) ##### Step 1: Open a terminal (e.g. Ctrl+Alt+T)
Step 2: Update the system package information (select the option for the OS you are using) ##### Step 2: Update the system package information (select the option for the OS you are using)
Option for Debian based distributions such as Ubuntu, Linux Mint, and Raspberry Pi OS Option for Debian based distributions such as Ubuntu, Linux Mint, and Raspberry Pi OS
``` `sudo apt update`
sudo apt update
```
Option for Arch based distributions such as Manjaro Option for Arch based distributions such as Manjaro
``` `sudo pacman -Syu`
sudo pacman -Syu
```
Option for Fedora based distributions Option for Fedora based distributions
``` `sudo dnf -y update`
sudo dnf -y update
```
Note: If you do not regularly maintain your system by installing updated packages, it is a good idea to not only update system package information but also to install the updated packages followed by a system reboot. The installation can then be continued with step 3. Note: If you do not regularly maintain your system by installing updated packages, it is a good idea to not only update system package information but also to install the updated packages followed by a system reboot. The installation can then be continued with step 3.
Step 3: Install the required packages (select the option for the OS you are using) ##### Step 3: Install the required packages (select the option for the OS you are using)
Option for Raspberry Pi OS Option for Raspberry Pi OS
``` ```
sudo apt install -y raspberrypi-kernel-headers bc build-essential dkms git sudo apt install -y raspberrypi-kernel-headers bc build-essential dkms git
``` ```
Option for Debian, or Linux Mint Debian Edition (LMDE) Option for Debian and Linux Mint Debian Edition (LMDE)
``` ```
sudo apt install -y linux-headers-$(uname -r) build-essential dkms git libelf-dev sudo apt install -y linux-headers-$(uname -r) build-essential dkms git libelf-dev
``` ```
Option for Ubuntu (all flavors) or Linux Mint Option for Ubuntu (all flavors) and Linux Mint
``` ```
sudo apt install -y dkms git build-essential sudo apt install -y dkms git build-essential
``` ```
@ -176,7 +170,7 @@ Step 3: Install the required packages (select the option for the OS you are usin
sudo dnf -y install git dkms kernel-devel kernel-debug-devel sudo dnf -y install git dkms kernel-devel kernel-debug-devel
``` ```
Options for Arch or Manjaro Options for Arch and Manjaro
if using pacman if using pacman