On Tuesday 08 July 2008 14:29:27 Bill Wohler wrote: > Kel Modderman <[EMAIL PROTECTED]> wrote: > > > I am not sure how well ath5k is working currently, but sure do hope it > > becomes > > a good successor to the bug prone madwifi driver soon. > > Hi Kel, > > I switched to ath5k a couple of weeks ago. Unfortunately, there appears > to be a problem with ath5k, WEP, and my chipset AR5211. I can associate > with the AP, but the network connection doesn't come up. If I drop WEP, > then I can connect. > > In any event, since I use restricted MAC addresses on my AP, and use ssh > and ssl for communications, I'm content with using an unsecured network > for now, especially since my ath5k connections have been up for two > weeks solid now!
Promising ;) I'm not sure ath5k supports WPA well at all yet though. > > I'm hoping to improve things by switching to WPA per [1] but haven't > gotten around to that yet. By the way, do you know if this HOWTO is up > to date? > > In any case, I'm not going back to madwifi, so I wouldn't really be able > to test any changes you make. Therefore, please close this bug unless > someone else sends out a "me too". > > 1. > http://wiki.debian.org/Manual-Howto#head-6fdd87d329e68a583e5fde32c6b21e460e5541a5 > The example is over engineered, but still relevant. Usually a common /etc/network/interfaces stanza for static connection to WPA-PSK access point: iface wlan0 inet dhcp wpa-ssid ACCESSPOINTSSID wpa-psk SUPERSECRETKEY This is explained in more detial at /usr/share/doc/wpasupplicant/README.modes.gz Thanks, Kel. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
