From: Roger James <roger@beardandsandals.co.uk>
To: Johannes Berg <johannes@sipsolutions.net>,
linux-wireless@vger.kernel.org
Subject: Re: Reading the current monitor flags of an interface
Date: Tue, 5 Jan 2016 16:19:29 +0000 [thread overview]
Message-ID: <568BED11.50302@beardandsandals.co.uk> (raw)
In-Reply-To: <1452009755.12357.44.camel@sipsolutions.net>
On 05/01/16 16:02, Johannes Berg wrote:
> On Sat, 2016-01-02 at 16:27 +0000, Roger James wrote:
>> Hi,
>>
>> I am trying to get at the current monitor flags setting of a wireless
>> monitor mode virtual interface. I have tried to do this by hacking
>> the
>> iw source. However I never see a NL80211_ATTR_MNTR_FLAGS attribute
>> returned in response to the
>>
>> TOPLEVEL(info, NULL, NL80211_CMD_GET_INTERFACE, 0, CIB_NETDEV,
>> handle_interface_info,
>> "Show information for this interface.");
>>
>> command in iw's interface.c code.
>>
>> Questions.
>>
>> 1. Am I wasting my time? (e.g. the rt2800usb driver never returns
>> this
>> info, or there is another easy way of viewing this info, etc)
>>
> Looks like it's never set in the corresponding kernel code.
>
> johannes
> --
> To unsubscribe from this list: send the line "unsubscribe linux-wireless" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
Thanks Johannes, that was my conclusion, but I was not sure if that was
true in all cases. I tried another chipset and got the same results. I
am trying to debug a problem with an adapter only seeing broadcast and
multicast packets in monitor mode, and the significance of the setting
of the otherbss flag in this case. It would be really helpful if iw
could return the complete state of an interface, but it looks like that
would require a kernel patch. This seems like a can of worms to me.
Roger
next prev parent reply other threads:[~2016-01-05 16:19 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-02 16:27 Reading the current monitor flags of an interface Roger James
2016-01-05 16:02 ` Johannes Berg
2016-01-05 16:19 ` Roger James [this message]
2016-01-05 16:21 ` Johannes Berg
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=568BED11.50302@beardandsandals.co.uk \
--to=roger@beardandsandals.co.uk \
--cc=johannes@sipsolutions.net \
--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).