PDA

View Full Version : WEP Causes segmentation fault


crossmr
16th January 2006, 03:20 PM
Okay I have tracked this problem to the following issue:
During my upgrade to gnome 2.12 it upgraded my kernel from 53 to 56.
I can no longer connect to wireless networks that require a WEP key.
I can bring up my wireless connection with wpa_supplicant or wlassistant and view available networks.
I can connect to an unprotected "default" someone has left open in my building
as soon as I try to connect to my home network which requires a wep key, there is a segmentation fault and it locks up. It doesn't matter whether I'm using those applications or the Network GUI, they all lock up. The network GUI is the only one that reports the segmentation fault, but they both cause the same lock up and weirdness on restart (yet another restart clears it all up and everything is fine again)

I had reinstalled the firmware, driver and ieee stuff after upgrading the kernel.

The wireless adapter on my laptop is an ipw2200BG.

Somehow, something to do with WEP has gotten mucked up, has this happened to anyone before? and if so how did they solve it?
I'm using 1.0.10 driver off sourceforge, 2.4 firmware, and latest ieee from sourceforge (don't recall the version right off, but I know it was the latest as of yesterday)

accessrichard
17th January 2006, 04:42 AM
I can't speak for your specific case, however I use wpa encryption and a lot of the issues I have had with ndiswrapper and wpa_supplicant were solved by updating or downgrading wpa_supplicant and/or ndiswrapper.Here is a quote on one of my blogs regarding ndiswrapper, wpa_supplicant and the kernel with a broadcom card.

" Version 1.2(ndiswrapper) would not work correctly with wpa_supplicant, version 1.3 did. Version 1.4 did not reckognize my broadcom driver, Version 1.5 did and worked correctly with wpa_supplicant"

Again, I did not change any ndiswrapper or wpa_supplicant settings, however my blog posting was written on a kernel update.

I am no expert on the ndiswrapper or wpa_supplicant, however, hopefully this will help

crossmr
17th January 2006, 04:20 PM

I've been in contact with Bill Moss who's had me upgraded to the 56.netdev.8 kernel, which has solved most of my issues. The wireless works, but only with a static IP. It seems something is wrong with my dhclient. I can get an IP easily over my NIC, but it seems that its having issue properly retrieving an IP over the wireless. I tested my wireless connection with another wireless PC I had and it was functioning correctly (so the issue is definitely on my machine). I also notice that if I try to release my network connection and renew it, it gives me a dhclient error. Is there an error log I could look at or other messages to see what the errors may be here? I've checked and I'm updated to the latest DHCP stuff via yum.