Had it working for a short while on F7 then an update killed it. Never worked since.

Tried going to F8 as I read ath5k was suppose to support it but nothing. Madwifi nor ndiswrapper work either.

No problem to find the router but theres something running in the back ground thats calling for "master" mode vs the "managed" I'm calling for via iwconfig or the graphical way-guessing they're the same?

Asks for key over and over. Even though its been entered every time. Seems as if theres 2 cooks in th kitchen on this thing.

What can I do to see where my key is ending up or whats really reporting to the router? Or what keeps setting the device to master?

Alright after a few more tries here I'm back to nowhere. Ubuntu 7.10 does the same thing.

Exactly the same thing. It repeatedly asks for the key.

Looking at the logs it seems to do fine all the way up to the first use of dhclient where its calls for "wmaster0:" then shows "unknown hardware address 801". After that it just sits there on dhcpdiscovery until it times out.

Anyone?

OK after more wasting time there seems to be more and more of the exact same question popping up from all the various distros.

No DHclient assignment. I have everything I need for connect but just never get ip assignment through ifup/down on the wireless. The iwconfig shows the access point. Shows 54mbs rate, the essid is right as is the key. Everything is good just never shows getting a dhcp offer.

The error on - dhclient;wmaster ;unknown hardware address 801
is the only thing I see but I dont know what it exactly means and googling it comes up with the same unanswered questions I have.

Can you connect with router security turned off?

Cant turn security off on the router to find out. Or wont rather.

It doesn't seem to be as router problem as iwconfig shows the proper essid and encryption key as well as access point. Doesnt access point mean its getting feedback from the router ?


Does anyone know what the dhclient error (dhclient;wmaster ;unknown hardware address 801) pertains to? Is that a driver error? Or is that a dhclient error?

How can see where that, the dhclient error, is coming from or not going to?

You'll want to make sure that ndiswrapper and madwifi modules are not loaded at the same time. Madwifi is probably the best bet if it supports your chip set.

You could try setting a fixed IP address in your network interface config file and see if that will connect, just to try to narrow down the list of possible issues.

Is it possible that the router has additional security features enabled, such as MAC address filtering?

Can you post the output of iwconfig?