Historical ath9k-devel archives
 help / color / mirror / Atom feed
From: Benoit Papillault <benoit.papillault@free.fr>
To: ath9k-devel@lists.ath9k.org
Subject: [ath9k-devel] ad-hoc mode
Date: Wed, 05 May 2010 23:02:28 +0200	[thread overview]
Message-ID: <4BE1DCE4.1050204@free.fr> (raw)
In-Reply-To: <OF87DF353C.6418B5D9-ON8825771A.0062EFA4-8825771A.00636ACA@denso-diam.com>

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

  reply	other threads:[~2010-05-05 21:02 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-05-05  1:34 [ath9k-devel] ad-hoc mode LIGEO_GEORGE at denso-diam.com
2010-05-05 18:07 ` LIGEO_GEORGE at denso-diam.com
2010-05-05 21:02   ` Benoit Papillault [this message]
2010-05-05 21:24     ` LIGEO_GEORGE at denso-diam.com
2010-05-06  5:40       ` Benoit Papillault
  -- strict thread matches above, loose matches on Subject: below --
2014-07-07  0:21 mahaveer gupta

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4BE1DCE4.1050204@free.fr \
    --to=benoit.papillault@free.fr \
    --cc=ath9k-devel@lists.ath9k.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox