From: "Alina Friedrichsen" <x-alina@gmx.net>
To: Sujith <Sujith.Manoharan@atheros.com>, linux-wireless@vger.kernel.org
Subject: Re: IBSS issues
Date: Fri, 27 Feb 2009 09:25:45 +0100 [thread overview]
Message-ID: <20090227082545.291220@gmx.net> (raw)
In-Reply-To: <18855.26210.618690.891378@gargle.gargle.HOWL>
Hi Sujith!
> I am seeing some strange behavior in IBSS mode with current
> wireless-testing.
>=20
> Scenario:
>=20
> * Create a new cell using ath9k.
> * Wait for a while to do a background merge scan run.
> * Join the cell from another peer ( say, using ath5k ).
> * Station dump in peer1 1 doesn't show the new peer right away.
> * The merge runs are not supposed to happen if a cell has more than =
one
> peer.
> It didn't happen before, but it keeps running repeatedly now.
> * Ping from peer2 to peer1 doesn't go through - peer1 to peer2 works
> though.
The strange thing is after the ping from peer1 to peer2, the ping from =
peer2 to peer1 works too. The same is if I start tcpdump on peer1. Afte=
r stopping tcpdump it keeps working. Looking...
> I identified one bug, where the timestamp in the beacon template was =
not
> updated.
> Patch below. But it doesn't fix the issue.
The TSF of the beacon is setted by the hardware automatically, so to wr=
ite it in the template is not needed.
Regards
Alina
--=20
Psssst! Schon vom neuen GMX MultiMessenger geh=F6rt? Der kann`s mit all=
en: http://www.gmx.net/de/go/multimessenger01
--
To unsubscribe from this list: send the line "unsubscribe linux-wireles=
s" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2009-02-27 8:25 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-27 4:04 IBSS issues Sujith
2009-02-27 8:25 ` Alina Friedrichsen [this message]
2009-02-27 8:44 ` Sujith
2009-02-27 9:53 ` Alina Friedrichsen
2009-02-27 10:14 ` Sujith
2009-02-27 10:56 ` Alina Friedrichsen
2009-02-27 9:01 ` Alina Friedrichsen
2009-02-27 9:24 ` Sujith
2009-02-27 10:19 ` Alina Friedrichsen
2009-02-27 10:32 ` Sujith
2009-02-27 11:02 ` Alina Friedrichsen
2009-02-27 21:53 ` Johannes Berg
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=20090227082545.291220@gmx.net \
--to=x-alina@gmx.net \
--cc=Sujith.Manoharan@atheros.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 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.