| 1 |
On Mon, 20 Aug 2012 19:04:38 +0100 |
| 2 |
Mick wrote: |
| 3 |
|
| 4 |
...[snip]... |
| 5 |
|
| 6 |
> You're welcome. BTW, port 22 in your example above does not *have* |
| 7 |
> to be port 22. As a matter of fact if it isn't, it would avoid |
| 8 |
> zillions of connection attempts by stupid botnets that could drive up |
| 9 |
> your bandwidth consumption. It could also be the same port as the one |
| 10 |
> you use at your local host. Whichever port you choose, you'll have to |
| 11 |
> allow it through the firewall at the remote machine and of course |
| 12 |
> whichever application is running at the remote host that you want to |
| 13 |
> connect to, should be listening on said port. -- |
| 14 |
> Regards, |
| 15 |
> Mick |
| 16 |
|
| 17 |
The remote machine(s) were set up by someone else. |
| 18 |
|
| 19 |
My firewall deals with port 22 by periodically checking for multiple |
| 20 |
failed logins from the same IP address and then blocking that address. |
| 21 |
The list gets long, but with the automatic handling, it's not a |
| 22 |
problem :-> |
Archives