From: Vic O <bugtrack2@gmail.com>
To: linux-wireless@vger.kernel.org
Subject: Re: ath9k<-->ath9k ad-hoc does not associate
Date: Thu, 21 Jul 2011 21:49:35 +0000 (UTC) [thread overview]
Message-ID: <loom.20110721T233131-976@post.gmane.org> (raw)
In-Reply-To: 489C5B6C.4030108@ozo.com
>Alexandros C. Couloumbis <alex <at> ozo.com> writes:
> iwconfig, ifconfig & iwlist wlan0 scan from the wrap board:
>
> wlan0 IEEE 802.11abgn ESSID:"awmn"
> Mode:Ad-Hoc Frequency:5.745 GHz Cell: 0E:18:12:1E:75:73
> Tx-Power=23 dBm
> Retry min limit:7 RTS thr:off Fragment thr=2352 B
> Encryption key:off
> Power Management:off
> Link Quality:0 Signal level:0 Noise level:0
> Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
> Tx excessive retries:0 Invalid misc:0 Missed beacon:0
>
>
> iwconfig, ifconfig & iwlist wlan0 scan on the alix board:
>
> wlan0 IEEE 802.11abgn ESSID:"awmn"
> Mode:Ad-Hoc Frequency:5.745 GHz Cell: E6:FE:0E:A1:77:22
> Tx-Power=23 dBm
> Retry min limit:7 RTS thr:off Fragment thr=2352 B
> Encryption key:off
> Power Management:off
> Link Quality:0 Signal level:0 Noise level:0
> Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
> Tx excessive retries:0 Invalid misc:0 Missed beacon:0
>
>
This reply is almost a year in the making, but it looks like
your ad-hoc interfaces are creating new cells(new IBSS)
on initialization (you'll see that the 48-bit cell IDs are different).
Thus, even though they are on the same channel, same ESS ("awmn")
and within wireless range, they can't talk.
The 802.11 standards for IBSS (ad-hoc) mode specifies that
this problem should be solved by having the first interface to
establish a BSS periodically broadcasting a beacon so that newer
nodes get this beacon and associate to that cell.
However, for some reason ath9k doesn't handle this problem
correctly (ath5k did a good job with it).
In the meantime, you can specifically set the cell ID using
the iw command on all your interfaces (in this case the cell
ID is the 48-bit value made up of twos).
iw dev wlan0 ibss join "awmn" 5745 22:22:22:22:22:22
prev parent reply other threads:[~2011-07-21 21:55 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-08 14:42 ath9k<-->ath9k ad-hoc does not associate Alexandros C. Couloumbis
2011-07-21 21:49 ` Vic O [this message]
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=loom.20110721T233131-976@post.gmane.org \
--to=bugtrack2@gmail.com \
--cc=linux-wireless@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).