madwifi or not?

[pkoufalas]

Jochen, I have the same multimode Atheros chipset on my laptop and am
using Hoary, stock.  Your WPA config pretty much matches mine and I
have it working with WPA-PSK+TKIP.  But I did have to use static
configuration rather than DHCP--I am 99% sure the issue with dynamic
configuration was at the other end, not in the laptop. (In any case, it
authenticated fine.)



You can use the wireless-tools utilities to check things out on ath0,
e.g.



sudo iwconfig ath0



as well as



sudo wpa_cli



to check on authentication.



Nb: The /etc/defaults script is for use by /etc/init.d scripts as far
as I know.  It is read if you have the wpa_supplicant service in
/etc/init.d starting on boot.  But I do what you do and use pre-up and
down or post-down to start and stop it.



On 8/20/05, Jochen Kaechelin <gissmoh at gmx.de> wrote:

> Am Samstag 20 August 2005 17:51 schrieb Shannon McMackin:

> > Jochen Kaechelin wrote:

> > > i have a netgear WG511T and FritzBox WLAN FON.

> > > everything works fine with WEP but WPA won't work.

> > >

> > > my wireless-card runs with these kernel-modules

> > >

> > > ath_pci 55584 0

> > > ath_rate_onoe 8840 1 ath_pci

> > > wlan 106588 4 wlan_wep,ath_pci,ath_rate_onoe

> > > ath_hal 133328 2 ath_pci

> > >

> > > out of the box running hoary with all updates.

> > >

> > > ####

> > > /etc/wpa_supplicant.conf:

> > >

> > > ctrl_interface=/var/run/wpa_supplicant

> > > eapol_version=1

> > > ap_scan=2

> > > network={

> > > ssid="OX-XXXXX"

> > > proto=WPA

> > > key_mgmt=WPA-PSK

> > > pairwise=TKIP

> > > group=TKIP

> > >

> > > psk=088447a0dbba29########ecfff3e#####c0d107730### ##1811179fa95

> > >f1c75e }

> > > ####

> > >

> > > ####

> > > /etc/default/wpasupplicant:

> > >

> > > ENABLED=1

> > > OPTIONS="-w -i ath0 -D madwifi -B"

> > > ####

> > >

> > >

> > > ####

> > > /etc/network/interfaces:

> > >

> > > auto ath0

> > > iface ath0 inet dhcp

> > >

> > > pre-up /usr/sbin/wpa_supplicant -D madwifi -i ath0

> > > -c /etc/wpa_supplicant.conf -dd

> > > post-down killall -q wpa_supplicant

> > >

> > > ####

> > >

> > > Do I really have madwifi???

> > > Theres no .deb called "madwifi" on my system, but severel

> > > documentations who describe how to install madwifi from source

> > > uses the same kernel modules as I do.

> > >

> > > Any hints?

> >

> > A simple lspci -v -v will tell you what network chipset you have.

> > The madwifi driver is probably part of the kernel as opposed to

> > an add-on module which is why you don't see a separate .deb for

> > it.

> 

> Thank you!

> 

> 0000:06:00.0 Ethernet controller: Atheros Communications, Inc.

> AR5212 802.11abg NIC (rev 01)

> Subsystem: Netgear: Unknown device 4b00

> Flags: bus master, medium devsel, latency 168, IRQ 9

> Memory at 1f000000 (32-bit, non-prefetchable) [size=64K]

> Capabilities: [44] Power Management version 2

> 

> --

> Glück ist nur was für Menschen die nichts drauf haben.

> 

> http://gissmoh.de

> 

> --

> ubuntu-users mailing list

> ubuntu-users at lists.ubuntu.com

> http://lists.ubuntu.com/mailman/listinfo/ubuntu-users

>


-- 
pkoufalas