various updates to documentation
This commit is contained in:
parent
ccb2b0aa4c
commit
2170e093ed
57
README.md
57
README.md
@ -480,7 +480,7 @@ sudo ./remove-driver-no-dkms.sh
|
|||||||
|
|
||||||
Note: These are general recommendations, some of which may not apply to your specific situation.
|
Note: These are general recommendations, some of which may not apply to your specific situation.
|
||||||
|
|
||||||
- Security: Set WPA2-AES. Do not set WPA2 mixed mode or WPA or TKIP.
|
- Security: Set WPA2-AES or WPA2/WPA3 mixed or WPA3. Do not set WPA2 mixed mode or WPA or TKIP.
|
||||||
|
|
||||||
- Channel width for 2.4 GHz: Set 20 MHz fixed width. Do not use 40 MHz or 20/40 automatic.
|
- Channel width for 2.4 GHz: Set 20 MHz fixed width. Do not use 40 MHz or 20/40 automatic.
|
||||||
|
|
||||||
@ -548,42 +548,32 @@ sudo nano /etc/wpa_supplicant/wpa_supplicant.conf
|
|||||||
|
|
||||||
Question: Is WPA3 supported?
|
Question: Is WPA3 supported?
|
||||||
|
|
||||||
Answer: WPA3-SAE support is in this driver according to Realtek, however, for it
|
Answer: WPA3-SAE support is in this driver according to Realtek and it
|
||||||
to work in client mode with some current Linux distros, you will need to
|
works well on some Linux distros but not all. Generally the reason for
|
||||||
download, compile and install the current development version of wpa_supplicant
|
WPA3 not working on Linux distros is that the distro has an old version
|
||||||
from the following site:
|
of wpa_supplicant or Network Manager. Your options are to upgrade to a
|
||||||
|
more modern distro (most distros released after mid 2022) or compile and
|
||||||
https://w1.fi/cgit/
|
install new versions of the wpa_supplicant and Network Manager utilities.
|
||||||
|
|
||||||
Note: There is a file in the `docs` folder called `Update_wpa_supplicant_v3a.md`
|
|
||||||
that may help with updating wpa_supplicant.
|
|
||||||
|
|
||||||
Note: Some distros appear to have versions of Network Manager that are not
|
|
||||||
compatible with this driver. If that is the case, you may need to STOP or KILL
|
|
||||||
Network Manager and connect using wpa_supplicant.
|
|
||||||
|
|
||||||
WPA3-SAE is working well in AP mode using hostapd with current versions of the
|
|
||||||
Raspberry Pi OS.
|
|
||||||
|
|
||||||
-----
|
-----
|
||||||
|
|
||||||
Question: I bought two rtl8812bu based adapters and am planning to use both in
|
Question: I bought two rtl8812bu based adapters and am planning to use
|
||||||
the same computer. How do I set that up?
|
both in the same computer. How do I set that up?
|
||||||
|
|
||||||
Answer: You can't without considerable technical skills. Realtek drivers do not
|
Answer: Realtek drivers do not support more than one adapter with the
|
||||||
support more than one adapter with the same chipset in the same computer. You
|
same chipset in the same computer. You can have multiple Realtek based
|
||||||
can have multiple Realtek based adapters in the same computer as long as the
|
adapters in the same computer as long as the adapters are based on
|
||||||
adapters are based on different chipsets.
|
different chipsets.
|
||||||
|
|
||||||
-----
|
-----
|
||||||
|
|
||||||
Question: Why do you recommend Mediatek based adapters when you maintain this
|
Question: Why do you recommend Mediatek based adapters when you maintain
|
||||||
repo for a Realtek driver?
|
this repo for a Realtek driver?
|
||||||
|
|
||||||
Answer: Many new and existing Linux users already have adapters based on Realtek
|
Answer: Many new and existing Linux users already have adapters based on
|
||||||
chipsets. This repo is for Linux users to support their existing adapters but my
|
Realtek chipsets. This repo is for Linux users to support their existing
|
||||||
STRONG recommendation is for Linux users to seek out USB WiFi solutions based on
|
adapters but my STRONG recommendation is for Linux users to seek out USB
|
||||||
Mediatek chipsets:
|
WiFi solutions based on Mediatek chipsets:
|
||||||
|
|
||||||
https://github.com/morrownr/USB-WiFi
|
https://github.com/morrownr/USB-WiFi
|
||||||
|
|
||||||
@ -644,8 +634,8 @@ to happen.
|
|||||||
|
|
||||||
Question: Are there any known problems with AP mode?
|
Question: Are there any known problems with AP mode?
|
||||||
|
|
||||||
Answer: Overall this driver does a good job with AP mode. During testing and
|
Answer: Overall this driver does a good job with AP mode. During testing
|
||||||
work prior to making this driver available, the team working on this
|
and work prior to making this driver available, the team working on this
|
||||||
driver noticed some problems in AP mode if used with a Raspberry Pi 4B.
|
driver noticed some problems in AP mode if used with a Raspberry Pi 4B.
|
||||||
We were unable to discover or fix the exact cause of the problem but
|
We were unable to discover or fix the exact cause of the problem but
|
||||||
the workaround is to keep the driver in USB2 mode. This workaround only
|
the workaround is to keep the driver in USB2 mode. This workaround only
|
||||||
@ -665,8 +655,9 @@ reports of success or failure are needed. If you have yet to buy an
|
|||||||
adapter to use with monitor mode, there are adapters available that are
|
adapter to use with monitor mode, there are adapters available that are
|
||||||
known to work very well with monitor mode. My recommendation for those
|
known to work very well with monitor mode. My recommendation for those
|
||||||
looking to buy an adapter for monitor mode is to buy adapters based on
|
looking to buy an adapter for monitor mode is to buy adapters based on
|
||||||
the following chipsets: mt7612u, mt7610u, rtl8812au and rtl8811au. My
|
the following chipsets: mt7921au, mt7612u, mt7610u, rtl8812au and
|
||||||
specific recommendations for adapters in order of preference are:
|
rtl8811au. My specific recommendations for adapters in order of
|
||||||
|
preference are:
|
||||||
|
|
||||||
ALFA AWUS036ACHM - long range - in-kernel driver
|
ALFA AWUS036ACHM - long range - in-kernel driver
|
||||||
|
|
||||||
|
File diff suppressed because it is too large
Load Diff
File diff suppressed because it is too large
Load Diff
@ -15,8 +15,6 @@ DRV_VERSION="5.13.1"
|
|||||||
DRV_DIR="$(pwd)"
|
DRV_DIR="$(pwd)"
|
||||||
KRNL_VERSION="$(uname -r)"
|
KRNL_VERSION="$(uname -r)"
|
||||||
|
|
||||||
clear
|
|
||||||
|
|
||||||
# support for NoPrompt allows non-interactive use of this script
|
# support for NoPrompt allows non-interactive use of this script
|
||||||
NO_PROMPT=0
|
NO_PROMPT=0
|
||||||
|
|
||||||
|
@ -15,7 +15,6 @@ DRV_VERSION="5.13.1"
|
|||||||
DRV_DIR="$(pwd)"
|
DRV_DIR="$(pwd)"
|
||||||
KRNL_VERSION="$(uname -r)"
|
KRNL_VERSION="$(uname -r)"
|
||||||
|
|
||||||
clear
|
|
||||||
echo "Running ${SCRIPT_NAME} version ${SCRIPT_VERSION}"
|
echo "Running ${SCRIPT_NAME} version ${SCRIPT_VERSION}"
|
||||||
|
|
||||||
# support for NoPrompt allows non-interactive use of this script
|
# support for NoPrompt allows non-interactive use of this script
|
||||||
|
Loading…
x
Reference in New Issue
Block a user