TP-Link TL-WN8200ND v3 #41
Comments
|
If you plug it in and scan with iw, is it the same? I mean, without using hcxdumptool first. |
|
Yes iw first, hcxdmptool second orhcxdumtool first and iw second, both results in the same problem. First I thought the problem is related to this: |
|
That patch will only affect the RTL8188EU. If the LED blinks, the chip thinks it's transmitting something. I wonder if this device needs different initialisation tables because it's „high power”. Can you compile this driver: https://github.com/Mange/rtl8192eu-linux-driver/ diff --git a/Makefile b/Makefile
index 8ecdb72..9548b64 100644
--- a/Makefile
+++ b/Makefile
@@ -92,10 +92,10 @@ CONFIG_ICMP_VOQ = n
CONFIG_IP_R_MONITOR = n #arp VOQ and high rate
########################## Debug ###########################
# Say "y" here to have the driver output debugging messages. Not intended for normal use.
-CONFIG_RTW_DEBUG = n
+CONFIG_RTW_DEBUG = y
# Default log level is 2, which only displays errors.
# Available levels = none(0), always(1), error(2), warning(3), info(4), debug(5), max(6)
-CONFIG_RTW_LOG_LEVEL = 2
+CONFIG_RTW_LOG_LEVEL = 4
######################## Wake On Lan ##########################
CONFIG_WOWLAN = n
#bit2: deauth, bit1: unicast, bit0: magic pkt.And show what it prints? Let's say everything up to „RTW: rtw_hal_read_chip_info in 317 ms”. |
|
The good old hal driver. |
|
Here we go debug level 4: |
|
The idea to debug the (working) hal driver is great. |
|
It prints useful information. rtl8xxxu is a bit lacking in that area. This device definitely needs different initialisation tables: My cheap, small dongle from Aliexpress: rtl8xxxu may already have all the code it needs for this device, but it's not enabled. You could try this simple patch: diff --git a/rtl8xxxu_8192e.c b/rtl8xxxu_8192e.c
index 82c1365..0d5802f 100644
--- a/rtl8xxxu_8192e.c
+++ b/rtl8xxxu_8192e.c
@@ -32,6 +32,8 @@
#include "rtl8xxxu.h"
#include "rtl8xxxu_regs.h"
+#define EXT_PA_8192EU
+
static const struct rtl8xxxu_reg8val rtl8192e_mac_init_table[] = {
{0x011, 0xeb}, {0x012, 0x07}, {0x014, 0x75}, {0x303, 0xa7},
{0x428, 0x0a}, {0x429, 0x10}, {0x430, 0x00}, {0x431, 0x00},
@@ -521,6 +523,10 @@ static int rtl8192eu_identify_chip(struct rtl8xxxu_priv *priv)
if (!priv->ep_tx_count)
ret = rtl8xxxu_config_endpoints_no_sie(priv);
+#ifdef EXT_PA_8192EU
+ priv->hi_pa = 1;
+#endif
+
out:
return ret;
}Unfortunately, this patch will break the „normal power” RTL8192EU devices. |
|
Working like a charm - good starting point. |
|
I've got a few of those rtl8192eu adapters ⭐ but lack of time atm |
|
Good price-performance ratio. |
|
All devices collected in rtl8xxxu is cheap, portable sized chips, affordable one.. TL-WN722n v1 was the well-known ath9k_htc. Downgrade |
|
And the TP-Link TL-WN722N (v2) is impressive, too: out of scope: I decided to dive into the world of QpenWRT (on Raspberry Pi Zero). |
|
So, I've run it down. The adapters must be set enabled in web gui btw, that was the block. I just finished flashing and run down now, great results 👍 So, I put the 1 chip in AP mode and number 2 chip in monitor, in gui. Fetching PMKIDs like a pro |
That's great. I will prepare a better patch „soon”. Wanna buy me a present? 😁 https://www.amazon.de/hz/wishlist/ls/1OCIJV31AAT9O/ref=nav_wishlist_lists_1 |
|
|
|
@kimocoder What's that? I guess the picture didn't upload. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I started to add support of TP-Link TL-WN8200ND V3
https://www.tp-link.com/en/home-networking/high-gain-adapter/tl-wn8200nd/
added device to rtl8xxxu_core.c
$ sudo dmesg
So far so good, everything is looking fine and hcxdumptool is able to set monitor mode and channels:
Up to here, everything is still fine.
We can set monitor mode and we can set a channel.
Unfortunately the device doesn't receive packets.
Neither in monitor mode, nor by iw scan
The green LED flashes during scan, but that's all.
I'm sure I'm missing something, but I don't know what.
Any ideas to point me to the right direction?
The text was updated successfully, but these errors were encountered: