Re: [Open1x-xsupplicant] xsupplicant sending replies to wrong address?

[John T. G. <gu...@co...>]

Hello Tim,

> 
> Hi John,
> 
> On Mar 25, 2004, at 4:04 PM, John T. Guthrie wrote:
> 
> > Hello all,
> >
> > I've been trying to set up xsupplicant on my laptop running redhat 
> > linux 8.0.
> > When I try to authenticate to my AP, I only see the message
> >
> > Connection Established, authenticating...
> 
> Which version of Xsupplicant are you using?
> 
> >
> > repeated over and over.  When I turn on ethereal, I see EAP identity 
> > request
> > packets coming from my AP to my wireless card.  Then I see EAP identity
> > response packets going from my wireless card to the address 
> > 01:80:c2:00:00:03.
> 
> 01:80:c2:00:00:03 is the Multicast address for 802.1x wired 
> authentication.
> 
> When a supplicant authenticates to a wired device, the appropriate 
> address to send to is the address listed above.  In the case of 
> wireless, the appropriate address is the BSSID (MAC Address) of the AP. 
>   Xsupplicant tries to determine whether or not a given device is 
> wireless or not, so it seems like this is failing for some reason.
> 
> If you are using the 0.8b code, you can force the destination address 
> by using the "-a" switch.  If you are using the latest CVS, you can use 
> the "dest_mac" parameter in the configuration file.  Obviously neither 
> one of these is going to work very well for a production environment 
> where your BSSID will likely be changing, but it will at least help you 
> test authentication.

I am in fact using 0.8b.  (This is the latest that I have been able to find on t
he web site.)  Sorry I forgot to include that the first time.  The -a flag
worked quite well to get xsupplicant and my AP talking to one another.

> > Does anyone know why xsupplicant is sending
> > packets out to that address and not my AP's address?
> 
> Hmmm I would venture to guess that xsupplicant is getting an invalid 
> response when it queries to determine what type of device your card is.
> 
> What driver are you using?  It could be that your driver is improperly 
> reporting itself.
> 
> > Is there some config
> > setting that I need to set?
> 
> You may also be able to force this to work by specifying that the 
> device is wireless in the xsupplicant configuration file.  (I can't 
> recall if this was actually turned on in the 0.8b and previous code, 
> but I know the option was around...)
> 
> Are you perhaps setting the wired flag in the configuration, or passing 
> the "-w" switch on the command line?
> 

I certainly haven't been using the -w flag.  I don't have any settings either
way in the config file.  One thing that might be relevant though is the fact
that my laptop has a builtin ethernet interface that always shows up as eth0.
My wireless card always shows up as eth1.  Could the fact that eth0 is a wired
interface be affecting anything?  BTW, the card that I am using uses the
prism54 driver.  (http://prism54.org/.)

Thanks for all of the help.

> - Terry

John Guthrie
gu...@co...