From: Bob Copeland <me@bobcopeland.com>
To: Derek Smithies <derek@indranet.co.nz>
Cc: Jonathan Guerin <jonathan@guerin.id.au>,
"Ath5k Devel issues." <ath5k-devel@lists.ath5k.org>,
linux-wireless@vger.kernel.org
Subject: Re: [ath5k-devel] ath5k Ad Hoc Association
Date: Tue, 20 Jul 2010 19:16:29 -0400 [thread overview]
Message-ID: <20100720231629.GC7049@hash.localnet> (raw)
In-Reply-To: <alpine.DEB.2.00.1007211002410.21858@kauri.acheron.indranet.co.nz>
On Wed, Jul 21, 2010 at 10:11:14AM +1200, Derek Smithies wrote:
>> Then on the other machine (Vista) I just located 'myibss' (so beacons
>> are working) and selected it, then successfully pinged 192.168.10.1.
> Wrong.
> If the other machine located your node, then one of the four statements
> is true:
Ok, fine, I just set up a monitor interface and I see beacons
(and probe responses) for my setup on that channel.
> A scan should not be necessary - if both ends are put on channel 2462- a
> scan should not be required - there is no channel changing. Yet - my
> colleague noted a scan helped nodes to associate.
There was a bug in older kernels that wouldn't fully configure the
beacons until after a reset, which scanning happens to do. It's
possible something similar is going on.
Also, scanning might open a previously passive channel because we might
get lucky and receive a beacon from another node on it. The 'iw phy
phy0 info' can show this kind of thing.
--
Bob Copeland %% www.bobcopeland.com
next prev parent reply other threads:[~2010-07-20 23:16 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-19 4:35 ath5k Ad Hoc Association Jonathan Guerin
2010-07-19 19:22 ` Bob Copeland
2010-07-20 6:39 ` Jonathan Guerin
2010-07-20 6:59 ` Jonathan Guerin
2010-07-20 11:20 ` Bob Copeland
2010-07-21 1:16 ` Jonathan Guerin
2010-07-21 5:47 ` Jonathan Guerin
2010-07-20 11:50 ` Holger Schurig
2010-07-20 12:05 ` Jonathan Guerin
2010-07-20 22:11 ` [ath5k-devel] " Derek Smithies
2010-07-20 22:54 ` Jonathan Guerin
2010-07-20 23:16 ` Bob Copeland [this message]
2010-07-21 0:00 ` Jonathan Guerin
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=20100720231629.GC7049@hash.localnet \
--to=me@bobcopeland.com \
--cc=ath5k-devel@lists.ath5k.org \
--cc=derek@indranet.co.nz \
--cc=jonathan@guerin.id.au \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.