Bob Copeland wrote:
> On Fri, Nov 21, 2008 at 11:45:18PM +0200, Maxim Levitsky wrote:
>>> I double check that I use right kernel (install it again).
>> compiled kernel again, and installed it, same results.
> 
> Can you confirm that the proper mac address shows up if you do ifconfig
> or macchanger -s?  I think it's just not associating.  
> 
> Also can you try specifying the ap again to trigger a probe after 
> ifconfig up:
> 
>     $ iwconfig wlan0 ap <your AP's mac address>
> 
> Though I did forget about this gem, try this too:

Mystery solved, and sorry for the noise,
short answer is, wpa_supplicant.

My network is WPA2 protected, and I only test against it, and
it takes time to go to AP settings, change encryption to WEP, and not forget
to change it back, etc...

So, wpa_supplicant wasn't aware of new mac, but I remember that WPA uses mac as 
part
of encryption.

restarting it solved the problem.

I also applied (by hand) your latest patch, so maybe it did help, I'll check 
without it too.


Best regards,
        Maxim Levitsky


_______________________________________________
ath5k-devel mailing list
[email protected]
https://lists.ath5k.org/mailman/listinfo/ath5k-devel

Reply via email to