From: Luis Carlos Cobo <luisca@cozybit.com>
To: "Luis R. Rodriguez" <mcgrof@gmail.com>
Cc: Johannes Berg <johannes@sipsolutions.net>,
linux-wireless@vger.kernel.org,
"John W. Linville" <linville@tuxdriver.com>
Subject: Re: [PATCH 00/13] o11s: mesh interface support for mac80211
Date: Tue, 19 Feb 2008 14:26:52 -0800 [thread overview]
Message-ID: <1203460012.31736.38.camel@localhost> (raw)
In-Reply-To: <43e72e890802191359o5c6a869i559a4f6aeb686772@mail.gmail.com>
On Tue, 2008-02-19 at 16:59 -0500, Luis R. Rodriguez wrote:
> > Currently, bss are sorted by ssid, bssid and frequency.
>
> I wouldn't use "sort" here but instead "are made unique". As John has
Right, sorry for the imprecise use of the word.
> The key'ing of the BSSes based on BSSID/freq/SSID was just a to deal
> with an issue, how about we just detect if a beacon is from a mesh and
> if so add it to the list using another type of rule? Since we have no
> BSSID/SSID strange issue we don't have to apply that rule there.
Sounds good.
> > but the user chooses an ad-hoc network), change the type of the
> > interface and the proceed to connect. Am I right?
>
> Hopefully nothing will be added via wext, but instead nl80211/cfg80211.
Hopefully, but last time I checked (10 days ago) it looked like there
was no work in progress to implement scanning via nl80211.
--
Luis Carlos Cobo Rus GnuPG ID: 44019B60
cozybit Inc.
next prev parent reply other threads:[~2008-02-19 22:25 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-04 18:48 [PATCH 00/13] o11s: mesh interface support for mac80211 Luis Carlos Cobo
2008-02-07 0:13 ` Johannes Berg
2008-02-19 21:13 ` Luis Carlos Cobo
2008-02-19 21:39 ` Dan Williams
2008-02-19 21:59 ` Luis R. Rodriguez
2008-02-19 22:26 ` Luis Carlos Cobo [this message]
2008-02-20 23:42 ` 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=1203460012.31736.38.camel@localhost \
--to=luisca@cozybit.com \
--cc=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=mcgrof@gmail.com \
/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).