[179033] in North American Network Operators' Group
Re: Frontier: Blocking port 22 because of illegal files?
daemon@ATHENA.MIT.EDU (Stephen Satchell)
Thu Mar 26 07:24:43 2015
X-Original-To: nanog@nanog.org
Date: Thu, 26 Mar 2015 04:24:38 -0700
From: Stephen Satchell <list@satchell.net>
To: nanog@nanog.org
In-Reply-To: <CAEE+rGqimJYAfgmzm9AJ72+gcmJxfZLM7n4Rf03vynxKN=Qfeg@mail.gmail.com>
Errors-To: nanog-bounces@nanog.org
On 03/25/2015 07:31 PM, Aaron C. de Bruyn wrote:
> After getting a few helpful users on the phone to run some quick
> tests, we found port 22 was blocked.
It's been a while since I did this, but you can select an additional
port to accept SSH connections. A Google search indicates you can
specify multiple ports in OpenSSH. Picking the right port to use is an
exercise, though, that will depend on what other services you are
running on your server.
People with sane ISPs can use the standard port. People on Frontier can
use the alternate port, which shouldn't be firewalled by the provider.
If Frontier is running a mostly-closed firewall configuration, then you
have to be damn careful about the port you select.
