Skip to content
Browse files

Add a section to README and convert the solution to Visual Studio 11.…

… Source code not changed.
  • Loading branch information...
1 parent 307119d commit 7b000c593e5f884d2f259c4ada30fa9f4f85a9df @andrivet andrivet committed Sep 20, 2011
Showing with 21 additions and 4 deletions.
  1. +4 −2 ADVsock2pipe.sln
  2. +17 −2
6 ADVsock2pipe.sln
@@ -1,13 +1,14 @@

-Microsoft Visual Studio Solution File, Format Version 11.00
-# Visual Studio 2010
+Microsoft Visual Studio Solution File, Format Version 12.00
+# Visual Studio 11
Project("{FAE04EC0-301F-11D3-BF4B-00C04F79EFBC}") = "ADVsock2pipe", "ADVsock2pipe\ADVsock2pipe.csproj", "{4FF697D5-618B-49B2-A844-75F3B83A94A8}"
Project("{FAE04EC0-301F-11D3-BF4B-00C04F79EFBC}") = "ADVsock2pipe.Core", "ADVsock2pipe.Core\ADVsock2pipe.Core.csproj", "{EE38BED3-0746-44C1-8CE3-37D219AB4738}"
Project("{2150E333-8FDC-42A3-9474-1A3956D46DE8}") = "Solution Items", "Solution Items", "{8B2258F1-2B2A-43A5-B77A-5A61DF1969FB}"
ProjectSection(SolutionItems) = preProject
+ =
@@ -26,6 +27,7 @@ Global
{4FF697D5-618B-49B2-A844-75F3B83A94A8}.Debug|x86.ActiveCfg = Debug|x86
{4FF697D5-618B-49B2-A844-75F3B83A94A8}.Debug|x86.Build.0 = Debug|x86
{4FF697D5-618B-49B2-A844-75F3B83A94A8}.Release|Any CPU.ActiveCfg = Release|x86
+ {4FF697D5-618B-49B2-A844-75F3B83A94A8}.Release|Any CPU.Build.0 = Release|x86
{4FF697D5-618B-49B2-A844-75F3B83A94A8}.Release|Mixed Platforms.ActiveCfg = Release|x86
{4FF697D5-618B-49B2-A844-75F3B83A94A8}.Release|Mixed Platforms.Build.0 = Release|x86
{4FF697D5-618B-49B2-A844-75F3B83A94A8}.Release|x86.ActiveCfg = Release|x86
@@ -2,21 +2,25 @@
ADVsock2pipe is a small utility to connect a TCP socket to a Windows named pipe. It can be used, for example, to capture network data with tcpdump on Linux or iPhone/iPad and to see the capture in (almost) real-time in Wireshark on Windows.
+It is released under GPLv3.
# How to use ADVsock2pipe?
For example, to capture data on a device ( and send it to Wireshark on Windows ( on port 7777:
On the Windows workstation (
- `ADVsock2pipe -pipe=wireshark -p 7777`
-- Start Wireshark
-- Capture | Options, Interface: Local, \\\\.\pipe\wireshark
+- Start Wireshark
+- Capture | Options, Interface: Local, \\\\.\pipe\wireshark
- Start
On the device:
- `tcpdump -nn -w - -U -s 0 "not port 7777" | nc 7777`
# Why do I get errors in Wireshark when a stop a capture and start a new one?
This is because Wireshark is either expecting a header and does not receive one or is receiving a header when it does not expect one: Wireshark expect data in pcap format, a pcap header follows by packet data. If you stop and start tcpdump, Wireshark receives a pcap header in the middle of a capture and thus generates an error.
@@ -27,14 +31,25 @@ So to avoid any problem:
- Each time you stop tcpdump, stop Wireshark.
- And each time you stop Wireshark, stop tcpdump.
+# What are the command line options?
+--pipe=<name> where <name> is the name of the Windows pipe.
+--port=<port> where <port> is the TCP port number.
+--log=<level> where <level> is Debug, Info, Warning, Error or Critical. Determine the level of details given by this tool.
+--help or -h to get some help about this tool.
# How to build ADVsock2pipe?
In order to build ADVsock2pipe, you need to have Visual Studio 2010 or 2011 Developer Preview. Open the solution (ADVsock2pipe.sln) and build it.
# References
[Wireshark Wiki - CaptureSetup/Pipes](
# Copyright and license
Copyright (c) 2011 - [ADVTOOLS SARL](

0 comments on commit 7b000c5

Please sign in to comment.
Something went wrong with that request. Please try again.