From: Andrew B. <bar...@os...> - 2004-09-30 21:36:49
|
There has been some discussion on the list recently about issues with the LEAP keying code. I went back to school here recently, and so I've had a chance to try the code on the wireless network on campus. I have an Intel PRO/Wireless 2100 Network Connection in my notebook, and it is driven by the ipw2100 driver version 0.55. My first few tries with xsupplicant 1.0.1 were successful, but then I started running into trouble. One of two things happens: 1) I see "connection established, authenticating..." over and over again as my network adapter repeatedly disassociates and reassociates with the AP. Or, I see that message once and xsupplicant crashes; there is no "segmentation fault" or similar message, but it leaves behind it's PID file (/var/run/xsupplicant). Don't worry if my descriptions are too vague, I have a logfile from running 'xsupplicant -i eth1 -f -d6', I just didn't want to post it to the list because it probably has my password in it. I am not out of ideas yet, I have other wireless hardware to try, I am going to try ndiswrapper, and I have also built a patched version of xsupplicant that includes the LEAP reauth fix described by Benjamin Reed yesterday. My progress in trying these ideas is slow because I don't live on campus and I'm only up there until noonish, and I have class almost the entire time. If someone knows what my issue is or would like to see my log, please let me know. Thanks in advance, Andrew P.S. I'll probably be changing my password after this, so there's no worries there. |