Network Services¶
The Control Center is designed to receive and respond to requests from Local Managers. In secure environments, exceptions made need to be made in firewalls to ensure proper operation.
Ports Used¶
The following inbound ports are used during normal operation.
Port | Protocol | Function | Description |
---|---|---|---|
443 | TCP | HTTP | provides access to the Control Center GUI - required |
8443 | TCP | Heartbeat and Archive | used for communication between Control Center and Local Managers - required |
7 | TCP | Echo | used by the Pulse feature |
22 | TCP | SSH | used to connect to the Control Center CLI |
2222 | TCP | Reverse SSH | used by Local Managers to create a reverse-ssh tunnel with the Control Center |
2244 | TCP | Reverse SSH | used by clients to connect to Local Managers via the reverse-SSH tunnel |
80 | TCP | HTTP | provides access to the Control Center GUI, redirects to 443 |
123 | UDP | NTP | provides NTP servers to managed devices |
If you will be using the SOCKS proxy server, you will also need to open TCP 1080 (typical default) or TCP 9000 (as suggested in our documentation).
Note
This information is for use with external firewalls and NATs. The Lantronix Control Center runs its own firewall to ensure only the above ports are accessible.
Traffic Compression¶
The use of network traffic compression services / devices is not recommended for Lantronix products. Devices such as Riverbed accelerators / optimizers may cause Heartbeat and Pulse features to fail.
Lantronix recommends adding exceptions for the ports listed above to ensure proper operation.