linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ben Greear <greearb@candelatech.com>
To: pat-lkml@erley.org
Cc: Dan Williams <dcbw@redhat.com>,
	Alexey Yudichev <ayudichev@yahoo.co.uk>,
	"Christoph .J Thompson" <cjsthompson@gmail.com>,
	linux-wireless@vger.kernel.org
Subject: Re: ath5k master (AP) mode
Date: Thu, 05 Mar 2009 11:12:37 -0800	[thread overview]
Message-ID: <49B02425.5030005@candelatech.com> (raw)
In-Reply-To: <041a41424b1a9851b471a7a3b794dc47@127.0.0.1>

pat-lkml@erley.org wrote:

>>> I don't know if it's intended, or just not implemented, but iwconfig
>>> <iface> mode master
>>> won't work with mac80211 drivers.  Hostapd knows how to set master mode
>>> on it's own.
>> Hostapd needs to be used for master mode in *any* case.  So yes, its
>> intended that you need hostapd for master mode with mac80211 drivers.
>> Just switching the card to master mode simply won't work, because
>> there's oh-so-much-more setup required in addition to that, which
>> hostapd knows how to do.
>>
>> Dan
> 
> Thanks for confirming this.  It was what I understood to be the case, 
> and what experimentation had shown, but I was not sure if it was by 
> design, or just not implemented yet.

Seems like iwconfig should have a more useful error message,
telling users to use hostapd for this particular driver,
instead of just a generic error...

Ben

-- 
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc  http://www.candelatech.com


  reply	other threads:[~2009-03-05 19:13 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <4dd58f490903041329p54ec56ceh1b64ab000027eac5@mail.gmail.com>
2009-03-04 21:33 ` ath5k master (AP) mode Alexey Yudichev
2009-03-04 22:26   ` Christoph .J Thompson
2009-03-04 22:51     ` Alexey Yudichev
2009-03-04 22:25       ` Christoph J. Thompson
2009-03-05 22:49         ` Alexey Yudichev
2009-03-06  7:45           ` Christoph J. Thompson
2009-03-10 21:04             ` Alexey Yudichev
2009-03-10 21:37               ` Christoph .J Thompson
2009-03-10 21:58                 ` Bob Copeland
2009-03-11 21:51                   ` Alexey Yudichev
     [not found]                     ` <4dd58f490905310754g2f01b083sd35831747ff93d4f@mail.gmail.com>
2009-05-31 14:56                       ` Alexey Yudichev
2009-03-04 22:58       ` pat-lkml
2009-03-05 11:43         ` Dan Williams
2009-03-05 19:09           ` pat-lkml
2009-03-05 19:12             ` Ben Greear [this message]
2009-03-05 22:21               ` Gábor Stefanik
2009-02-13 21:28 Jeff Tchang
  -- strict thread matches above, loose matches on Subject: below --
2009-02-11 18:47 Norman Rieß
2009-02-11 21:04 ` Bob Copeland
2009-02-11 22:34   ` pat-lkml
2009-02-12  9:12   ` Norman Rieß
2008-11-12 21:48 RUMI Szabolcs
2008-11-12 22:46 ` Pavel Roskin
2008-11-12 23:46   ` RUMI Szabolcs
2008-11-13 17:11     ` RUMI Szabolcs
2008-11-13 17:49       ` Johannes Berg
2008-11-13 22:59         ` RUMI Szabolcs
2008-11-13 23:03           ` Johannes Berg
2008-11-13 23:07           ` Nick Kossifidis
2008-11-14 10:15             ` RUMI Szabolcs
2009-02-10 12:14               ` RUMI Szabolcs
2009-02-11 21:49                 ` Nick Kossifidis
2009-02-12  2:11                   ` Ben Greear

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=49B02425.5030005@candelatech.com \
    --to=greearb@candelatech.com \
    --cc=ayudichev@yahoo.co.uk \
    --cc=cjsthompson@gmail.com \
    --cc=dcbw@redhat.com \
    --cc=linux-wireless@vger.kernel.org \
    --cc=pat-lkml@erley.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).