From: Henning Rogge <rogge@fgan.de>
To: linux-wireless@vger.kernel.org
Subject: Re: Virtual wireless network card for mac80211
Date: Wed, 14 Nov 2007 16:20:15 +0100 [thread overview]
Message-ID: <200711141620.15821.rogge@fgan.de> (raw)
In-Reply-To: <20071114150839.GA6226@tuxdriver.com>
Am Mittwoch 14 November 2007 16:08:39 schrieben Sie:
> On Wed, Nov 14, 2007 at 01:16:50PM +0100, Henning Rogge wrote:
> No, but I have been thinking about this as well. It might be a nice
> capability to have, so long as the regulatory spectre continues to
> discourage some vendors from disclosing information about their
> hardware. At least such a scenario seems less grey w.r.t. GPL
> compliance.
>
> Still, I would not want to put much effort into a project that
> distracts from development of fully open source drivers. But I think
> the performance of such a solution would be sub-optimal enough to
> discourage full reliance upon it. And the plus of having a userland
> binary driver versus no driver at all might make it worthwhile.
>
> What is the situation that makes this interesting to you?
I'm not interested in having a binary driver but in simulation of mobile
networks with virtual machines. By placing a virtual driver into the mac80211
layer the sollution would be totally transparent for the clients, even for
applications with Radiotap headers and Libpcap.
A central server would be connected to the userspace parts of the virtual
driver and simulate connections between the VMs.
Henning Rogge
next prev parent reply other threads:[~2007-11-14 15:20 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-14 12:16 Virtual wireless network card for mac80211 Henning Rogge
2007-11-14 15:08 ` John W. Linville
2007-11-14 15:20 ` Henning Rogge [this message]
2007-11-14 15:30 ` John W. Linville
2007-11-14 15:27 ` Johannes Berg
2007-11-14 15:22 ` Johannes Berg
2007-11-14 15:59 ` Mike Kershaw
2007-11-15 6:46 ` Henning Rogge
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=200711141620.15821.rogge@fgan.de \
--to=rogge@fgan.de \
--cc=linux-wireless@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 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.