From 2bd2a041513d7a9e4d21b29eab959ab92a6b7980 Mon Sep 17 00:00:00 2001 From: Gerhard Rieger Date: Mon, 12 Jun 2023 20:51:16 +0200 Subject: [PATCH] socat-tun.html: not TCP but UDP --- CHANGES | 4 ++++ doc/socat-tun.html | 4 ++-- 2 files changed, 6 insertions(+), 2 deletions(-) diff --git a/CHANGES b/CHANGES index 5594f73..ca914e5 100644 --- a/CHANGES +++ b/CHANGES @@ -71,6 +71,10 @@ Porting: Small correction in configure.ac makes Socat C99 able. Thanks to Florian Weimer from Red Hat for provinding a patch. +Documentation: + socat-tun.html described TCP as tunnel medium but this does not keep + packet boundaries. Changed to UDP. + Testing: Idea: EXEC,SYSTEM addresses can keep packet boundaries when option socktype= diff --git a/doc/socat-tun.html b/doc/socat-tun.html index d73acd2..ab04f56 100644 --- a/doc/socat-tun.html +++ b/doc/socat-tun.html @@ -53,14 +53,14 @@ the two socat instances; the TUN interfaces both have the same quality.

TUN Server

-socat -d -d TCP-LISTEN:11443,reuseaddr TUN:192.168.255.1/24,up +socat -d -d UDP-LISTEN:11443,reuseaddr TUN:192.168.255.1/24,up

After starting this command, socat will wait for a connection and then create a TUN pseudo network device with address 192.168.255.1; the bit number specifies the mask of the network that is pretended to be connected on this interface.

TUN Client

-socat TCP:1.2.3.4:11443 TUN:192.168.255.2/24,up +socat UDP:1.2.3.4:11443 TUN:192.168.255.2/24,up

This command should establish a connection to the server and create the TUN device on the client.