From: Luca Beltrame <lbeltrame@kde.org>
To: JuniorJPDJ <juniorjpdj@juniorjpdj.pl>
Cc: WireGuard mailing list <wireguard@lists.zx2c4.com>
Subject: Re: [HACK] UDP tunneling over TCP for WireGuard
Date: Wed, 18 Apr 2018 23:12:30 +0200 [thread overview]
Message-ID: <2691203.H8StyC36JO@leon.lan> (raw)
In-Reply-To: <f47035e6-8940-7f24-6d13-f645a76bc3a7@juniorjpdj.pl>
[-- Attachment #1: Type: text/plain, Size: 348 bytes --]
In data mercoledì 18 aprile 2018 21:29:11 CEST, hai scritto:
> You can use this:
> https://github.com/wangyu-/udp2raw-tunnel
> instead of socat to avoid TCP over TCP effect.
This is interesting . I'll give it a shot in the next few days and see how it
fares (and report back).
--
Luca Beltrame - KDE Forums team
GPG key ID: A29D259B
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2018-04-18 21:12 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-18 11:55 [HACK] UDP tunneling over TCP for WireGuard Luca Beltrame
2018-04-18 15:55 ` Tim Sedlmeyer
2018-04-18 21:07 ` Matthias Urlichs
2018-04-18 16:36 ` Ximin Luo
[not found] ` <f47035e6-8940-7f24-6d13-f645a76bc3a7@juniorjpdj.pl>
2018-04-18 21:12 ` Luca Beltrame [this message]
2018-05-24 1:20 ` Beware of udp2raw-tunnel (was: [HACK] UDP tunneling over TCP for WireGuard) tomli
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=2691203.H8StyC36JO@leon.lan \
--to=lbeltrame@kde.org \
--cc=juniorjpdj@juniorjpdj.pl \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.