Skip to content

Commit

Permalink
Mention IP filtering is available in inlets-cloud
Browse files Browse the repository at this point in the history
Signed-off-by: Alex Ellis (OpenFaaS Ltd) <[email protected]>
  • Loading branch information
alexellis committed Oct 20, 2024
1 parent c6bec13 commit a830b83
Showing 1 changed file with 3 additions and 1 deletion.
4 changes: 3 additions & 1 deletion blog/_posts/2024-10-17-ssh-with-inlets-cloud.md
Original file line number Diff line number Diff line change
Expand Up @@ -190,7 +190,7 @@ Access is completely private, there is no way to decrypt the SSH traffic, and it

**IP filtering/allow list**

For taking things further, sshmux also supports an IP allow list, which will be available in inlets-cloud shortly, or which you can use already today with the self-hosted version of inlets-pro.
For taking things further, sshmux also supports an IP allow list, which is available for inlets-cloud and self-hosted tunnels.

If the IP for your mobile hotspot was 35.202.222.154, you could write the following to restrict access to `nuc.example.com` to only yourself:

Expand All @@ -202,6 +202,8 @@ upstreams:
- 35.202.222.154
```
Then just add a `--proxy-protocol` argument to the `inlets-pro sshmux` command before restarting the command. You can use `v1` or `v2` as the argument, just make sure it is the same as the one you selected for the tunnel server.

Watch a video walk-through of this tutorial:

{% include youtube.html id="ws3-VlL2884" %}

0 comments on commit a830b83

Please sign in to comment.