From: Jean Tourrilhes <jt@bougret.hpl.hp.com>
To: Linux kernel mailing list <linux-kernel@vger.kernel.org>,
Linux Net mailing list <linux-net@vger.kernel.org>
Subject: Re: Wireless Network Maintainer?
Date: Thu, 9 Oct 2003 17:55:48 -0700 [thread overview]
Message-ID: <20031010005548.GA3573@bougret.hpl.hp.com> (raw)
Nico Schottelius wrote :
>
> Is there _anyone_ responsable for the wireless (802.11*) drivers in the
> Linux kernel?
Yes, the individual driver authors. Either check the names in
the source code or check my Howto.
> - easy interface = support for wireless tools
Can't agree me, but I'm biased. This is slowly improving.
> - compatibility with 2.5/2.6 modul interface
Wireless drivers included in kernel 2.6.X are already compatible.
> - support for AP-Master/AP/Ad-Hoc/Monitor Modus (like HostAP can do)
There is two aspect there.
First, I want the HostAP driver to be included in 2.6.X, and
I'm trying to make this happen.
Second, Master and Monitor mode can be implemented only in
drivers for which the necessary hardware documentation is available,
which means only a subset of them.
> - device naming scheme should be wlanX -> easier to see what it is
There are pros and cons to that. Personally I prefer the
approach taken by the aironet driver (ethX + wifiX). The interface the
driver present to the kernel is *really* an Ethernet interface.
If you really want easy identification, we could take the *BSD
approach where every driver use it's own unique device name.
> - support for external encryption (kernel modules/user space) like WLSec
Let's not reinvent the wheel again. What's wrong with IPsec ?
If you want to go that route, at least follow one of the upcomming
standard (802.1x, WPA, ...).
Jean
next reply other threads:[~2003-10-10 0:56 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-10 0:55 Jean Tourrilhes [this message]
2003-10-10 20:27 ` Toon van der Pas
-- strict thread matches above, loose matches on Subject: below --
2003-10-09 21:48 Nico Schottelius
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=20031010005548.GA3573@bougret.hpl.hp.com \
--to=jt@bougret.hpl.hp.com \
--cc=jt@hpl.hp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-net@vger.kernel.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
all inboxes | Powered by JetHome®