Skip to content
Oleksij Rempel edited this page Aug 22, 2014 · 1 revision

He we collect testcases for this driver or firmware.

TDLS

From Csaba Kiralys mail:

Here it comes. I try to give a detailed description, although I suppose you don't need most of it I have used two laptops, two TP-Link TL-WN722N USB devices, and a Linksys WAP54g AP.

0) stop conflicting services, clean up files

service network-manager stop killall wpa_supplicant killall dhclient rm -rf /run/wpa_supplicant

1) on both nodes, start wpa_supplicant and connect to the same AP.

Conf files attached

hostap/wpa_supplicant/wpa_supplicant -D nl80211 -i wlan2 -c wpa_supplicant_wap54g_WPA2.conf

2) on each node, configure IP addresses (or start dhclient)

ifconfig wlan2 $IP1 ifconfig wlan2 $IP2

3) start pinging the other node

ping $IP2

4) start pinging the AP

ping $IPAP

5) get MAC of node2's Atheros card

get it on node2, or directly on node1 from the arp cache

arp -n

6) on node1, start wpa_cli

hostap/wpa_supplicant/wpa_cli -i wlan2

7) on node1, in wpa_cli, start the TDLS setup

tdls_setup

8) verify that TDLS works

- ping time will reduce (in my case it went from 1.6 ms to 1 ms)

- ping time to the AP should remain the same

- node2's MAC will appear in ath9k_htc debugfs

ls /sys/kernel/debug/ieee80211/phy1/netdev:wlan2/stations

- look inside the debugfs folder for more details

9) stress test

ping -f $IP2

10) disable encryption in the AP and repeat the same with the "open" config file

pitfalls and notes

  • APs could interfere in various ways with the test. Some models could set the TDLS prohibit flag. Others (like my Huawei E587) could work at the beginning but deauthenticate the nodes after 20-30 seconds.
  • I didn't check 802.11n
  • I have used the stock 3.16.0 kernel as the base, since wireless-testing with tag master-2014-08-11 gave kernel panic during wlan scan, even without my patch (but this is for another mail)
  • use wpa_passphrase to generate the wpa_supplicant WPA2 config file

Csaba