 |
FirewallBuilder |
|
Search Users Guide
If the ssh daemon on your firewall is listening on an alternate port, then you need to configure the built-in installer so that it will run SCP and ssh clients with command line parameters that would make them connect to this port. This is done in the installer tab of the firewall object advanced settings dialog as shown on the following screenshot (here we set the port to "2222"):
Note
On Unix, the command line option that specifies the port number is different for ssh and SCP. It is lowercase -p for ssh and uppercase -P for SCP. If you use the putty tool plink.exe and pscp.exe on Windows, the option to specify an alternate port number is -P (capital "P") for both.
You can use the same input fields in this dialog to add any other command line parameters for ssh and SCP. For example, this is where you can configure parameters to make it use an alternate identity file (private keys). This information is saved with a firewall object rather than globally because you may need to use different parameters for different firewall machines, such as different key files or ports.
Copyright © 2000-2012 NetCitadel, Inc. All rights reserved.
Using free CSS Templates.