|
Name: Ken Young
Linux Distribution: Open Suse
Supplicant Used: Open 1X
Comments: Hi,
I'm Ken Young, the moderator for this forum. We're hoping that, in true open source collaborative fashion, we can develop a simple and effective CWU wireless solution for Linux users by sharing our knowledge here. I'll post the parameters for connecting to CWU wireless below and some code snippets/suggestions to get things started. Please post anything you've come up with or questions you may have and we'll see how far we go.
Ken
Code Example:
|
|
Name: Tyler Leavitt
Linux Distribution: Debian (Ubuntu 8.04 Hardy Heron)
Supplicant Used:
Comments: I'm running Madwifi drivers on my atheros chipset as well... just wanted to post that it worked for the most recent updated Hardy Ubuntu distro. Thanks!!!
Also... is it possible Ken to get this fix on the main site (it says no fix is currently available)? I wasn't able to access this forum until I got to a hard-wired computer (seeing as we are trying to fix our wireless...).
Thanks again for all the help!
Code Example:
|
|
Name: Michael Wilson
Linux Distribution: Debian
Kernal: 2.6.26-1-686
Wireless Chipset: Atheros
Driver: madwifi-ng
Supplicant Used: The debian package provides integration to /etc/network/interfaces. Debian 4.0 (using lenny repositories) will work out of the box, so long as you have the correct drivers for your chipset.
Comments: wpa_supplicant is no longer supported in Debian (lenny). There is now a "Network Manager". It should be set up like this....using your name and password of course!!
Code Example: First "Connect to other wireless network"
Then fill in the blanks and click connect.
|
|
Name: Ken Young
Linux Distribution:
Supplicant Used:
Comments: Michael, thanks for the post (and the excellent instructions). One interesting thing about your setup: We actually use WEP as our security protocol rather than WPA2 Enterprise. The reason it works is that the WPA2 standard requires that the supplicant query the access point to see if it supports WPA2; if not, the supplicant can fall back to WEP. We are configuring iPhones/iPods to use WPA2 since they routinely fail when set to WEP. You may see some lag at initial connection this way but it seems to work fine otherwise.
Code Example:
|
|
Name:
Linux Distribution:
Supplicant Used:
Comments:
Code Example:
|
|
Name:
Linux Distribution:
Supplicant Used:
Comments:
Code Example:
|
|
Name:
Linux Distribution:
Supplicant Used:
Comments:
Code Example:
|
|
Name:
Linux Distribution:
Supplicant Used:
Comments:
Code Example:
|
