All of lore.kernel.org
 help / color / mirror / Atom feed
From: Gianluca Gabrielli <tuxmealux@protonmail.com>
To: "wireguard@lists.zx2c4.com" <wireguard@lists.zx2c4.com>
Subject: TCP Wireguard with socat
Date: Fri, 09 Mar 2018 11:41:45 -0500	[thread overview]
Message-ID: <utLzzyzPJsv-W3vVhU4Sdchg_5A07v9qCxR1DeJ5Wu7RzJHcje1cCEjtEWi4j0aCN05ozn9b4VYJQsLovvl6TGPp-kbZ_5kfpReEJHQQXGk=@protonmail.com> (raw)

Hi everybody,

I'm an happy wireguard user since a while, but at that time I need to link =
two peers and I can only use TCP. I know that there are thousand of other t=
ools I can use, but I'd like to do it using wireguard.
My first thought has been to make use of socat, since some newest version a=
 new address type called INTERFACE has been added (http://www.dest-unreach.=
org/socat/doc/socat.html#ADDRESS_TYPES), so I tried to use it but I've not =
been able to make it works.
This is why I'm here asking your feedbacks, or to collect other ideas to le=
t wireguard works through a TCP tunnel.

I wrote all the notes about the tests I made on a pdf, I know that this is =
not the good way to share with you my results, and I should write it here o=
nce again in plaintext. But for me it will would turn on a waste of time do=
 it again, and it also would be less comprehensible.
I uploaded the pdf online instead to attach it to this email hence nobody n=
eeds to open it on his personal laptop, but it can be viewed via any browse=
r. I personally hate open unknown file on my computer. The pdf can be viewe=
d from the following link:
https://drive.google.com/open?id=3D1KrLvU1D0K4YpRHi-jsIjbExh0lFTRQks

I will really appreciate any constructive feedback or suggestion on how to =
easily use wireguard with TCP.

Thanks,
Gianluca

             reply	other threads:[~2018-03-09 16:32 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-03-09 16:41 Gianluca Gabrielli [this message]
2018-03-09 21:45 ` TCP Wireguard with socat Matthias Urlichs
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='utLzzyzPJsv-W3vVhU4Sdchg_5A07v9qCxR1DeJ5Wu7RzJHcje1cCEjtEWi4j0aCN05ozn9b4VYJQsLovvl6TGPp-kbZ_5kfpReEJHQQXGk=@protonmail.com' \
    --to=tuxmealux@protonmail.com \
    --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.