Revision 7.10
2/28/2012
This allows only encrypted traffic on the private network. There are multiple approaches
to authentication. The Glider could authenticate via
telnet
to the
proxy
computer. The
Glider's user account could (e.g. via .bash_login) initiate a
ssh
connection to the actual
Dock Server. Alternatively, all the port 6565 traffic on the
proxy
computer could be
forwarded to the Dock Server (at the system level) and the glider could authenticate at
the actual Dock Server.
All of the intervening Firewalls and NAT routers must be configured to route and pass
ssh
traffic from the
proxy
computer.
12.5.5 Configuring the Operating System Firewall
The software Firewall in Dock Server is disabled by default under the presumption that
the Dock Server is deployed on a secure network. If enabled, it must be configured to
accept packets on the following ports:
Port Number
Service Name
Why?
21
FTP
Transfer data from Glider Data
to/from Dock Server and Users
22
SSH
Remote management via
gmc
outofbandtools
80
WWW
Web Launch Glider/GLMPC
Terminal. Observe Dock
Server status from a web
browser.
6564
Glider/GLMPC Terminal
Allow remote usage
6565
RUDICS
Allow Glider to connect to
Dock Server.
NOTE: as of this writing, PASSIVE FTP CONNECTIONS will not work through the Dock
Server Operating System Firewall! Configure your FTP Client for Active Connections
only if you enable the Firewall.
The Firewall can be configured from a GUI launched from the Menu:
Applications / System Settings / Security Level
The appropriate settings are shown in the following screen shot:
Page 154 of 228