Received-SPF: pass (google.com: domain of linux-wireless-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20;
MIME-Version: 1.0
References: <CALbLcfAXrHp4vsVGqU0nBdB_gFmKTKx0GcdrFJA7R_kodAy0Ew@mail.gmail.com>
 <bfe732f4-60dd-4d78-1259-5f9f6c11adbc@gmail.com> <CALbLcfB7cMctHC-Fv93z1WVCZkQ76uW2F_=P6rCW7ZSPXvmapw@mail.gmail.com>
 <2857f998-1b1a-e3c2-20fe-d03dadcf8f23@gmail.com>
In-Reply-To: <2857f998-1b1a-e3c2-20fe-d03dadcf8f23@gmail.com>
From:   Artem Makhutov <artem.makhutov@gmail.com>
Date:   Wed, 19 Apr 2023 19:21:10 +0200
Message-ID: <CALbLcfCsyGzhvrqjSz37+7cLvc3rc4Y_kgspZV=kiPNs4TBE4w@mail.gmail.com>
Subject: Re: RTL8188EU (LogiLink WL0151A) - Malformed packets
To:     Bitterblue Smith <rtl8821cerfe2@gmail.com>
Cc:     "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Content-Type: text/plain; charset="UTF-8"
Precedence: bulk

Hello,

Am Di., 18. Apr. 2023 um 17:49 Uhr schrieb Bitterblue Smith
<rtl8821cerfe2@gmail.com>:
> Can you also capture the wifi traffic using some device which is not
> handled by rtl8xxxu? With airodump-ng, wireshark, etc. Then you can
> compare the pkt_len with what the capture device sees.

This is not possible right now as I only have remote access to the device.

> It could also be useful to see what the v5.2.2.4 driver receives,
> both with 1428 and with 1430:

From the v5.2.2.4 I am getting:

ping -I wlan0 -s 1430 10.10.0.1
[ 1249.671282] rtl8188e_query_rx_desc_status: pkt_len: 1508
[ 1249.697409] rtl8188e_query_rx_desc_status: pkt_len: 456
[...]
[ 1250.210397] rtl8188e_query_rx_desc_status: pkt_len: 119
[ 1250.306412] rtl8188e_query_rx_desc_status: pkt_len: 456
[...]
[ 1250.660650] rtl8188e_query_rx_desc_status: pkt_len: 1508
[...]
[ 1251.438777] rtl8188e_query_rx_desc_status: pkt_len: 264
[ 1251.533917] rtl8188e_query_rx_desc_status: pkt_len: 456
[ 1251.636303] rtl8188e_query_rx_desc_status: pkt_len: 456
[ 1251.677177] rtl8188e_query_rx_desc_status: pkt_len: 1508

ping -I wlan0 -s 1428 10.10.0.1
[ 1335.845038] rtl8188e_query_rx_desc_status: pkt_len: 1506

> Also, can you show the hex dump from a good ping?

Yes, I will try to capture that, but it's not so easy. The logs file
is overwritten verry fast and it's hard to catch.

I have also tested the driver from https://github.com/aircrack-ng/rtl8188eus

The problem occurs here too, but much less frequently than in the
rtl8xxxu driver. The strange thing is that sometimes I have 99% of
broken packets with the rtl8xxxu driver, but sometimes only 1%...
With the aircrack-ng driver I had maybe about 2% of failures.

Thanks, Artem