Ok. Thanks. I will try that. Reading an earlier post, https://lists.ath9k.org/pipermail/ath9k-devel/2009-November/002670.html , I thought there was a problem with IBSS mode, but maybe its fixed now or I probably have an older driver..
To reiterate an earlier question, does the current driver in git support 11N in ad-hoc mode? I haven't been able to figure out the current status of 11N + IBSS development from the mailing list. Please let me know. Thanks! - Lig [email protected] wrote on 05/05/2010 02:02:28 PM: > Le 05/05/2010 20:07, [email protected] a écrit : > > > > After going through older posts - I found this one > > https://lists.ath9k.org/pipermail/ath9k-devel/2009-December/002808.html > > > > I use the config script in that post and can get the ad-hoc mode to work > > - the main reason why I think it didn't work earlier for me was that I > > didn't specify the fixed BSSID/cell number at both ends. > > > > But, I observe the exact same behavior as reported by the post - if I > > change the frequency to 2412, pings stop working in ad-hoc mode. Even if > > I re-insert the ath9k, it seem like the new frequency I set (2412) > > doesn't work. If I go back to the 5200 frequency after re-inserting > > ath9k module, pings start working again. Again, like the post stated, > > when I set 2412 using iw, I still see the old 5200 frequency in iwconfig. > > > > hm... > > You don't need to use a fixed frequency, nor fixed BSSID. Just use : > > iw dev wlan0 ibss join YourSSIID YourFrequency > > YourFrequency is only used if scanning did not find a neighbor node. > > Regards, > Benoit > _______________________________________________ > ath9k-devel mailing list > [email protected] > https://lists.ath9k.org/mailman/listinfo/ath9k-devel
_______________________________________________ ath9k-devel mailing list [email protected] https://lists.ath9k.org/mailman/listinfo/ath9k-devel
