From: Bodo Eggert <harvested.in.lkml@7eggert.dyndns.org>
To: Michael Buesch <mbuesch@freenet.de>,
jgarzik@pobox.com, bcm43xx-dev@lists.berlios.de,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [Bcm43xx-dev] [Fwd: State of the Union: Wireless]
Date: Fri, 06 Jan 2006 23:57:59 +0100 [thread overview]
Message-ID: <E1Ev0X3-0000tX-4l@be1.lrz> (raw)
In-Reply-To: <5rXDU-5s4-5@gated-at.bofh.it>
Michael Buesch <mbuesch@freenet.de> wrote:
> How would the virtual interfaces look like? That is quite easy to answer.
> They are net_devices, as they transfer data.
> They should probaly _not_ be on top of the ethernet, as 80211 does not
> have very much in common with ethernet. Basically they share the same
> MAC address format. Does someone have another thing, which he thinks
> is shared?
<brainstorming>
It has a connection status.
It has a connection speed, which is less static than on a LAN.
(Maybe it can be asynchronous in the next version.)
It can't yet be full duplex, but who knows ...
It can be in promiscious mode (wardriving).
> The virtual interface is then configured though /dev/wlan0 using write()
> (no ugly ioctl anymore, you see...). Config data like TX rate,
> current essid,.... basically everything + xyz which is done by WE today,
> is written to /dev/wlan0.
In ASCII parsed by an in-kernel library? Did you consider sysfs?
What would a connection manager look for if it's supposed to act on
* plugging in the WLAN card
* finding/losing a (better) network
--
Ich danke GMX dafür, die Verwendung meiner Adressen mittels per SPF
verbreiteten Lügen zu sabotieren.
next parent reply other threads:[~2006-01-06 22:54 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <5rXDU-5s4-7@gated-at.bofh.it>
[not found] ` <5rXDU-5s4-5@gated-at.bofh.it>
2006-01-06 22:57 ` Bodo Eggert [this message]
[not found] <1136541243.4037.18.camel@localhost>
2006-01-06 11:00 ` Michael Buesch
2006-01-06 11:38 ` Marcel Holtmann
2006-01-06 11:45 ` Michael Buesch
2006-01-06 12:10 ` Marcel Holtmann
2006-01-06 12:46 ` Patrick McHardy
2006-01-06 18:23 ` Stephen Hemminger
2006-01-06 22:16 ` David Lang
2006-01-06 22:18 ` David S. Miller
2006-01-09 18:24 ` Ingo Oeser
2006-01-06 22:22 ` Patrick McHardy
2006-01-12 14:20 ` Harald Welte
2006-01-06 16:12 ` Feyd
2006-01-06 16:25 ` Johannes Berg
2006-01-06 17:02 ` 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=E1Ev0X3-0000tX-4l@be1.lrz \
--to=harvested.in.lkml@7eggert.dyndns.org \
--cc=7eggert@gmx.de \
--cc=bcm43xx-dev@lists.berlios.de \
--cc=jgarzik@pobox.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mbuesch@freenet.de \
--cc=netdev@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®