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:21:31 +0200 [thread overview]
Message-ID: <200806261821.31643.mb@bu3sch.de> (raw)
In-Reply-To: <1214496086.30722.14.camel@dv>
On Thursday 26 June 2008 18:01:26 Pavel Roskin wrote:
> On Thu, 2008-06-26 at 17:46 +0200, Stefanik G=E1bor wrote:
>=20
> > Maybe we had more people working on/debugging AP mode if we didn't
> > intentionally disable the existing limited support for it... Possib=
ly
> > print a big warning that "THIS IS NOT STANDARDS_COMPLIANT YET!", bu=
t
> > outright disabling it and requiring an external patch is IMHO stupi=
d.
> > Perhaps a Kconfig option with EXPERIMENTAL and default=3Dn would be
> > better.
>=20
> I agree. More people would be looking into AP support for individual
> drivers if mac80211 didn't need a patch.
I'd also like to get something like the following merged:
Subject: mac80211: allow AP and VLAN modes
This patch is based on a patch by Johannes Berg.
It allows switching interfaces into AP/VLAN modes using
cfg80211 (nl80211). Don't allow doing it with wext because then
people will just attempt to do it manually (without hostapd) and
complain that it doesn't work.
Signed-off-by: Michael Buesch <mb@bu3sch.de>
Index: wireless-testing/net/mac80211/cfg.c
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
--- wireless-testing.orig/net/mac80211/cfg.c 2008-06-10 13:58:23.000000=
000 +0200
+++ wireless-testing/net/mac80211/cfg.c 2008-06-26 18:12:31.000000000 +=
0200
@@ -33,6 +33,12 @@ nl80211_type_to_mac80211_type(enum nl802
case NL80211_IFTYPE_MESH_POINT:
return IEEE80211_IF_TYPE_MESH_POINT;
#endif
+#ifdef CONFIG_MAC80211_AP
+ case NL80211_IFTYPE_AP:
+ return IEEE80211_IF_TYPE_AP;
+ case NL80211_IFTYPE_AP_VLAN:
+ return IEEE80211_IF_TYPE_VLAN;
+#endif /* AP */
case NL80211_IFTYPE_WDS:
return IEEE80211_IF_TYPE_WDS;
default:
Index: wireless-testing/net/mac80211/Kconfig
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
--- wireless-testing.orig/net/mac80211/Kconfig 2008-06-10 13:58:23.0000=
00000 +0200
+++ wireless-testing/net/mac80211/Kconfig 2008-06-26 18:19:13.000000000=
+0200
@@ -92,6 +92,25 @@ config MAC80211_LEDS
This option enables a few LED triggers for different
packet receive/transmit events.
=20
+config MAC80211_AP
+ bool "AccessPoint and VLAN modes (read help text!)"
+ depends on MAC80211 && EXPERIMENTAL
+ ---help---
+ =3D=3D=3D> BIG FAT WARNING <=3D=3D=3D
+ 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.
+
+ This option enables AP/VLAN support in mac80211.
+ Note that the latest GIT snapshot of the userspace hostapd
+ daemon is required for this. It will not work without
+ hostapd or with an old version of hostapd without nl80211 support.
+
+ Say N.
+
config MAC80211_DEBUGFS
bool "Export mac80211 internals in DebugFS"
depends on MAC80211 && DEBUG_FS
--=20
Greetings Michael.
--
To unsubscribe from this list: send the line "unsubscribe linux-wireles=
s" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2008-06-26 16:22 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 [this message]
2008-06-26 16:34 ` Pavel Roskin
2008-06-26 16:46 ` Michael Buesch
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=200806261821.31643.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.