If this is your first visit, be sure to
check out the Forum Rules by clicking the
link above. You may have to register
before you can post: click the register link above to proceed. To start viewing messages,
select the forum that you want to visit from the selection below.

But unfortunately with ath5k, there is no wlanconfig. So how do I destroy the wlan0 interface? (With the ath5k driver, there is only wlan0 and wmaster0. I don't think wmaster0 does anything, as airmon-ng shows wlan0 as the main device, when with madwifi, airmon-ng showed wifi0 as the parent, and ath0 under it. I could destroy ath0 as I pleased, but not wifi0. With ath5k, only wlan0 is there, and I can't do anything to it and cannot create any Managed interfaces under it. wmaster doesn't seem to do anything.)

It times out at the dhclient and it says No DHCPOFFERS received, No working leases in persistent database - sleeping, blah blah. This same thing happened with the madwifi driver, which is why I had to use wlanconfig destroy to kill the interface, without making it go away, but more than just bringing it down (I had to destroy it). So after it failed to connect, at this point I had to either reload the ath5k module or take out/put back in my wireless card (both methods work fine) to reset the MAC address back to the original so I can dhclient again and it connects to the internet normally with the original MAC address, but if I use "macchanger --mac" to change the MAC address of wlan0 back to the original, it still won't connect. I have to use any of the two methods mentioned before (reloading module or replugging card) to make it work again.

Yea, that all works fine, but when I do "dhclient wlan0", it doesn't connect to my router. So I have to unplug my wireless card and plug it back in, and then I can connect to the internet again with "dhclient wlan0" but the MAC address is reset back to my original because I unplugged it.