Re: TCP Wireguard with socat

[Gianluca Gabrielli <tuxmealux@protonmail.com>]

=E2=80=90=E2=80=90=E2=80=90=E2=80=90=E2=80=90=E2=80=90=E2=80=90 Original Me=
ssage =E2=80=90=E2=80=90=E2=80=90=E2=80=90=E2=80=90=E2=80=90=E2=80=90

On March 9, 2018 10:45 PM, Matthias Urlichs <matthias@urlichs.de> wrote:

> On 09.03.2018 17:41, Gianluca Gabrielli wrote:
>=20
> > My first thought has been to make use of socat
>=20
> socat can do either packet streams or byte streams. A UDP socket (or a
>=20
> tun/tap interface) is a packet stream. TCP is a byte stream. You can't
>=20
> forward a packet stream into a byte stream. (Well, OK, socat does allow
>=20
> you to set that up, but it won't work.)
>=20
> You need wrap your packets in some sort of frame (simplest: precede each
>=20
> with a length word (but think about byte ordering)). I'm sure there are
>=20
> programs which do that, or you can write your own. socat can't do it.

Forwarding UDP packets (message oriented) into a TCP connection (stream ori=
ented) could be done without any problem. Think about an OpenVPN TCP tunnel=
 where you've redirected all your traffic, UDP connections as well.
Do you mean that socat just forward packets through the two specified chann=
el without wrapping them?