WireGuard Archive on lore.kernel.org
 help / color / Atom feed
* Tun interface do not route packets on Windows 7 (extended no-NAT)
@ 2019-08-26  9:39 Vasili Pupkin
  0 siblings, 0 replies; only message in thread
From: Vasili Pupkin @ 2019-08-26  9:39 UTC (permalink / raw)
  To: WireGuard mailing list

In my setup I have a client running Win7, the tun interface allows to
make connection from client to server but it only route packets back
for some time and then broke.

The client system is NOT behind the NAT and PersistentKeepalive=25 do
not help, the issue is local and external network route encrypted
packets as expected. Have tested it with wireshark.

I have checked the tun adapter with RawCap tool (wireshark do not let
you monitor tun interface on Win7) and decrypted packets sent by the
server actually generated inside the tun
interface on the client but aren't routed to the process nor processed
any further, they stuck on OSI level 3. If I then ping server from
client the tun interface revives but broke again after like 30 seconds
of silence. The support for Win7 will be dropped later this year but
it is still rather popular OS among users.
WireGuard mailing list

^ permalink raw reply	[flat|nested] only message in thread

only message in thread, back to index

Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2019-08-26  9:39 Tun interface do not route packets on Windows 7 (extended no-NAT) Vasili Pupkin

WireGuard Archive on lore.kernel.org

Archives are clonable:
	git clone --mirror https://lore.kernel.org/wireguard/0 wireguard/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 wireguard wireguard/ https://lore.kernel.org/wireguard \
	public-inbox-index wireguard

Example config snippet for mirrors

Newsgroup available over NNTP:

AGPL code for this site: git clone https://public-inbox.org/public-inbox.git