Hello, Am Di., 18. Apr. 2023 um 17:49 Uhr schrieb Bitterblue Smith <rtl8821cerfe2@xxxxxxxxx>: > 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
