Bug 436350
| Summary: | WEP does not work ("link is not ready") | ||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Gene Czarcinski <gczarcinski> | ||||||||||||||||
| Component: | kernel | Assignee: | John W. Linville <linville> | ||||||||||||||||
| Status: | CLOSED NOTABUG | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||||||||||||
| Severity: | medium | Docs Contact: | |||||||||||||||||
| Priority: | low | ||||||||||||||||||
| Version: | 8 | CC: | kernel-maint | ||||||||||||||||
| Target Milestone: | --- | ||||||||||||||||||
| Target Release: | --- | ||||||||||||||||||
| Hardware: | i386 | ||||||||||||||||||
| OS: | Linux | ||||||||||||||||||
| Whiteboard: | |||||||||||||||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||||||||||||||
| Doc Text: | Story Points: | --- | |||||||||||||||||
| Clone Of: | Environment: | ||||||||||||||||||
| Last Closed: | 2008-03-11 14:27:35 UTC | Type: | --- | ||||||||||||||||
| Regression: | --- | Mount Type: | --- | ||||||||||||||||
| Documentation: | --- | CRM: | |||||||||||||||||
| Verified Versions: | Category: | --- | |||||||||||||||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||||||||||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||||||||||||||
| Embargoed: | |||||||||||||||||||
| Attachments: |
|
||||||||||||||||||
|
Description
Gene Czarcinski
2008-03-06 18:00:43 UTC
The "link is not ready" is expected and unimportant enough that we should probably find a way to prevent it from showing-up. :-( Please attach the contents of /var/log/messages, as well as the output of running 'lspci -n', 'iwlist wlan0 scan', and 'iwconfig wlan0'. Hopefully that will give us sufficient info to begin narrowing the search...thanks! Attachments follow. I did a fresh bootup and edited the /var/liog/messages to only have this bootup. I I two interfaces configured identically .. the internal Broadcom BCM4306 and the Linksys WPC55AG PC card. I have redacted the key from the iwconfig listing files. Both interfaces are configured to use dhcp. After the final failuse of the Broadcom, the interface was disabled and I re-did deactive/active wlan0 so that I could run iwlist wlan0 scan while the interface was enabled for dhcp tries. The Linksys stayed enabled after failure so iwlist work during and after. Created attachment 297206 [details]
/var/log/messages
Created attachment 297207 [details]
lspci
Created attachment 297208 [details]
lspci -n
Created attachment 297209 [details]
iwconfig wlan0
Internal Broadcom BCM4306
Created attachment 297210 [details]
iwlist wlan0 scan
Created attachment 297212 [details]
iwconfig wlan1
Linksys WPC55AG
Created attachment 297213 [details]
iwlist wlan1 scan
both interfaces work with the "winchester97" unencrypted AP. Just for the hell of it, I consigured a Linksys WRT54G to use WPA-Personal. I then (using NetwortManager) connect to it with no (NO!) problem. Unfortunately, my situation is that I have a two segment network with the two wired segments connected via 54G wireless. On the one segment (the segment actually connected via a firewall to the Internet), I have a WAP54G running WEP ... why WEP instead of WPA ... the other wire segment has a WET54G "bridge" which is only capable of no security or WEP. I cannot find a commercial product which supports bridging into a 54G WPA netowrk. Is "JruQNcb8DN6Y" your WEP AP? Or is it one of the other ones? FWIW, I use WEP nearly every day on a variety of hardware. It is a very simple protocol, so I am surprised you would be having any trouble with it. How are you configuring your wireless network? NetworkManager? system-config-network? Or manually (i.e. iwlist, iwconfig)? If the latter, what is the exact sequence you are using? 1. Yes, "JruQNcb8DN6Y" is my WEP AP ... yes, I named it before I realized that these names were quite visible ... I really should change it except that everything works right now (except for Fedora). This was originally implemented/configured in the Fedora Core 1 timeframe. 2. I have tried using s-c-network, NetworkManager, and command-line (iwconfig, etc.) to configure/control the network interface with WEP and they all result in the same thing ... it does not work. I fully believe that it is some configuration stupidity on my part but have not got a clue as to where the error is. I would prefer to use s-c-network or NetworkManager as oppose to command-line. 3. Not wanting to screw with the existing hardware/configurations since I need it to work to support some systems, I decided to get another AP to see if un-encrypted worked for me ... it turns out that Best Buy is running a fire-sale right now on the Linksys WRT54G ($45) so I got one. I configured the WRT54G up unencrypted with MAC filtering and tried it with Windows-XP and Fedora 8 (with the various interfaces including the Broadcom BCM4306) ... it worked fine [NetworkManager is nice]. Mmmmm ... lets try WPA-Personal. Wow, that works too with both Windows-XP and Fedora 8 (using NetworkManager) [I have no idea how to configure it with s-c-network]. Not only did it work but it appears to work better than the old stuff (stronger signal and faster). This worked so well that I bought a second WRT54G (at $45, why not) and got a copy of dd-wrt ... I am in the process of setting this second WRT54G up as a client-bridge for the lan segment that currently uses a WET54G (which does not support WPA and actually costs more ... $100). To be blunt, I got tied of beating my head against the wall and tried someting different which seems to work (both better and with better security). Once I get everything working to my satisfaction, I intend to replace the old WEP based wireless with this new WPA based wireless. That said, the WEP based stuff is there (and can stay in place for a while) and I am willing to debug things (I really would like to know why it does not work and I have the time to support it) ... if it is a configuration error on my part, then maybe it will help someone else; if it is a "bug", then maybe it can be identified and fixed. But, my need to have it work has greatly reduced. It is up to you ... If you have a lot of other high priority work, then bag it. If you can spend some time figuring this out with me then great, lets continue. WEP should definitely work, so it iw probably worth figuring-out what might be happening... IIRC, switching from WPA to WEP on the wrt54g is pretty simple. Did you happen to try a WEP configuration with the new AP? Stick with NetworkManager -- since that was working for you with WPA, it should work w/ WEP too. If not, then please attach a new copy of /var/log/messages, one taken after you have tried to connect w/ WEP using NetworkManager. Sometimes that gives more information...thanks! OK, I will run the WEP test with the WRT54G later today. Right now I suspect that the problem is the WAP54G box/firmware. This an early box as there is no version specified on the external label and the firmware is V 1.06 dated Feb 2003. Unfortunately, I need it to support what it currently supports and did not want to screw with it (e.g., screw it up so supported stuff does not work). OK, I just ran a "quick" test with WEP on the WRT54G and it did not work with my
intent to document later ...
... but, then I was "fooling" around with both the WPA1 and WEP (production) APs
working. I tried to connect using NetworkManager to the WEP AP ("JruQNcb8DN6Y")
... son of a gun ... it WORKED!!!
I have no idea what I did to make it work but it is working (no updates applied
for the last few days).
I reran the test using s-c-network and it did not work (??) Since
NetworkManager does work, that is good enough.
I am closing this NOTABUG
|