Do I need to create a separate patch if I need this included in the next 2.6.x release?
Actually wireshark is not running on the Linux side and this is not using rpcap.
I am using the TCP@ sockets stream support built in to
dumpcap rather than extcap or rpcap.
On the linux side I have a TCP server which generates PCAPNG data with SHB and IDB sent to any client connecting followed by
EPBs.
I have wireshark/dumpcap 2.6.2 on Windows and Linux (Ubuntu 18.04) clients.
From: Anders Broman
Sent: Tuesday, September 18, 00:27
Subject: Re: [Wireshark-dev] Windows dumpcap -i TCP@<IP>
To: Developer support list for Wireshark
What version of Wireshark and what Linux version on the remote side? I think some work has ben done on rpcap recently so trying out the development version
Regards
Anders
From: Wireshark-dev <wireshark-dev-bounces@xxxxxxxxxxxxx> On Behalf Of
James Ko
Sent: den 18 september 2018 02:22
To: wireshark-dev@xxxxxxxxxxxxx
Subject: [Wireshark-dev] Windows dumpcap -i TCP@<IP>
Hi,
I am trying to connect to a remote PCAPNG stream from Windows using the TCP@ socket interface but the connection closes immediately after connecting. The same dumpcap command on linux works just fine to the remote TCP socket.
No errors indicating any failure are printed from dumpcap.exe
Capturing on 'TCP@192.168.1.100'
dumcap:
C:\>
On the remote end running in linux I see a connect and disconnect with EPOLLHUP event.
Has anyone else tried or have remote TCP socket connections working with dumpcap in Windows?
James
