================== TEST ENVIRONMENT ================== Laptop with ipw2200 driver Distribution - Debian, Gentoo, RH/FC, SuSE (latest version) Kernel - Kernel required by INSTALL file or the latest kernel in the distribution. ============== FEATURE LISTS ============== This test plan will cover the following features of ipw2200: 1. Infrastructure Mode 2. Ad-hoc Mode 3. SSID scan 4. Processor Power Mgmt on 2.6 kernel and 802.11 Power Mgmt 5. AP to AP roaming 6. WLAN Extention Support, including iwconfig, iwpriv, iwspy 7. WEP 8. 802.1X 9. Install 10. Rate scaling 11. Fragmentation 12. Data transfer 13. Promiscuous mode 14. WPA/WPA2 ============== TEST COVERAGE ============== Using eth1 as the wireless network interface Infrastructure Mode Testing ---------------------------- 1. Test Association + Associate eth1 with valid essid with/without WEP + Associate eth1 with invalid essid + Associate eth1 with a closest AP, Reassociation + Switch eth1 from one AP to another one 2. Data Transfer See the Data Transfer Section. Basically it will include: + Send Unicast package to another wireless machine + Send Multicast package to the network + Using tools like scp, ftp, netperf, ping to test the data transfer + Using remote login like ssh, telnet, rlogin, rsh, etc. Ad-hoc Mode Testing -------------------- 1. Ad-hoc configuration testing + Configure two laptops in ad-hoc mode without WEP + Configure two laptops in ad-hoc mode with WEP + Using three laptops in ad-hoc mode 2. Data Transfer See the Data Transfer Section. Basically it will include: + Send Unicast package to another wireless machine + Send Multicast package to the network + Using tools like scp, ftp, netperf, ping to test the data transfer + Using remote login like ssh, telnet, rlogin, rsh, etc. 3. Interoperability Test Between laptops with different wireless drivers. + Laptop with b driver to communicate with bg driver + Laptop with bg driver to communicate with abg driver + Laptop with b driver to communicate with abg driver SSID Scan Testing ----------------- 1. Test the iwlist command + iwlist eth1 scanning + iwlist eth1 frequency + iwlist eth1 channel + iwlist eth1 bitrate + iwlist eth1 rate + iwlist eth1 encryption + iwlist eth1 key + iwlist eth1 power + iwlist eth1 txpower + iwlist eth1 retry 2. Functional testing to SSID Scan + Change each parameter value to see the scan result Processor Power mgmt on 2.6 kernel ---------------------------------- 1. Test the influence of C state to wireless driver 2. Test the influence of S state to wireless driver 802.11 Power mgmt ----------------- + Set different beacon interval + Set different Tx/Rx Timeout AP to AP Roaming ---------------- + Test the switching from one AP to another AP + Test whether the driver can find the nearest AP WLAN Extention Support ---------------------- Note: iwlist is not covered in this section since it is heavily covered in the SSID Scan Testing section. 1. iwconfig + Test the essid parameter + Test the nwid parameter + Test the freq parameter + Test the channel parameter + Test the sens parameter + Test the mode parameter + Test the ap parameter + Test the nick parameter + Test the rate parameter + Test the rts parameter + Test the frag parameter + Test the txpower parameter + Test the enc/key parameter + Test the power parameter + Test the retry parameter + Test the commit parameter + Using combination parameters to test iwconfig 2. iwpriv + Test the command of iwpriv 3. iwspy + Test the command of iwspy WEP --- The following scenarios should be tested with WEP enabled on the laptop and the AP: + Association/Disassociation + All key parameters (open/restricted, string/hex, all four keys) + Changing keys on AP and laptop and reassociating. + Error case: Associating with WEP-enabled AP without a key. + Error case: Associating with WEP-enabled AP with wrong key. + Error case: Associating with non-WEP-enabled AP using a restricted key. + Run through fragmentation tests with WEP enabled. + Run through infrastructure mode tests with WEP enabled. + Run through ad-hoc tests with WEP enabled. + Run through data transfer tests with WEP enabled. 802.1X ------ (Contributed by Terry Simons. Many thanks!) + Infrastructure mode tests with 802.1X. + Association/Disassociation + Open mode w/fake WEP key + Authentication tests. If possible, basic testing of LEAP should be performed. As well, basic testing of one of the types TLS, PEAP, or TTLS should be performed. + Key set tests. + Error case - Card reset bug. i.e. Verify that authentication loop does not occur when key is set + Error case - Broadcast key set bug. i.e. Verify that xmit key is not set on "EAPoL Broadcast" key sets + Data transfer tests using 802.1X. + Error cases where AP is set to a different encryption method. + WPA "Compatibility" Mode w/TKIP unicast-cipher, WEP multicast-cipher. Install ------- Run through all instructions in the install file for the following scenarios: + Legacy firmware load/Hotplug firmware load + Built within the kernel/Built outside the kernel + WEP enabled/WEP disabled + Using each of the distributions listed above. After installation, perform: % modprobe ipw2100 <- Verify no error messages appear. % lsmod | grep ipw2100 <- Verify ipw2100 module is loaded. % iwconfig eth1 essid % iwconfig eth1 key * If WEP was enabled. % ifconfig eth1 up <- Verify no error messages appear. % ifconfig eth1 <- Verify valid IP address has been assigned. % ping -I eth1 <- Verify response is received. Driver load/Unload Some issues have been seen depending on the order of driver loads and unloads. Some tests to perform are: + Basic driver load: % modprobe ipw2100 <- Verify no error messages appear. % lsmod | grep ipw2100 <- Verify ipw2100 module is loaded. % ifconfig eth1 up <- Verify no error messages appear. % ifconfig eth1 <- Verify valid IP address has been assigned. % ping -I eth1 <- Verify response is received. + Driver load replacing modprobe with insmod. + Driver load replacing ifconfig eth1 up with ifup eth1. + Driver load before turning radio on. + Driver load after turning radio on. + Error case: Bring interface up before driver load. + Configure machine to load the driver on system restart and restart the machine. + Test the load parameters: mode={0=bss,1=ibss,2=monitor} channel=n (Defaults to mode=0.) + Basic driver unload: % ifconfig eth1 down<- Verify no error messages appear. % ifconfig eth1 <- Verify no IP address is assigned. % rmmod ipw2100 <- Verify no error messages appear. % lsmod | grep ipw2100 <- Verify ipw2100 module is no longer loaded. + Driver unload with modprobe -r ipw2100. + Do not bring the network down before driver unload. + Driver unload replacing ifconfig eth1 down with ifdown eth1. + Configure system to not load the driver on system restart and restart the machine. Rate scaling ------------ Test the following scenarios: + Ensure connection always happens initially at 11Mbps. + Increase traffic on network, and ensure connection decreases to 5.5Mbps, then 2Mbps, then 1Mbps. + Decrease traffic on network and ensure connection increases in reverse order. + Use iwconfig to verify signal quality is decreasing as traffic increases and increasing as traffic decreases. Fragmentation ------------- The following scenarios should be executed and verified using the methods above: + Tx data where fragmentation is set to 3 values between 256 and 2346. + Rx fragmented data where fragmentation on Tx machine is set to 3 values between 256 and 2346. + Perform above tests in infrastructure as well as adhoc modes. + Perform above tests with WEP enabled. RTS/CTS RTS and CTS should also be tested. To test these, perform: echo "768" > /proc/net/ipw2100/debug_level. Also, see /proc/net/ipw2100/eth1/ordinals for more info. Then, perform the following tests: + Set RTS to three values. Probably between 250 and 2400. + Perform above tests in infrastructure as well as adhoc modes. + Perform above tests with WEP enabled. Fragmentation parameters Also, test the fixed, auto, and off parameters of iwconfig eth1 frag. Data transfer ------------- The following data transfer scenarios should be tested. They should use secure (scp) and non-secure (ftp) transfers. + Test Tx/Rx of a small (< 1Mb) file. + Test Tx/Rx of a 1G and 2G file. + Test Tx/Rx of 100 files of sizes from 1Mb-2G. The following are other types of data transfer scenarios. + Test downloading files from a website. + Test watching a streaming video from a website. + Test using ssh/telnet to connect to a remote machine Promiscuous mode ---------------- The following scenarios should be tested: + Test that a basic ping can be seen using Ethereal. + Perform the above test with WEP enabled. + Test moving from monitor->managed and managed->monitor. In managed->monitor, test not bringing down the network beforehand. WPA/WPA2 -------- 1. Test association via wpa_supplicant, with an AP that is: + using WPA-PSK + using WPA-EAP (FreeRadius Server needed.) 2. Data Transfer + Test Tx/Rx of a large file via ftp. Copyright (c) 2004 Intel Corporation. All rights reserved. This material may be distributed only subject to the terms and conditions set forth in the Open Publication License, v1.0 or later (the latest version is presently available at http://www.opencontent.org/openpub/).