Development discussion of WireGuard
 help / color / mirror / Atom feed
From: "Siegfried Herholdt (GTS)" <siggi@gts.com.na>
To: "wireguard@lists.zx2c4.com" <wireguard@lists.zx2c4.com>
Subject: Windows 10 Traffic Dump on Wireguard Interface
Date: Fri, 2 Aug 2019 14:54:31 +0000	[thread overview]
Message-ID: <0102016c52d33db1-5ed34601-9f16-4305-abfa-96ce1f22f183-000000@eu-west-1.amazonses.com> (raw)
In-Reply-To: <D75CD021-DF88-4F3F-86DF-7A79BE7EDBD8@contoso.com>

Hi,

I am an early adopter of Wireguard and trying out various network configurations.

I have issues passing certain types of traffic from a MacOS Wireguard client to a Windows 10 Wireguard server (master).  To troubleshoot this I normally do a network traffic dump on each side, among other things.  However, I am not able to get any combination of tools to capture raw traffic on my my Wireguard interface.

With Wireshark the Wireguard interface does not show up, even if the Wireguard tunnel is up and working for some traffic, for e.g. Remote Desktop.  The same when I use Microsoft Message Analyzer. It seem as if Wireguard's network interface is not available.  However, if I list my IPV4 interfaces via Powershell using netsh, the Wireguard interface is in the list.

Does anybody have a pointer for me how to capture the raw network traffic on the Wireguard interface?

Thanks,
Siggi


_______________________________________________
WireGuard mailing list
WireGuard@lists.zx2c4.com
https://lists.zx2c4.com/mailman/listinfo/wireguard

           reply	other threads:[~2019-08-05 18:45 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <D75CD021-DF88-4F3F-86DF-7A79BE7EDBD8@contoso.com>]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=0102016c52d33db1-5ed34601-9f16-4305-abfa-96ce1f22f183-000000@eu-west-1.amazonses.com \
    --to=siggi@gts.com.na \
    --cc=wireguard@lists.zx2c4.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).