Hi Per,
I noticed the same. It seems like npcap isn't binding to NdisMediumIP
for layer 3 devices. Thanks for posting that github issue. I'll add
some details to it so that the npcap developers can fix it.
Jason
Hi,
currently Wintun devices are not seen by Wireshark/npcap, which is a
bit annoying as it removes a simple way of debugging problems with
various protocols over VPNs that use Wintun.
There is an issue reported here (with some comments from me):
https://github.com/nmap/npcap/issues/173
Does an
Hi Joshua,
A new version is now released, which should address all the issues you
found. Let me know how things go...
Jason
With no further info from you, it's hard to know how to proceed. I'll
be releasing this fix in the next version hoping it's sufficient for
you:
https://git.zx2c4.com/wireguard-windows/commit/?id=4a45e2fcc0cf0884bc82268c1c15af2fe477d5be
Thanks! Applied.
https://git.zx2c4.com/wireguard-go/commit/?id=913f68ce3820801e045632cb05c6f11e0df50b47
From: Haichao Liu
fix panic: send on closed channel when remove peer
Change-Id: Ica0e2447cd941bd3a26948aacafc837904ea18b2
Signed-off-by: Haichao Liu
---
device/peer.go| 6 +-
device/receive.go | 2 ++
device/send.go| 4
3 files changed, 11 insertions(+), 1 deletion(-)
diff --
Hi Roman,
Op 18-11-2020 om 08:32 schreef Roman Mamedov:
Do you use ULA IPs (fc00::/7) for the tunnel endpoints? Those are always
depreferred compared to IPv4. See RFC 6724:
Actually we do this:
10.42.42.0/24
fddd:42:42:42/64
Let us test with some other prefix. Thanks for the hint.
I'll get
