Wireless
Issues related to Intel® Wireless Adapters and technologies
5974 Discussions

Problem injecting unicast packets using pcap library.

sklee
Beginner
432 Views

I have an AX210 and latest iwlwifi driver on linux(kernel 5.10.1).

When i send unicast frame through monitor interface
inject frame = 00000a00040000001200c000000064e599cb1faef05b7b61cb7164e599cb1fae00000700
iwlwifi driver retransmit same packet about 80 times, and it take very long time to finish (100msec).

dmesg message
[ 86.257966] iwl_mvm_mac_tx
[ 86.261111] iwlwifi 0000:03:00.0: iwl_mvm_tx_skb_non_sta station Id 1, queue=1
[ 86.289646] iwlwifi 0000:03:00.0: iwl_txq_inc_wr_ptr Q:1 WR: 0x3
about 100msec later
[ 86.396785] iwl_mvm_rx_tx_cmd_single
[ 86.400808] iwlwifi 0000:03:00.0: iwl_txq_reclaim [Q 1] 2 -> 3 (3)
[ 86.420411] iwlwifi 0000:03:00.0: iwl_mvm_rx_tx_cmd_single TXQ 1 status LONG_LIMIT (0x00000083)

 

But when i send broadcast frame, iwlwifi work well.
inject frame = 00000a00040000001200c0000000fffffffffffff05b7b61cb7164e599cb1fae00000700

dmesg message
[15376.508494] iwl_mvm_mac_tx
[15376.511640] iwlwifi 0000:03:00.0: iwl_mvm_tx_skb_non_sta station Id 1, queue=1
[15376.540428] iwlwifi 0000:03:00.0: iwl_txq_inc_wr_ptr Q:1 WR: 0x7
about 6msec later
[15376.546741] iwl_mvm_rx_tx_cmd_single
[15376.551152] iwlwifi 0000:03:00.0: iwl_txq_reclaim [Q 1] 6 -> 7 (7)
[15376.573474] iwlwifi 0000:03:00.0: iwl_mvm_rx_tx_cmd_single TXQ 1 status SUCCESS (0x00000001)

 

0 Kudos
4 Replies
Alberto_Sykes
Employee
417 Views

sklee, Thank you for posting in the Intel® Communities Support.

 

In order for us to provide the most accurate assistance on this scenario, we just wanted to confirm a few details about your system:

What is the model of the motherboard?

If this is a laptop, what is the model of it?

What is the model of the Router?

Is this a new computer?

Was it working fine before?

When did the issue start?

Did you make any recent hardware/software changes?

The wireless card, did you purchased it separately or did it came installed on the computer?

 

Please follow the instructions below:

 

WiFi troubleshooting steps

 

Step 1: Check whether the kernel version customer uses supports this device:

The reference table of Wireless adapters and corresponding kernel versions is available by the link: https://wireless.wiki.kernel.org/en/users/drivers/iwlwifi

The latest FWs are available by the following link:​ ​https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/

If the kernel version corresponds to the Wireless adapter, proceed with step 2.

 

Step 2: Check whether the Wireless adapter is connected correctly:

Type the following command to the terminal: # lspci​ 

Verify that the Intel network controller ​is identified, as on a picture below. If not, then the system doesn't identify the Intel network adapter and you will need to make sure it's properly integrated. You may need to request help from the system manufacturer. If the wireless adapter is properly identified - proceed with the step 3.

Alberto_R_Intel_0-1617734991828.png

 

 

Step 3: Check whether this is an iwlwifi issue:

Type the following command to the terminal: # modinfo iwlwifi​ (example of the command output is on the picture below). If there is no output, then the module isn’t installed this is the distribution installation issue.

Alberto_R_Intel_1-1617735026489.png

 

 

Please type: # lsmod | grep iwlwifi​   

Alberto_R_Intel_2-1617735063442.png

 

 

If the result is empty, the driver hasn't been loaded. Most likely to be a distribution issue.

To verify, please type: # dmesg | grep iwlwifi​   

Alberto_R_Intel_3-1617735113279.png

 

If the result is empty, the driver wasn’t initialized and this is a distribution issue. If the result is populated as on the above picture, proceeed with the step 4.

 

Step 4: Check whether the suitable firmware is installed:

Please type: # dmesg | grep “no suitable firmware found!”​

Alberto_R_Intel_4-1617735149813.png

 

 

If the result is not empty, it means you don't have a suitable FW (api mentioned in the dmesg).

Please visit here​ h​ttps://wireless.wiki.kernel.org/en/users/drivers/iwlwifi for supported FW, or here​ ​https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/ for the latest versions.

If these steps didn't reveal the issue or didn't solve the problem, proceed with the Step 5: 

 

Step 5: Collect the debug data:

Please type: # dmesg | grep ASSERT​ 

If the output is empty, please follow this wiki: https://wireless.wiki.kernel.org/en/users/drivers/iwlwifi/debugging to extract dmesg and trace-cmd.

If the output has value, please collect from the wiki FW dump too.

 

Any questions, please let me know.

 

Regards,

Albert R.

 

Intel Customer Support Technician

 

 

sklee
Beginner
408 Views

Hi, Albert R.

What is the model of the motherboard?

 =>  Raspberry Pi Compute Module.

If this is a laptop, what is the model of it?

=>

What is the model of the Router?

=> 

Is this a new computer?

=> yes

Was it working fine before?

=>  There is problem with general wireless LAN function.

When did the issue start?

=> When i  was  testing packet injection.

Did you make any recent hardware/software changes?

=>

The wireless card, did you purchased it separately or did it came installed on the computer?

=> Purchase separately.

 

the device is recognized and operated as shown below.

# lsmod
Module Size Used by Not tainted
iwlmvm 454656 0
mac80211 913408 1 iwlmvm
libarc4 16384 1 mac80211
iwlwifi 290816 1 iwlmvm
cfg80211 778240 3 iwlmvm,mac80211,iwlwifi
rfkill 32768 1 cfg80211
ipv6 503808 24 [permanent]

 

#iwconfig
lo no wireless extensions.

eth0 no wireless extensions.

wlan0mon IEEE 802.11 Mode:Monitor Frequency:2.472 GHz Tx-Power=-2147483648 dBm
Retry short limit:7 RTS thr:off Fragment thr:off
Power Management:on

wlan1mon IEEE 802.11 Mode:Monitor Frequency:2.422 GHz Tx-Power=-2147483648 dBm
Retry short limit:7 RTS thr:off Fragment thr:off
Power Management:on

AX210 supports monitor mode and packet injection.

The main problem is that fw make too many retransmissions  (about 80) when injecting single unicast packet in monitor mode.

Best regards,

 

 

Alberto_Sykes
Employee
400 Views

Hi sklee, Thank you very much for providing that information.


We will do further research on this matter, as soon as I get any updates I will post all the details on this thread.


Regards,

Albert R.


Intel Customer Support Technician


Alberto_Sykes
Employee
357 Views

Hello sklee, I just received an update on this matter.


I sent you an email, please verify your inbox.


Regards,

Albert R.


Intel Customer Support Technician


Reply