Skip to main content

IP filters in TCP, SSH, Postgres and Redis tunnels

· 3 min read

In the console client tuna version v0.25.0 we added the ability to restrict IPs and subnets from which connections can be made. This increases the level of security and is especially important in applications without built-in authorization.

New flags

The tuna tcp, tuna ssh, tuna postgres and tuna redis commands have new flags and env analogs:

--cidr-allow # Reject connections that do not match specified CIDRs
--cidr-deny # Reject connections matching specified CIDRs

Usage examples

You can define a whitelist of subnets in CIDR format:

tuna tcp 3389 --cidr-allow="10.0.0.1/32"

Or block access from specific subnets:

tuna tcp 3389 --cidr-deny="10.0.0.1/32"

You can combine, for example specify a wide network and subtract private IPs:

tuna tcp 3389 --cidr-allow="10.0.0.1/24" --cidr-deny="10.0.0.33/32"

You can also pass lists separated by commas:

tuna tcp 3389 --cidr-allow="10.0.0.1/24,192.168.0.1/24" --cidr-deny="10.0.0.33/32,192.168.0.33/32"

IP policies in Team

In teams, if IP policies are specified, they will work in conjunction with these flags.

Update

To update, follow the instructions.

Leave feedback

If you enjoy using Tuna, or on the contrary you are not happy with something, please leave feedback.

Help

We value our users and carefully review every request. If you have any problems with tuna, please contact us in one of the following ways: