maurice/snix
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

chore(wpcarro/blog): Edit "TCP Tunneling (note to self)"

Browse source 
Proof-reading much easier when Markdown is rendered in the browser.

Change-Id: Ia173dea817866d214547546bc3428ac6fe6782bf
Reviewed-on: https://cl.tvl.fyi/c/depot/+/7305
Tested-by: BuildkiteCI
Reviewed-by: wpcarro <wpcarro@gmail.com>
Autosubmit: wpcarro <wpcarro@gmail.com>
This commit is contained in:
William Carroll 2022-11-17 10:59:09 -08:00 • committed by clbot
parent 8c3d87cd14
commit 44076fbd42
1 changed files with 5 additions and 10 deletions
Download patch file Download diff file Expand all files Collapse all files

15
users/wpcarro/website/blog/posts/tcp-tunneling-note.md
View file

@ -16,7 +16,7 @@ on the remote. It's quite cool!
Run the following on your local machine to forward your remote's traffic:
```shell
$ ssh -R 4317:127.0.0.1:4317 -N -f user@remote
λ ssh -R 4317:127.0.0.1:4317 -N -f user@remote
```
Here is an abridged explanation of the flags we're passing from `man ssh`:
@ -34,19 +34,14 @@ ssh: Could not resolve hostname 4317:127.0.0.1:4317: Name or service not known
```
The remote should now be forwarding traffic from port `4317` to our
machine. We can verify with the following:
```shell
$ nc -l 4317 -k
```
machine.
## Testing
Let's generate some traffic on the remote. **Note:** you should see the output
in the shell in which you're running `nc -l 4317 -k`.
Let's generate some traffic on the remote:
```shell
$ telnet localhost 4317
λ telnet localhost 4317
Trying ::1...
Connected to localhost.
Escape character is '^]'.
@ -57,7 +52,7 @@ world
Locally you should see:
```shell
λ nc -l 4317 -k
λ nc -l 4317 -k # run this *before* running the above command
hello
world
```