linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Andy Green <andy@warmcat.com>
To: Ulrich Kunitz <kune@deine-taler.de>
Cc: linux-wireless <linux-wireless@vger.kernel.org>,
	Daniel Drake <dsd@gentoo.org>
Subject: Re: mac80211 driver interface semantics
Date: Fri, 03 Aug 2007 08:59:43 +0100	[thread overview]
Message-ID: <46B2E06F.4090706@warmcat.com> (raw)
In-Reply-To: <20070803052935.GA12683@deine-taler.de>

Somebody in the thread at some point said:

> As far as I know the phy0/add_iface entry can be used to add a new
> interface. Notify though the "file" has write access for other,
> you will need network admin capabilities, which is satisfied by
> being root. For example:
> 
> # cat mon0 >/sys/class/net/wmaster0/phy80211/add_iface

echo -n mon0 ... ;-)

you can also come at this through

/sys/class/ieee80211/phy<n>/add_iface

Nice idea to document it Daniel.  Seeing it written down makes it a
little more obviously "huh?" about the hard and soft monitor distinction
IMO.  There seems to be some agreement that in the future the number of
virtual interfaces that happen to be lying around shouldn't determine
the functionality of Monitor mode like that.

-Andy

  reply	other threads:[~2007-08-03  7:59 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-08-03  0:30 mac80211 driver interface semantics Daniel Drake
2007-08-03  5:29 ` Ulrich Kunitz
2007-08-03  7:59   ` Andy Green [this message]
2007-08-03  9:54     ` Johannes Berg
2007-08-03 10:20       ` Joerg Mayer
2007-08-03 10:27       ` Andy Green
2007-08-03 10:32         ` Johannes Berg
2007-08-03 10:35           ` Andy Green
2007-08-03 10:41             ` Johannes Berg
2007-08-03 10:49               ` Andy Green
2007-08-06  6:44                 ` Johannes Berg
2007-08-06  8:25                   ` Andy Green

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=46B2E06F.4090706@warmcat.com \
    --to=andy@warmcat.com \
    --cc=dsd@gentoo.org \
    --cc=kune@deine-taler.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).