Development discussion of WireGuard
 help / color / mirror / Atom feed
From: Matthias Urlichs <matthias@urlichs.de>
To: wireguard@lists.zx2c4.com
Subject: Re: TCP Wireguard with socat
Date: Fri, 9 Mar 2018 22:45:32 +0100	[thread overview]
Message-ID: <e0bff705-f328-0071-0fb7-0367d36f0074@urlichs.de> (raw)
In-Reply-To: <utLzzyzPJsv-W3vVhU4Sdchg_5A07v9qCxR1DeJ5Wu7RzJHcje1cCEjtEWi4j0aCN05ozn9b4VYJQsLovvl6TGPp-kbZ_5kfpReEJHQQXGk=@protonmail.com>

On 09.03.2018 17:41, Gianluca Gabrielli wrote:
> My first thought has been to make use of socat

socat can do either packet streams or byte streams. A UDP socket (or a
tun/tap interface) is a packet stream. TCP is a byte stream. You can't
forward a packet stream into a byte stream. (Well, OK, socat does allow
you to set that up, but it won't work.)

You need wrap your packets in some sort of frame (simplest: precede each
with a length word (but think about byte ordering)). I'm sure there are
programs which do that, or you can write your own. socat can't do it.

-- 
-- Matthias Urlichs

  reply	other threads:[~2018-03-09 21:36 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 [this message]
2018-03-12  9:15   ` Gianluca Gabrielli
2018-03-12 11:30     ` Matthias Urlichs
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=e0bff705-f328-0071-0fb7-0367d36f0074@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).