From: Matthias Urlichs <matthias@urlichs.de>
To: wireguard@lists.zx2c4.com
Subject: Re: TCP Wireguard with socat
Date: Mon, 12 Mar 2018 12:30:51 +0100 [thread overview]
Message-ID: <88b9e6e0-1f38-1a20-3fac-372e96f847a3@urlichs.de> (raw)
In-Reply-To: <kvc0wmbZv_OgdINTzQhQnFxt0vFHFoqpVqYTFQkfPYOY_vqZHJN-bEvL9oJYuk-LJHubVyWlP2JCXTbRLK_9fGp7r298KveBFiOsF6P9r4Y=@protonmail.com>
On 12.03.2018 10:15, Gianluca Gabrielli wrote:
> Do you mean that socat just forward packets through the two specified c=
hannel without wrapping them?
Exactly. it doesn't know how to do any wrapping+unwrapping, thus it's
useless for exchanging data between a stream-based and a packet-based
port/device/interface/whatever (assuming that you need to keep the
packet boundaries intact).
--=20
-- Matthias Urlichs
next prev parent reply other threads:[~2018-03-12 11:21 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-09 16:41 Gianluca Gabrielli
2018-03-09 21:45 ` Matthias Urlichs
2018-03-12 9:15 ` Gianluca Gabrielli
2018-03-12 11:30 ` Matthias Urlichs [this message]
2018-03-12 14:37 ` Gianluca Gabrielli
2018-03-12 15:14 ` Gianluca Gabrielli
2018-03-12 15:44 ` Tim Sedlmeyer
2018-03-12 16:45 ` Gianluca Gabrielli
2018-03-12 17:05 ` Matthias Urlichs
2018-03-12 18:47 ` Matthias Urlichs
2018-03-13 9:19 ` Gianluca Gabrielli
2018-03-13 13:43 ` Matthias Urlichs
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=88b9e6e0-1f38-1a20-3fac-372e96f847a3@urlichs.de \
--to=matthias@urlichs.de \
--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).