From: Bitterblue Smith <rtl8821cerfe2@gmail.com>
To: Ioannis Barkas <jnyb.de@gmail.com>, linux-wireless@vger.kernel.org
Subject: Re: TL-WN823N Realtek WPA3 SSID connection problem #9
Date: Thu, 24 Nov 2022 23:53:41 +0200 [thread overview]
Message-ID: <f1775b71-97fc-8b23-6ae1-319aa26c414a@gmail.com> (raw)
In-Reply-To: <CADUzMVYz8zJ13cunSKbtKrArsiSCr2m5k7QuwsP0nvyuVLrK6Q@mail.gmail.com>
On 25/11/2022 21:40, Ioannis Barkas wrote:
> Hello,
>
> I have tested various USB devices and all worked except the TL-WN823N.
> This device has never worked and we have 2 of them.
>
> On Ubuntu boot I get:
> [ 1208.638541] usb 1-1: RTL8192EU rev B (SMIC) 2T2R, TX queues 3,
> WiFi=1, BT=0, GPS=0, HI PA=0
> [ 1208.638553] usb 1-1: RTL8192EU MAC: d4:6e:0e:**:**:**
> [ 1208.638560] usb 1-1: rtl8xxxu: Loading firmware rtlwifi/rtl8192eu_nic.bin
> [ 1208.641483] usb 1-1: Firmware revision 19.0 (signature 0x92e1)
> [ 1209.735452] usbcore: registered new interface driver rtl8xxxu
>
> When I attempt to connect at a 2,4GHz WPA3 SSID this is what I get:
> [ 1502.319954] wlxd46e0eeba0f4: authenticate with c6:27:28:**:**:**
> [ 1502.332105] wlxd46e0eeba0f4: send auth to c6:27:28:**:**:** (try 1/3)
> [ 1502.476159] wlxd46e0eeba0f4: authenticate with c6:27:28:**:**:**
> [ 1502.476181] wlxd46e0eeba0f4: send auth to c6:27:28:**:**:** (try 1/3)
> [ 1502.587356] wlxd46e0eeba0f4: authenticated
> [ 1502.589113] wlxd46e0eeba0f4: associate with c6:27:28:**:**:** (try 1/3)
> [ 1502.593773] wlxd46e0eeba0f4: RX AssocResp from c6:27:28:**:**:**
> (capab=0x1431 status=0 aid=16)
> [ 1502.595559] usb 1-1: rtl8xxxu_bss_info_changed: HT supported
> [ 1502.597222] wlxd46e0eeba0f4: associated
> [ 1502.743847] wlxd46e0eeba0f4: deauthenticating from
> c6:27:28:**:**:** by local choice (Reason: 1=UNSPECIFIED)
>
> To make things worse, I accidentally inserted it in a USB 1.1 port on
> my AMD test PC and it could not even connect to a combo 2,4GHz WPA2,3
> SSID:
> [ 1001.681485] wlxd46e0eeba0f4: authenticate with c6:27:28:**:**:**
> [ 1001.703190] wlxd46e0eeba0f4: send auth to c6:27:28:**:**:** (try 1/3)
> [ 1001.904265] wlxd46e0eeba0f4: send auth to c6:27:28:**:**:** (try 2/3)
> [ 1002.108231] wlxd46e0eeba0f4: send auth to c6:27:28:**:**:** (try 3/3)
> [ 1002.312262] wlxd46e0eeba0f4: authentication with c6:27:28:**:**:** timed out
> [ 1013.501401] wlxd46e0eeba0f4: authenticate with c6:27:28:**:**:**
> [ 1013.523483] wlxd46e0eeba0f4: send auth to c6:27:28:**:**:** (try 1/3)
> [ 1013.724276] wlxd46e0eeba0f4: send auth to c6:27:28:**:**:** (try 2/3)
> [ 1013.928271] wlxd46e0eeba0f4: send auth to c6:27:28:**:**:** (try 3/3)
> [ 1014.132282] wlxd46e0eeba0f4: authentication with c6:27:28:**:**:** timed out
> [ 1027.230375] wlxd46e0eeba0f4: authenticate with c6:27:28:**:**:**
> [ 1027.242103] wlxd46e0eeba0f4: send auth to c6:27:28:**:**:** (try 1/3)
> [ 1027.444258] wlxd46e0eeba0f4: send auth to c6:27:28:**:**:** (try 2/3)
> [ 1027.648271] wlxd46e0eeba0f4: send auth to c6:27:28:**:**:** (try 3/3)
> [ 1027.852237] wlxd46e0eeba0f4: authentication with c6:27:28:**:**:** timed out
>
> On USB 2.0 port the problem with WPA2,3 SSID was resolved. Is it
> possible to set a flag so that the driver will bail out if the device
> is on a USB 1.1 port? The truth is that the maximum speed it reached
> was way below the 12Mb of USB 1.1 so it should not have a problem but
> in practise it does...
I believe the authentication failure is not related to USB 1.1. I get
that even with USB 2.0. It's probably intermittent, the best kind of
failure. Because of this and other problems, the standard advice on
various internet forums is "blacklist rtl8xxxu, install
Mange/rtl8192eu-linux-driver". I will look into it someday soon (ish).
>
> This is the device:
> Device Descriptor:
> bLength 18
> bDescriptorType 1
> bcdUSB 2.10
> bDeviceClass 0
> bDeviceSubClass 0
> bDeviceProtocol 0
> bMaxPacketSize0 64
> idVendor 0x2357 TP-Link
> idProduct 0x0109 TL-WN823N v2/v3 [Realtek RTL8192EU]
> bcdDevice 2.00
> iManufacturer 1 Realtek
> iProduct 2 802.11n NIC
> iSerial 3 00**********
> bNumConfigurations 1
> Configuration Descriptor:
> bLength 9
> bDescriptorType 2
> wTotalLength 0x0035
> bNumInterfaces 1
> bConfigurationValue 1
> iConfiguration 0
> bmAttributes 0xe0
> Self Powered
> Remote Wakeup
> MaxPower 500mA
> Interface Descriptor:
> bLength 9
> bDescriptorType 4
> bInterfaceNumber 0
> bAlternateSetting 0
> bNumEndpoints 5
> bInterfaceClass 255 Vendor Specific Class
> bInterfaceSubClass 255 Vendor Specific Subclass
> bInterfaceProtocol 255 Vendor Specific Protocol
> iInterface 2 802.11n NIC
> Endpoint Descriptor:
> bLength 7
> bDescriptorType 5
> bEndpointAddress 0x84 EP 4 IN
> bmAttributes 2
> Transfer Type Bulk
> Synch Type None
> Usage Type Data
> wMaxPacketSize 0x0200 1x 512 bytes
> bInterval 0
> Endpoint Descriptor:
> bLength 7
> bDescriptorType 5
> bEndpointAddress 0x05 EP 5 OUT
> bmAttributes 2
> Transfer Type Bulk
> Synch Type None
> Usage Type Data
> wMaxPacketSize 0x0200 1x 512 bytes
> bInterval 0
> Endpoint Descriptor:
> bLength 7
> bDescriptorType 5
> bEndpointAddress 0x06 EP 6 OUT
> bmAttributes 2
> Transfer Type Bulk
> Synch Type None
> Usage Type Data
> wMaxPacketSize 0x0200 1x 512 bytes
> bInterval 0
> Endpoint Descriptor:
> bLength 7
> bDescriptorType 5
> bEndpointAddress 0x87 EP 7 IN
> bmAttributes 3
> Transfer Type Interrupt
> Synch Type None
> Usage Type Data
> wMaxPacketSize 0x0040 1x 64 bytes
> bInterval 3
> Endpoint Descriptor:
> bLength 7
> bDescriptorType 5
> bEndpointAddress 0x08 EP 8 OUT
> bmAttributes 2
> Transfer Type Bulk
> Synch Type None
> Usage Type Data
> wMaxPacketSize 0x0200 1x 512 bytes
> bInterval 0
> Binary Object Store Descriptor:
> bLength 5
> bDescriptorType 15
> wTotalLength 0x000c
> bNumDeviceCaps 1
> USB 2.0 Extension Device Capability:
> bLength 7
> bDescriptorType 16
> bDevCapabilityType 2
> bmAttributes 0x00000002
> HIRD Link Power Management (LPM) Supported
> Device Status: 0x0001
> Self Powered
next prev parent reply other threads:[~2022-11-24 21:53 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-25 19:40 TL-WN823N Realtek WPA3 SSID connection problem #9 Ioannis Barkas
2022-11-24 21:53 ` Bitterblue Smith [this message]
2023-03-16 14:18 ` Bitterblue Smith
2023-04-04 19:48 ` Ioannis Barkas
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=f1775b71-97fc-8b23-6ae1-319aa26c414a@gmail.com \
--to=rtl8821cerfe2@gmail.com \
--cc=jnyb.de@gmail.com \
--cc=linux-wireless@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.