Appendix A. TCP Ports Used by ThinLinc
A.1. On Machine Running VSM Server
22: SSH Daemon
Port 22 is not used by ThinLinc per se, but since no ThinLinc installation can work without a
running SSH daemon, we list port 22 here. Port 22 is the normal SSH port, but basically any port
can be used - the client has support for connecting to any port. Note however that if the SSH
daemon on the VSM server is listening on port x, all VSM agents must also have their SSH
daemons configured to listen on port x.
300: ThinLinc HTML5 Browser Client
By default, ThinLinc’s HTML5 Browser client service tlwebaccess is available on TCP port 300.
Traffic to this port is encrypted (TLS).
Note: The port on which tlwebaccess runs is configurable via the parameter
/webaccess/listen_port. See Section 8.7.3.1.1 for details.
1010: ThinLinc Administration Interface (tlwebadm)
By default, ThinLinc’s web-based administration interface is available on TCP port 1010. In order
to access this interface remotely, port 1010 will need to be reachable. Traffic to this port is
encrypted (TLS).
Note: The port on which tlwebadm runs is configurable via the parameter /tlwebadm/listen_port.
See Section 16.2 for details.
9000: VSM server
The VSM server listens on port 9000. The traffic is not encrypted, but sensitive information will
only be shared with root or connections originating from a port lower than 1024, from a list of
known IP adresses. The protocol used is XML-RPC through HTTP (using a minimal internal HTTP
server in the VSM server).
A.2. On Machine Running VSM Agent
22: SSH Daemon
Just as for the VSM server, there must be a SSH Daemon running on all VSM agent machines. This
daemon is normally listening to port 22, although it can listen to other ports as well. See the entry
about port 22 on Section A.1.
197
Comentarios a estos manuales