Huge thanks to our Platinum Members Endace and LiveAction,
and our Silver Member Veeam, for supporting the Wireshark Foundation and project.

Wireshark-bugs: [Wireshark-bugs] [Bug 11834] New: Restart current capture fails with "no interfa

Date: Mon, 30 Nov 2015 22:40:16 +0000
Bug ID 11834
Summary Restart current capture fails with "no interface selected" error when capturing in promiscuous mode
Product Wireshark
Version Git
Hardware x86
OS Ubuntu
Status UNCONFIRMED
Severity Normal
Priority Low
Component Qt UI
Assignee [email protected]
Reporter [email protected]

Build Information:
Version 2.1.0 (v2.1.0rc0-865-g0160397 from master)

Copyright 1998-2015 Gerald Combs <[email protected]> and contributors.
License GPLv2+: GNU GPL version 2 or later
<http://www.gnu.org/licenses/old-licenses/gpl-2.0.html>
This is free software; see the source for copying conditions. There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.

Compiled (64-bit) with Qt 4.8.1, with libpcap, with POSIX capabilities (Linux),
with libnl 3, with libz 1.2.3.4, with GLib 2.32.4, with SMI 0.4.8, with c-ares
1.7.5, with Lua 5.2, with GnuTLS 2.12.14, with Gcrypt 1.5.0, with MIT Kerberos,
with GeoIP, without QtMultimedia, without AirPcap.

Running on Linux 3.13.0-53-generic, with locale C, with libpcap version
1.8.0-PRE-GIT_2015_11_05, with libz 1.2.3.4, with GnuTLS 2.12.14, with Gcrypt
1.5.0.
Intel(R) Core(TM) i7-4600U CPU @ 2.10GHz (with SSE4.2)

Built using gcc 4.6.3.

Wireshark is Open Source Software released under the GNU General Public
License.

Check the man page and http://www.wireshark.org for more information.
--
Pressing "Restart current capture" button with live capture running in
promiscuous mode fails with "no interface" selected error.

The root cause has been identified and relates to rtnl messages being sent when
setting promiscuous mode on/off. The rtnl messages trigger an action to refresh
the list of network interfaces that then deselects the selected capture
interfaces.


You are receiving this mail because:
  • You are watching all bug changes.