From: "Henry Ptasinski" <henryp@broadcom.com>
To: "Luis R. Rodriguez" <mcgrof@gmail.com>
Cc: linux-wireless <linux-wireless@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"openwireless@eff.org" <openwireless@eff.org>
Subject: Re: EFF's Open Wireless Movement - solutions for Linux 802.11 APs
Date: Fri, 29 Apr 2011 10:29:16 -0700 [thread overview]
Message-ID: <20110429172916.GA17775@broadcom.com> (raw)
In-Reply-To: <BANLkTinw9KJ5Awow5W6ASZ6ZWS6Hu7n7LA@mail.gmail.com>
On Thu, Apr 28, 2011 at 10:05:08AM -0700, Luis R. Rodriguez wrote:
> The EFF announced an effort and desire to promote open wireless
> networks instead of closed encrypted networks to help users with
> connectivity. They have come up with some alternative proposals and
> challenges which they are asking for review / help on. As far as Linux
> is concerned I've started a wiki [2] to cover what we can do for
> 802.11 Linux based APs. Feel free to extend the wiki as you see fit
> and / or subscribe for changes.
>
> [1] https://www.eff.org/deeplinks/2011/04/open-wireless-movement
> [2] http://wireless.kernel.org/en/developers/OpenWirelessMovement
The Wi-Fi Alliance currently has a Hotspot program in development:
http://www.wi-fi.org/news_articles.php?news_id=1048
While it's mainly targeted at service providers, it seem likely that much of
the work could be leveraged if you consider the "service provider" in this case
to be a loosly-coordinated group of people willing to make their APs available
for public use.
- Henry
next prev parent reply other threads:[~2011-04-29 17:29 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-28 17:05 EFF's Open Wireless Movement - solutions for Linux 802.11 APs Luis R. Rodriguez
2011-04-28 18:15 ` Larry Finger
2011-04-28 18:50 ` David Lynch Jr.
2011-04-29 10:50 ` Gábor Stefanik
2011-04-29 17:29 ` Henry Ptasinski [this message]
2011-07-27 21:57 ` Luis R. Rodriguez
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=20110429172916.GA17775@broadcom.com \
--to=henryp@broadcom.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=mcgrof@gmail.com \
--cc=openwireless@eff.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).