Re: WPA problem on FC5

Tom Kelly <[email protected]>
Newsgroups gmane.linux.drivers.ipw2100.devel
Message-ID <[email protected]>
Fixed.  This turned out to be a combination of a couple of
FC issues and pilot error.

My FC3 system didn't come with wpa_supplicant, so I integrated
it into the startup scripts by adding a call to the end of
/etc/sysconfig/network-scripts/ifup-wireless:

/usr/sbin/wpa_supplicant -ieth1 -Dipw -c /etc/wpa_supplicant.conf -wB

FC5 comes with wpa_supplicant installed as a service, so I tried using
that.  I tried running it in debug mode, but didn't see anything.  So
I added it to the end of ifup-wireless and it still didn't work.

Tonight I figured it out.

When wpa_supplicant is run before ifup-wireless, it immediately
associates and sets the key (as can be seen from iwconfig).

However, when ifup-wireless is run, it executes
the following:

if [ -n "$KEY" -o -n "$KEY1" -o -n "$KEY2" -o -n "$KEY3" -o -n "$KEY4" ] ; then
    [ -n "$KEY1" ] && iwconfig $DEVICE key [1] $KEY1
    [ -n "$KEY2" ] && iwconfig $DEVICE key [2] $KEY2
    [ -n "$KEY3" ] && iwconfig $DEVICE key [3] $KEY3
    [ -n "$KEY4" ] && iwconfig $DEVICE key [4] $KEY4
    [ -n "$DEFAULTKEY" ] && iwconfig $DEVICE key [${DEFAULTKEY}]
    [ -n "$KEY" ] && iwconfig $DEVICE key $KEY
else
    iwconfig $DEVICE key off
fi

Since we're using WPA, the key variables are unset, and we set the key
to off, wiping out what wpa_supplicant has set up.  I fixed
this by commenting out the line that sets the key to off, and it
started to work.  I think this is an FC problem - it shouldn't
modify the keys if using WPA.

Why didn't it work with the wpa_supplicant call at the end
of ifup-wireless?  I forgot the -wB options, which apparently
messed things up.

So it works now.   Sorry for the false alarm.

Note that NetworkManager (which works great with WEP) doesn't
work with WPA, and a quick look using iwconfig suggests that
the keys are getting wiped in that case too.  I'm
still looking into that.

Tom

Tom Kelly wrote:
> Hi folks -
> 
> Looking for suggestions.  If debugging information is needed, let me
> know.
> 
> The wireless setup works fine (i9ncluding WPA) with Fedora Core 3, ipw2200 1.0.8.
> 
> 
> Running ieee 1.2.15 with ipw2200 1.1.4 on Fedora Core 5.
> 
> Everything works fine with WEP.
> 
> wpa_supplicant needed -Dwext instead of -Dipw, but after that it
> successfully negotiates keys and associates.  However, no
> packets flow.  dhclient fails - the server never sees any
> of the DHCP request packets.
> 
> If using static IP addresses, ARP fails.
> 
> Ideas?  Suggestions for debug things to look for?
> 
> If I change the AP to use WEP, everything works.
> 
> Thanks,
> Tom
> 
> -------------------------------------------------------------------------
> 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

-------------------------------------------------------------------------
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
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.