All of lore.kernel.org
 help / color / mirror / Atom feed
* Advice about otherbss monitor flag for Wireshark use
@ 2016-01-13  7:58 Mikael Kanstrup
  2016-01-13  8:24 ` Johannes Berg
  0 siblings, 1 reply; 2+ messages in thread
From: Mikael Kanstrup @ 2016-01-13  7:58 UTC (permalink / raw)
  To: linux-wireless

Hi,

Roger James reported that capturing wireless data on monitor
interfaces created by Wireshark only capture frames to/from BSSID of
the monitor interface. This was solved using iw by setting otherbss
monitor flag. See Wireshark mailing list thread here:
https://www.wireshark.org/lists/wireshark-dev/201601/msg00031.html

I suggested a patch to handle this within Wireshark:
https://code.wireshark.org/review/#/c/13219

Now before merging I hope to get some feedback here if this is safe
for the general case? For most users/drivers it appears explicitly
setting the flag is not needed.

/Mikael

^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2016-01-13  8:24 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2016-01-13  7:58 Advice about otherbss monitor flag for Wireshark use Mikael Kanstrup
2016-01-13  8:24 ` Johannes Berg

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.