From: Johannes Berg <johannes@sipsolutions.net>
To: Vladimir Koutny <vlado@work.ksp.sk>
Cc: Pavel Roskin <proski@gnu.org>, Mark Ryden <markryde@gmail.com>,
linux-wireless@vger.kernel.org
Subject: Re: AP (Master Mode) of wireless drivers
Date: Wed, 26 Nov 2008 11:03:13 +0100 [thread overview]
Message-ID: <1227693793.4613.57.camel@johannes.berg> (raw)
In-Reply-To: <492D0A26.9090801@work.ksp.sk> (sfid-20081126_100034_138731_1E1B1C2B)
[-- Attachment #1: Type: text/plain, Size: 966 bytes --]
On Wed, 2008-11-26 at 09:34 +0100, Vladimir Koutny wrote:
> >> More specifically, I am particularly interested to know whether Intel
> >> iwl3945 and Intel iwl4965 support AP (Master Mode), and in case they
> >> do not (as I am afraid is the situation)
> >> - is there any intention to add AP (masted mode) support to these drivers
> >> in the near future ?
> >
> > The driver announces AP mode support (look for NL80211_IFTYPE_AP and
> > hw->wiphy->interface_modes in iwl-core.c and iwl3945-base.c), so it
> > might work, or at least the intention is to make it work. By the way,
> > rt2x00 announces AP mode support too (in some conditions).
>
> I've tested AP mode on iwl4965 about 2 weeks ago and a very quick test did
> work (no encryption, just connected a win notebook to it and did some
> browsing). Just be sure to fetch correct (=recent) versions of hostapd and
> libnl..
I don't think it'll do mcast buffering correctly.
johannes
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2008-11-26 11:21 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-25 15:35 AP (Master Mode) of wireless drivers Mark Ryden
2008-11-25 17:16 ` Pavel Roskin
2008-11-26 8:34 ` Vladimir Koutny
2008-11-26 10:03 ` Johannes Berg [this message]
2008-11-26 13:47 ` Mark Ryden
2008-11-26 13:58 ` Johannes Berg
2008-11-26 14:02 ` Mark Ryden
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=1227693793.4613.57.camel@johannes.berg \
--to=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=markryde@gmail.com \
--cc=proski@gnu.org \
--cc=vlado@work.ksp.sk \
/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