diff options
| -rw-r--r-- | users/wpcarro/website/blog/posts/tcp-tunneling-note.md | 15 |
1 files changed, 5 insertions, 10 deletions
diff --git a/users/wpcarro/website/blog/posts/tcp-tunneling-note.md b/users/wpcarro/website/blog/posts/tcp-tunneling-note.md index 4597405fae..06f6469aff 100644 --- a/users/wpcarro/website/blog/posts/tcp-tunneling-note.md +++ b/users/wpcarro/website/blog/posts/tcp-tunneling-note.md @@ -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 ``` |