From: Dan Williams <dcbw@redhat.com>
To: pat-lkml <pat-lkml@erley.org>
Cc: 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 06:43:22 -0500 [thread overview]
Message-ID: <1236253402.31456.8.camel@localhost> (raw)
In-Reply-To: <49AF077D.2020408@erley.org>
On Wed, 2009-03-04 at 17:58 -0500, pat-lkml wrote:
> Alexey Yudichev wrote:
> >> On Wed, 4 Mar 2009 21:33:21 +0000
> >> Alexey Yudichev <ayudichev@yahoo.co.uk> wrote:
> >>> Hello,
> >>>
> >>> I've just joined the list so don't know how to join the same thread so
> >>> to indicate that it's the same matter I use the same subject. I am
> >>> trying to make my "04:01.0 Ethernet controller: Atheros Communications
> >>> Inc. Atheros AR5001X+ Wireless Network Adapter (rev 01)" which is
> >>> identified by ath5k as
> >>> [ 10.356742] ath5k phy0: Atheros AR5213A chip found (MAC: 0x59, PHY: 0x43)
> >>> [ 10.356748] ath5k phy0: RF5112B multiband radio found (0x36)
> >> I have the exact same card (AR5001X+) working in master mode with hostapd. What kernel version and hostapd version do you use?
> >
> > Hi, I use 2.6.27-11-generic (from ubuntu's
> > linux-backports-modules-intrepid-generic), hostapd v0.5.10.
>
> 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
next prev parent reply other threads:[~2009-03-05 11:45 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 [this message]
2009-03-05 19:09 ` pat-lkml
2009-03-05 19:12 ` Ben Greear
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=1236253402.31456.8.camel@localhost \
--to=dcbw@redhat.com \
--cc=ayudichev@yahoo.co.uk \
--cc=cjsthompson@gmail.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).