linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "John W. Linville" <linville@tuxdriver.com>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: "Hin-Tak Leung" <hintak.leung@gmail.com>,
	"Gábor Stefanik" <netrolller.3d@gmail.com>,
	"Stefan Steuerwald" <salsasepp@googlemail.com>,
	linux-wireless@vger.kernel.org
Subject: Re: Testing AP mode with WLAN-USB-Stick: How to obtain?
Date: Wed, 10 Jun 2009 07:31:59 -0400	[thread overview]
Message-ID: <20090610113158.GA2798@tuxdriver.com> (raw)
In-Reply-To: <1244619027.18481.55.camel@johannes.local>

On Wed, Jun 10, 2009 at 09:30:27AM +0200, Johannes Berg wrote:

> This means that your sleeping clients will not be receiving multicast,
> and as such be invisible to the network once they fall off the ARP/NDP
> caches. This is the reason we have said that it will not be possible to
> support AP mode with this card. I'm curious how, if at all, the vendor
> driver handles that.

My completely uninformed guess is that they ignore it.  I will hazard
a guess that most scenarios involving "laptop as AP" are for support
of devices that don't (or at least didn't) do a lot of sleeping,
like other laptops.

I'm still a bit "on the fence" regarding this requirement for AP mode.
I think there is a reasonable body of users that would prefer a
not-quite-right AP mode over no AP mode at all.

John
-- 
John W. Linville		Someday the world will need a hero, and you
linville@tuxdriver.com			might be all we have.  Be ready.

  reply	other threads:[~2009-06-10 11:45 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <f76a32050906081007q19e9361w8c1fad6fc73c47e7@mail.gmail.com>
2009-06-08 17:11 ` Testing AP mode with WLAN-USB-Stick: How to obtain? Stefan Steuerwald
2009-06-08 20:19   ` Chi-Thanh Christopher Nguyen
2009-06-08 23:59   ` Hin-Tak Leung
2009-06-09 11:26     ` Gábor Stefanik
2009-06-10  3:18       ` Hin-Tak Leung
2009-06-10  7:30         ` Johannes Berg
2009-06-10 11:31           ` John W. Linville [this message]
2009-06-10 19:19             ` Kalle Valo
2009-06-10 19:28               ` Jouni Malinen
2009-06-10 19:36                 ` Kalle Valo
2009-06-10 19:40                   ` Gábor Stefanik
2009-06-10 19:58                 ` John W. Linville
2009-06-10 19:55               ` John W. Linville
2009-06-10 13:39           ` Hin-Tak Leung
2009-06-10 15:22             ` Gábor Stefanik
2009-06-10 15:49               ` Johannes Berg
2009-06-10 15:51                 ` Johannes Berg
2009-06-10 19:28                 ` Kalle Valo
2009-06-11  3:08                 ` Hin-Tak Leung
2009-06-11  3:51                   ` Luis R. Rodriguez
2009-06-11  9:59                   ` Johannes Berg
2009-06-11 14:42                     ` Gábor Stefanik
2009-06-09  8:19   ` Jon Fairbairn
2009-06-09  9:16     ` Alexandre Becholey - s h o c k f i s h /
2009-06-11 14:58 Joerg Pommnitz
2009-06-11 15:06 ` Gábor Stefanik

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=20090610113158.GA2798@tuxdriver.com \
    --to=linville@tuxdriver.com \
    --cc=hintak.leung@gmail.com \
    --cc=johannes@sipsolutions.net \
    --cc=linux-wireless@vger.kernel.org \
    --cc=netrolller.3d@gmail.com \
    --cc=salsasepp@googlemail.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).