Information from Testing rt73usb

Live forum: http://rt2x00.serialmonkey.com/viewtopic.php?t=4821

JustGreg

30-05-2008 19:24:32

I am a using of Puppy Linux. In the next version of Puppy, the 2.6.25.# kernel will be used. Along with the kernel change comes the use of the rt2x00 driver for WIFI. The my wifi adapters are based on RT73 chip set. The rt73usb module is used for my equipment. I did some testing (sucessful) on the new driver with a test release of Puppy ande 2.6.25 kernel. I used two scripts and manage to successfully connect with my wifi network using open, wep, wpa, and wpa2 encryption. The scripts are nothing out of the ordinary. I thought I would share them here for other people's information and use.

Here is the script that I used for open and wep

# From serialmonkey.com page; http//rt2x00.serialmonkey.com/wiki/
# and http//rt2x00.serialmonkey.com/wiki/ind ... x00_README
# Modified by Just Greg (9 May 2008) for Puppy Dingo with kernel 2.6.25
iwconfig wlan0 mode managed
# Enter SSID for the wireless network to connect
iwconfig wlan0 essid myessid
# for WEP connection enter 10 hexadecimal digit key
# for Open connection, comment the next line
iwconfig wlan0 enc AABBCCDDEE
ifconfig wlan0 up
# Show available networks and access point addresses
# if you need the ap address, 12 hexadecimal digits
# iwlist wlan0 scan
# make sure dhcpcd is not running and remove old pid file.
dhcpcd -k wlan0
rm /etc/dhcpc/dhcpcd-*.*
# some versions have pid in /var/run/, then uncomment next line
# rm /var/run/dhcpcd*.pid
# now to get IP address
dhcpcd -t 30 -h puppypc -d wlan0

In testing wpa and wpa2 encryption, I found that ap_scan needed to be set. The are three values (0, 1, and 2) for ap_scan. The value of 0 uses the driver to do the access point (ap) scanning. I found that ap_scan=0 was not reliable. Sometimes it work and other times, it did. The value of 1 uses the wpa_supplicant program to do the ap scanning. I found ap_scan=1 to always work with networks that broadcast the ESSID (or SSID) network name. The value of 2 associates with an ap using security policy and SSID in the wpa.conf or wpa2.conf file. It is the only way I could connect to a hidden (not broadcast) ESSID network.? If you are not able to connect to a wireless network, then I suggest that you try ap_scan with each of the three values. It worked for me.

Connecting to a wpa network, requires the use of wpa_supplicant and associated wpa.conf or wpa2.conf files.

Here is the general wpa.conf file that I used for wpa encrypted networks
ctrl_interface=/var/run/wpa_supplicant
# ap_scan=0
# ap_scan=1
ap_scan=2
update_config=0
network={
ssid="your network SSID"
key_mgmt=WPA-PSK
proto=WPA
pairwise=TKIP
group=TKIP
psk="your ASCII passhase"
}

Here is the general wpa2.conf that I use for wpa2 encrypted networks
ctrl_interface=/var/run/wpa_supplicant
# ap_scan=0
# ap_scan=1 works best with open SSID WPA or WPA2 networks and my Linksys usb
ap_scan=1
# ap_scan=2
update_config=0
network={
ssid="your network SSID"
mode=0
proto=RSN
key_mgmt=WPA-PSK
group=CCMP TKIP
psk="your ASCII pass phase"
}

Here is the script used to test the wpa and wpa2 networks
# Script to test Dingo kernel 4.6.25 wifi networking using wpa_supplicant
# For other drivers not using wlan0 (i.e. eth1 or ralink0) replace wlan0
# with the correct desination
# 17 May 2008 JustGreg
echo
echo "Starting up wlan0"
ifconfig wlan0 up
ifconfig wlan0
echo " "
echo "Now starting wpa_supplicant"
# Make sure another wpa_supplicant is not running
wpa_cli terminate
## now start wpa_supplicant
## first remove stale wpa_supplicant file if it exists
if [ -e /var/run/wpa_supplicant/* ]; then rm /var/run/wpa_supplicant/*; fi
wpa_supplicant -i wlan0 -D wext -c /root/my-applications/bin/mywpa2.conf -d
sleep 60
echo " "
wpa_cli status

I hope the above helps. I am a new user of this forum and hope this is the
correct place for this information.

Enjoy life, JustGreg
Live Well, Laugh Often, Love Much