DWL-G122 802.11g rev. B1 / WEP / 1Mbps

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

ilgiz

08-12-2008 06:43:57

Could not connect with either of these drivers from DWL G122 rev B1 to SMC 7004 VWBR where I had to set the 1Mbps transmission and basic rates in order for the other machines to connect to the access point.
(a) rt2500usb from Debian unstable 2.6.26-1-686 (version 2.6.26-11)
(b) rt2570-cvs-2008120722.

With the former driver, I was getting the "authentication frame received but not in authenticate state" message,
[code1wq2iufu]
Dec 7 21:54:10 ei kernel: [34028.370480] rt: Initial auth_alg=0
Dec 7 21:54:10 ei kernel: [34028.370528] rt: authenticate with AP 00:04:e2:8e:86:aa
Dec 7 21:54:10 ei kernel: [34028.570243] rt: authenticate with AP 00:04:e2:8e:86:aa
Dec 7 21:54:10 ei kernel: [34028.769988] rt: authenticate with AP 00:04:e2:8e:86:aa
Dec 7 21:54:10 ei kernel: [34028.959761] rt: RX authentication from 00:04:e2:8e:86:aa (alg=0 transaction=2 status=0)
Dec 7 21:54:10 ei kernel: [34028.959794] rt: authenticated
Dec 7 21:54:10 ei kernel: [34028.959807] rt: associate with AP 00:04:e2:8e:86:aa
Dec 7 21:54:10 ei kernel: [34028.960515] rt: authentication frame received from 00:04:e2:8e:86:aa, but not in authenticate state - ignored
Dec 7 21:54:10 ei kernel: [34028.961803] rt: authentication frame received from 00:04:e2:8e:86:aa, but not in authenticate state - ignored
Dec 7 21:54:11 ei kernel: [34029.158184] rt: associate with AP 00:04:e2:8e:86:aa
Dec 7 21:54:11 ei kernel: [34029.359232] rt: associate with AP 00:04:e2:8e:86:aa
Dec 7 21:54:11 ei kernel: [34029.560545] rt: association with AP 00:04:e2:8e:86:aa timed out
Dec 7 21:54:12 ei kernel: [34030.312706] rt: authentication frame received from 00:04:e2:8e:86:aa, but not in authenticate state - ignored
Dec 7 21:54:12 ei kernel: [34030.313434] rt: authentication frame received from 00:04:e2:8e:86:aa, but not in authenticate state - ignored
[/code1wq2iufu]

With the latter, I saw "AUTH - AuthTimeout" messages (see the attached file rt2570-debug31.txt).

Here is my /etc/network/interfaces for the interface[code1wq2iufu]
iface rt inet static
address 192.168.2.172
netmask 255.255.255.0
network 192.168.2.0
broadcast 192.168.2.255
gateway 192.168.2.1
dns-nameservers 192.168.2.1
wireless_mode managed
wireless_essid YY
wireless_ap 00:04:E2:8E:86:AA
wireless_key s:XXXXXXXXXXXXX
# wireless_channel auto
wireless_channel 6
wireless_bit 1M
wireless_rate 1M
up /sbin/iwconfig "${IFACE}" key open
# up sleep 3; /sbin/iwlist "${IFACE}" scan
up sleep 3; /sbin/iwconfig "${IFACE}"
# up /sbin/iwconfig "${IFACE}" ap 00:04:E2:8E:86:AA
up /sbin/ip route add 224.0.0.0/4 dev "${IFACE}"
[/code1wq2iufu]

(To rename the interface of the former driver, I changed the name against the MAC address in /etc/udev/rules.d/70-persistent-net.rules. With the latter driver, I removed /etc/modprobe.d/ralink, added the MAC to /etc/mactab and ran /sbin/nameif).

ilgiz

08-12-2008 06:46:04

Forgot to mention that the Windows XP pro drivers v1 and v2.04 worked intermittently. I could not find the cause of them stopping working.

The other Linux driver, adm8211, connects the ADMtek ADM8211 with my SMC access point using the same /etc/network/interfaces options just fine.

Vern

08-12-2008 15:48:34

Hi ilgiz,

From the looks of the /etc/network/interfaces file you supplied, it looks like you're naming the rt2570 device "rt". Does "ifconfig" show an interface named "rt"? If not, have you tried adding "ifname=rt" to the modprobe command line? (Otherwise, the drive calls the interface "rausb0".)

Thanks,

ilgiz

09-12-2008 04:14:42

Thanks, Vern. I did not try supplying the module's ifname option to modprobe and I removed /etc/modprobe.d/ralink because I manually rename the interface to "rt" using the "nameif" command that looks up my /etc/mactab.

I remember that the Debian's rt2500usb driver's interface was renamed by udev where I assigned it the same name, "rt".

Vern

09-12-2008 17:18:18

Hi ilgiz,

While the driver can accept a command to change the MAC address it uses, it *cannot* accept a command to change its interface name. The nameif command doesn't enter into it here. Changing the interface name can only be done via the modprobe options I mentioned above, hence my questions.

Thanks,

ilgiz

09-12-2008 18:28:24

Well, the "ip link list" command showed that the interface was renamed by my "nameif" invokation. And I think the attached log files show attempts to associate with the access point.

My conjecture is that there are 2 factors that make my case unusual

(a) I limited the SMC access point to 1Mbps transmission and basic rates because it stopped being reachable by other machines at 11Mbps. I think this indicates some deterioration of the radio hardware in the first place. The access point is few years old.

(b) My D-Link USB stick showed unstable connectivity even under its Windows drivers. Recently, the link would re-appear only sporadically, in about 1 try out of 20.

Vern

10-12-2008 16:57:58

Hi ilgiz,

Just took another look at the info in your original post.[quote2e5j3o3k]... but not in authenticate state - ignored[/quote2e5j3o3k] is not issued by the legacy driver. Looks like you're using the nextgen driver. Maybe Ivo can help.

Thanks,

ilgiz

11-12-2008 18:59:08

Interesting. I tried both. The other driver's logs should be in the attachment to the first posting. Thanks for your patience.