From mboxrd@z Thu Jan 1 00:00:00 1970 From: Benoit Papillault Date: Wed, 05 May 2010 23:02:28 +0200 Subject: [ath9k-devel] ad-hoc mode In-Reply-To: References: Message-ID: <4BE1DCE4.1050204@free.fr> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: ath9k-devel@lists.ath9k.org Le 05/05/2010 20:07, LIGEO_GEORGE at denso-diam.com 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