Re: Can't WPA associate with latest ipw2200 driver (1.1.3)

Hi,

I've been experiencing the same things with my Netgear router running
in BG mode, 54MB and with WPA.  Here's the work-around that I've come
up with that allows me to connect.

First, you must have the following modules loaded.  For some reason
missing any of them prevents the thing from working.
80211_crypt_wep, 80211_crypt_ccmp, 80211_crypt_tkip

Next, use iwconfig to set your card to managed mode.
iwconfig eth1 mode managed

then set the card to be unassociated with any access point
iwconfig eth1 essid off

then wpa supplicant should associate.and successfully handshake.
wpa_supplicant -Dwext -i eth1 -c /etc/wpa_supplicant.conf -w -W

Lucky for me, my own access point is the only one visible.  Setting
the essid value using iwconfig will prevent the wpa_supplicant from
successfully handshaking.  It MUST be set to off and allow
wpa_supplicant to set the essid.  Furthermore, setting any other
options like RTS, power, rate, channel, etc seems to make the thing
fail as well.

If any of these fail, you must unload all of your modules, including
all ipw2200 and all ieee80211 modules.  Then restart the process
again.  It took me quite a bit of trial and error to get this
combination to work.  On my system any deviation from these steps will
prevent it from succeeding.

Also, disassociating from the AP will cause all subsequent
reassociations to fail.  If you diassociate from the AP you have to
unload and reload the modules and repeat the process.

I'm using:
 ipw2200 version 1.1.3
 ieee80211 version 1.1.14
 wpa_supplicant version 0.4.9
 kernel 2.6.16.16

Let me know if this works for you.

-Jing


On 7/14/06, TNKS <[email protected]> wrote:
> Zhu Yi wrote:
>
> > Did you enable QoS in your AP? If so, can you disable it and see if it
> > works or not?
>
> It's possible that my Netgear router is old enough that it doesn't offer any
> QoS functionality.  I didn't see any such option on the router's HTTP-based
> configuration interface.  Let me know if there's something else on my
> router you want me to check for.
>
> > Can you also try 1.1.3/1.1.13? It helps to identify it's a ieee80211
> > regression or ipw2200.
>
> Okay, so I tried 1.1.3/1.1.13, and I got a really bad kernel panic.  I
> didn't go through the labor of transcribing the stack trace of the panic,
> but maybe you can reproduce it on your end.
>
> On the other hand, I'm now currently running 1.1.2/1.1.14, and it seems to
> be running fine.  So I think with respect to regression, the problem seems
> to be with 1.1.3.  Certainly a kernel panic definitely worth looking into
> if there's no known reason that 1.1.3 shouldn't work with 1.1.13.
>
> Looking forward to you respond; happy to help out further.
>
> -Sukant
>
>
>
>
> -------------------------------------------------------------------------
> Using Tomcat but need to do more? Need to support web services, security?
> Get stuff done quickly with pre-integrated technology to make your job easier
> Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
> http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
> _______________________________________________
> ipw2100-devel mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/ipw2100-devel
>

-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys -- and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV