From: Ulrich Kunitz <kune@deine-taler.de>
To: Andy Green <andy@warmcat.com>
Cc: Johannes Berg <johannes@sipsolutions.net>,
Jon Smirl <jonsmirl@gmail.com>, Daniel Drake <dsd@gentoo.org>,
linux-wireless@vger.kernel.org,
John Linville <linville@tuxdriver.com>
Subject: Re: Arrested Development
Date: Mon, 9 Jul 2007 00:38:29 +0200 [thread overview]
Message-ID: <20070708223829.GA18217@deine-taler.de> (raw)
In-Reply-To: <46915B3C.6030609@warmcat.com>
On 07-07-08 22:46 Andy Green wrote:
> > This isn't going to work properly when you add a sta interface and then
> > a monitor interface, which afaict the driver doesn't prevent in
> > zd_mac_open. Basically, it has the phy always follow the last-added
> > virtual interface which doesn't seem right. Also, I might be missing
> > something, but it shouldn't allow multiple sta interfaces, afaict it
> > does now.
>
> This is a bit of a general issue that has been discussed a couple of
> times, not really to a resolution: how to deal with conflicting demands
> of multiple interfaces on the same rx hardware. I guess it wants it to
> be that if any interface is in Monitor then the hardware promisc is
> enabled. IFF_PROMISC was discussed to be another way to select genuine
> promisc rx as well.
> FWIW my script looks like this:
>
> modprobe -r zd1211rw-mac80211
> modprobe -r rc80211_simple
> modprobe -r mac80211
> modprobe zd1211rw-mac80211
> sleep 2s
> ifconfig wlan0 up
> echo -n mon0 >/sys/class/ieee80211/phy0/add_iface
> iwconfig mon0 mode monitor
> iwconfig mon0 channel 6
> ifconfig mon0 up
I forgot to mention that the monitor support doesn't work with
additonal interfaces right now. Additional interfaces are broken
currently for zd1211rw. I cannot fix all the problems with
mac80211 interface of the driver at the same time.
Try
iwconfig wlan0 mode monitor
ifconfig wlan0 up
iwconfig wlan0 channel 6
for now.
The problem with the STA + MNTR interface is, that mac80211 must
do the FCS checking for the STA interface or the driver has to
filter them before forwarding them to the upper layer.
--
Uli Kunitz
next prev parent reply other threads:[~2007-07-08 22:38 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-06 6:52 Arrested Development Andy Green
2007-07-06 11:07 ` Johannes Berg
2007-07-06 13:46 ` Daniel Drake
2007-07-06 13:50 ` Daniel Drake
2007-07-06 15:13 ` Andy Green
2007-07-08 14:00 ` Ulrich Kunitz
2007-07-08 16:22 ` Andy Green
2007-07-08 18:15 ` Ulrich Kunitz
2007-07-08 18:18 ` Michael Buesch
2007-07-08 18:29 ` Andy Green
2007-07-08 19:08 ` Johannes Berg
2007-07-09 0:40 ` Daniel Drake
2007-07-09 5:15 ` Johannes Berg
2007-07-08 18:42 ` Jon Smirl
2007-07-08 18:46 ` Andy Green
2007-07-08 19:04 ` Jon Smirl
2007-07-08 19:17 ` Andy Green
2007-07-08 20:37 ` Ulrich Kunitz
2007-07-08 21:23 ` Johannes Berg
2007-07-08 21:46 ` Andy Green
2007-07-08 22:38 ` Ulrich Kunitz [this message]
2007-07-08 22:55 ` Michael Buesch
2007-07-09 5:57 ` Uli Kunitz
2007-07-09 5:29 ` Andy Green
2007-07-08 22:44 ` Michael Wu
2007-07-09 5:15 ` Johannes Berg
2007-07-09 5:32 ` 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=20070708223829.GA18217@deine-taler.de \
--to=kune@deine-taler.de \
--cc=andy@warmcat.com \
--cc=dsd@gentoo.org \
--cc=johannes@sipsolutions.net \
--cc=jonsmirl@gmail.com \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
/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).