Re: If Wireshark is started with -i option it does not set wanted interface if the interface is a pipe

[Peter Wu <peter () lekensteyn nl>]

Hi Anders,

Have you tried adding the "-k" option to start the capture? That should
work. Having that said, there seems to be an issue with the interface
selection for which I opened:
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=13865

Kind regards,
Peter

On Mon, Jun 26, 2017 at 01:25:29PM +0000, Anders Broman wrote:
> Hi,
> I did a git bisect and this is the commit that broke it:
>
> wireshark -i /tmp/Vnfcscfv1_fee0_eth1_Oc2th -i /tmp/Vnfcscfv1_fee1_eth1_c6nZw -i /tmp/Vnfcscfv1_fee2_eth1_leNWM -i 
> /tmp/Vnfcscfv1_fee3_eth1_F37Bh
>
> 40a5fb567a9bd1bb02d38ca33efe64392230d27d is the first bad commit
> commit 40a5fb567a9bd1bb02d38ca33efe64392230d27d
> Author: Peter Wu <peter () lekensteyn nl>
> Date:   Fri Mar 10 03:46:53 2017 +0100
>
>     Restore interface selection after interface refresh
>
>     Remember which interfaces were selected for the next capture and restore
>     the selection (note that only active capture devices are stored in
>     "ifaces", so simply querying that list does not work).
>
>     The original change tried to fix duplicate devices (which were added
>     from "ifaces" to "all_ifaces") by clearing "ifaces", this patch tries to
>     fix that by ignoring all non-PIPE devices while preserving "ifaces".
>
>     Now after refreshing the interfaces list in Qt, the selection in the
>     Manage Interfaces dialog is preserved. Removal of the bluetooth0
>     interface+refresh does hide the interface. Read+refresh does add the
>     interface (and preserve the selected state).
>
>     Change-Id: I26a78982f0327c835dc96da9c813e38f31d6cd3d
>     Fixes: v1.99.0-rc1-879-g55733ea170 ("fix scan_local_interfaces()")
>     Reviewed-on: https://code.wireshark.org/review/20477
>     Petri-Dish: Peter Wu <peter () lekensteyn nl>
>     Tested-by: Petri Dish Buildbot <buildbot-no-reply () wireshark org>
>     Reviewed-by: Stig Bjørlykke <stig () bjorlykke org>
>     Reviewed-by: Anders Broman <a.broman58 () gmail com>
>
> :040000 040000 2be10254a5b2bf2ef9053eb70cc50274ac2cdf8b 3e51ea9648ad6086fb1ff3a1029da1deafcd6f41 M   ui
>
> From: Wireshark-dev [mailto:wireshark-dev-bounces () wireshark org] On Behalf Of Anders Broman
> Sent: den 5 juni 2017 15:13
> To: wireshark-dev () wireshark org
> Subject: [Wireshark-dev] If Wireshark is started with -i option it does not set wanted interface if the interface is 
> a pipe
>
> Hi,
> I received this report from an internal user, does anyone know what have been changed?
>
>
> When Wireshark is started with -i option it does not set wanted interface if the interface is a pipe
>
> ... has one script that first creates named pipe and then starts Wireshark on that interface:
> serv308 [13:45] [/tmp] -> ps -ef | grep xxxx | grep pipe
> xxxx  15565 15512  0 13:08 ?        00:00:16 /app/vbuild/ wireshark -i /tmp/pipe_15512
>
> pipie_15512 is not shown in interface list and I consider this as a problem, can you please advise?
>
> I used Interface Management to manually create new interface (/tmp/pipie_15512) and verified if decoding is working 
> as expected. And I can say it is.
>
>
> Regards
> Anders
___________________________________________________________________________
Sent via:    Wireshark-dev mailing list <wireshark-dev () wireshark org>
Archives:    https://www.wireshark.org/lists/wireshark-dev
Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-dev
             mailto:wireshark-dev-request () wireshark org?subject=unsubscribe