All of lore.kernel.org
 help / color / mirror / Atom feed
From: Michael Buesch <mb@bu3sch.de>
To: Pavel Roskin <proski@gnu.org>
Cc: "Stefanik Gábor" <netrolller.3d@gmail.com>,
	"Johannes Berg" <johannes@sipsolutions.net>,
	cs010101@gmail.com, linux-wireless@vger.kernel.org,
	"John Linville" <linville@tuxdriver.com>
Subject: Re: [Q] ath5k : doesn't support AP mode?
Date: Thu, 26 Jun 2008 18:46:17 +0200	[thread overview]
Message-ID: <200806261846.17962.mb@bu3sch.de> (raw)
In-Reply-To: <1214498071.30722.22.camel@dv>

On Thursday 26 June 2008 18:34:31 Pavel Roskin wrote:
> On Thu, 2008-06-26 at 18:21 +0200, Michael Buesch wrote:
> > +	  ===> BIG FAT WARNING <===
> > +	  This is not IEEE 802.11 compliant, yet!
> > +	  You might disturb operation of other accesspoints and
> > +	  stations in your neighbourhood. Do only enable this, if
> > +	  you want to help out fixing this to make this warning disappear.
> > +	  If you enable this, expect that your neighbour will ring your
> > +	  door and yell at you for disturbing his network.
> 
> Gladly there will be no black helicopters :-)

Oh right. I forgot these :)

> But is it really so bad?

Well no. But I think we should try hard to make users not use this, yet.
Something that is not IEEE 802.11 compliant is not what everybody should use.
There's enough noise in the air that disturbs wireless. I don't want
to have yet another neighbour installing yet another broken thing. ;)

> What's the current TODO list for the AP mode?

I think there are some issues with the rates.
Maybe more. I don't really know.
I was going to look into this, but I was pushed back a little bit
by some hardware and software defects. I probably need to get new
hardware first.

-- 
Greetings Michael.

  reply	other threads:[~2008-06-26 17:42 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-26  2:54 [Q] ath5k : doesn't support AP mode? 김영환
2008-06-26  2:57 ` Pavel Roskin
2008-06-26 13:33   ` Johannes Berg
2008-06-26 14:57     ` Pavel Roskin
2008-06-26 15:46       ` Stefanik Gábor
2008-06-26 16:01         ` Pavel Roskin
2008-06-26 16:21           ` Michael Buesch
2008-06-26 16:34             ` Pavel Roskin
2008-06-26 16:46               ` Michael Buesch [this message]
2008-06-26 17:23                 ` Johannes Berg
2008-06-26 18:03                   ` Pavel Roskin
2008-06-26 18:08                     ` Johannes Berg
2008-06-26 18:18                       ` Pavel Roskin
2008-06-26 18:21                         ` Johannes Berg
2008-06-26 18:27                           ` Johannes Berg
2008-06-26 18:36                             ` Pavel Roskin
2008-06-26 18:37                               ` Johannes Berg
2008-06-26 18:22                         ` Michael Buesch
2008-06-26 17:36             ` John W. Linville
2008-06-26 18:08               ` Pavel Roskin
2008-06-26 18:08               ` Michael Buesch
2008-06-26 17:24           ` Johannes Berg
2008-06-26 17:27           ` Johannes Berg
2008-06-26 18:09             ` Stefanik Gábor
2008-06-26 18:20               ` Johannes Berg
2008-06-26 18:34                 ` Stefanik Gábor
2008-06-26 18:36                   ` 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=200806261846.17962.mb@bu3sch.de \
    --to=mb@bu3sch.de \
    --cc=cs010101@gmail.com \
    --cc=johannes@sipsolutions.net \
    --cc=linux-wireless@vger.kernel.org \
    --cc=linville@tuxdriver.com \
    --cc=netrolller.3d@gmail.com \
    --cc=proski@gnu.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.