Red HatThis forum is for the discussion of Red Hat Linux.
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
Reading all of this makes me feel a little bit better - at least it's showing that I'm not the only one with problems with an ADMtek card with Fedora Core 1!
The problem with mine is that it's simply not /talking/ to anything however - either with the 103 or 105 driver. With me though, each reboot is a brand new 'experience'. Once, it actually let me talk to mozilla.org long enough to download Firebird before it simply stopped talking to my AP. Usually, the signal light blinks happily (which my SMC card does when it /is/ connected to an AP,) but, nothing else.
Most of the times I get an IP address from the AP - but nothing else happens. Can't even ping or log into the router.
Sometimes it connects, and nothing at all happens. iwconfig also shows different information at different times. Sometimes the channel info/essid/etc. info simply doesn't get set at all. Sometimes I can change the info, sometimes I can't.
As always, with problems I'm having, I'm sure it's something right in front of me that I'm missing. :/
I my case I turned on the debug info in the 1.05 source from admtek
and saw that the card occaisionally does a channel research and afterwards is unable to setup the connection well again. This also happens when doing an iwconfig eth1 essid ..... The solution is in my case not to restart the networking again, but simply reset the WEP encryption key.
iwconfig eth1 key 0000-0000-00. The driver notifies us when doing the rescan by telling: set channel 1. I found this in the sources and tried to insert the key again straight afterwards, but the c structs are to complicated for me to do the right calls. Slight difference with the people above is maybe that in my case it concerns an Ad-Hoc network with encryption.
Hopefully this will help someone to either identify the bug in the source or patch a workaround.
Hi wbertels, that's the same behavior I noticed.
I tried resetting the encryption key for a while, however, I found that on some occaisions it wasn't doing the trick and the card still refused to communicate until it is reset.
And I'm using the same setup, adhoc with encryption.