From: Johannes Berg <johannes@sipsolutions.net>
To: "John W. Linville" <linville@tuxdriver.com>
Cc: "Gábor Stefanik" <netrolller.3d@gmail.com>,
CalimeroTeknik <calimeroteknik@free.fr>,
linux-wireless@vger.kernel.org
Subject: Re: Wireless channel stuck to -1 on mon0 (fix patch submission)
Date: Tue, 21 Dec 2010 15:39:04 +0100 [thread overview]
Message-ID: <1292942344.3563.8.camel@jlt3.sipsolutions.net> (raw)
In-Reply-To: <20101220141134.GA10104@tuxdriver.com>
On Mon, 2010-12-20 at 09:11 -0500, John W. Linville wrote:
> On Sun, Dec 19, 2010 at 10:36:12PM +0100, Johannes Berg wrote:
> > On Sun, 2010-12-19 at 21:58 +0100, Gábor Stefanik wrote:
> > > This is a known problem, that has basically been WONTFIXed a while
> > > ago. I highly disagree with the reasoning, but the decision ultimately
> > > rests on Johannes. In the meantime, check patches.aircrack-ng.org for
> > > a workaround.
> > >
> > > Johannes: I know that you consider reporting the actual channel of the
> > > PHY to be "confusing to users" when running with multiple virtual
> > > PHYs, but apparently this is what most users expect. Perhaps it
> > > *should* be implemented after all.
> >
> > In which case it should be implemented properly, not half-baked like all
> > the patches we've seen so far.
>
> This does continue to pop-up. Do you have a link to a description
> of a proper implementation?
I don't think so -- I don't recall anyone ever asking before ;-)
FWIW, I think right now we need to simply query mac80211's oper_channel
somehow -- that'll be good enough until that goes away for real
multi-channel operation.
Using the channel that was set on the monitor interfaces like these
patches have done is obviously flawed because monitor interfaces have
absolutely no influence on the channel unless that's all there is.
johannes
prev parent reply other threads:[~2010-12-21 14:39 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-19 11:11 Wireless channel stuck to -1 on mon0 (fix patch submission) CalimeroTeknik
2010-12-19 20:58 ` Gábor Stefanik
2010-12-19 21:36 ` Johannes Berg
2010-12-20 14:11 ` John W. Linville
2010-12-21 14:39 ` Johannes Berg [this message]
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=1292942344.3563.8.camel@jlt3.sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=calimeroteknik@free.fr \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=netrolller.3d@gmail.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).