Question

How do I configure my firewall to allow SSH traffic for new the Remote Console / Recovery Console?

I installed the new droplet-agent on my CentOS 7 droplet, but attempts to connect using the Droplet Console timed out.

I reasoned it was my firewall (iptables) setup. When I disabled iptables, the Console connected, using IP address 198.211.111.194. ARIN shows that CIDR 198.211.96.0/19 belongs to Digital Ocean, so that makes sense.

How do I configure iptables to safely allow only legitimate SSH traffic for the Droplet Console?

Thanks in advance for your help!


Submit an answer

This textbox defaults to using Markdown to format your answer.

You can type !ref in this text area to quickly search our full set of tutorials, documentation & marketplace offerings and insert the link!

Sign In or Sign Up to Answer

These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.

Want to learn more? Join the DigitalOcean Community!

Join our DigitalOcean community of over a million developers for free! Get help and share knowledge in Q&A, subscribe to topics of interest, and get courses and tools that will help you grow as a developer and scale your project or business.

This comment has been deleted

Hi @aknash,

Well, I’ll recommend allowing only IP addresses that are needed and only on PORTS that are meant to be used by such IPs.

To allow incoming SSH connections from a specific IP address or subnet, specify the source. For example, if you want to allow the entire 198.211.96.0/19 subnet, run these commands:

sudo iptables -A INPUT -p tcp -s 198.211.96.0/19 --dport 22 -m conntrack --ctstate NEW,ESTABLISHED -j ACCEPT
sudo iptables -A OUTPUT -p tcp --sport 22 -m conntrack --ctstate ESTABLISHED -j ACCEPT

The second command, which allows the outgoing traffic of established SSH connections, is only necessary if the OUTPUT policy is not set to ACCEPT.