~rumpelsepp/homepage

a91aa6841587e4c2e078d0facdb621a8c27c77a0 — Stefan Tatschner 12 days ago 4b7b8ce
fix typo
1 files changed, 1 insertions(+), 1 deletions(-)

M content/blog/2021-02-28-vpn-over-ssh.md
M content/blog/2021-02-28-vpn-over-ssh.md => content/blog/2021-02-28-vpn-over-ssh.md +1 -1
@@ 59,7 59,7 @@ Everything which is written to `ssh`'s stdin is written to the remote process' s
Well, let's spawn a `socat` an the remote side as well:

```
$ sudo socat TUN:192.168.255.1/24,up EXEC:'ssh -l root HOST "socat TUN:192.168.255.2/24,up"'
$ sudo socat TUN:192.168.255.1/24,up EXEC:'ssh -l root HOST "socat TUN:192.168.255.2/24,up -"'
```

The right argument (`EXEC:"…"`) spaws `ssh` logs into `HOST` and starts a `socat` which is connected to a tunnel device.