# Limit the interfaces SSH is exposed on

**URL:** <https://forums.balena.io/t/limit-the-interfaces-ssh-is-exposed-on/373293>\
**Category:** Feature Requests\
**Tags:** balenaos\
**Created:** [July 19, 2023, 2:42pm UTC](https://forums.balena.io/t/limit-the-interfaces-ssh-is-exposed-on/373293 "2023-07-19T14:42:19Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![system](https://global.discourse-cdn.com/balena/original/2X/6/60e5c11e1222480d38bea45d7ab9ea57bbe86d53.png) [@system](https://forums.balena.io/u/system)\
**Post date:** [July 19, 2023, 2:42pm UTC](https://forums.balena.io/t/limit-the-interfaces-ssh-is-exposed-on/373293/1 "2023-07-19T14:42:19Z")

</div>

The SSH daemon listening on port 55555 currently listens on all network interfaces, which is problematic for devices that are going to be deployed on untrusted networks. Ideally this would be limited to the balenaCloud VPN connection, and optionally any explicitly safelisted interfaces configured by the user.

We can work around this by deploying a container to set up iptables rules, but that does result in a race condition where the host OS SSH daemon is up, but the container has not yet been started.
