2.6 Other Network Services and Plugins
Besides the other services mentioned in the previous sections, the device provides the following network communication/control facilities:
- TCP Remote Control Socket: A TCP socket can be used to remotely control the device, similar to the Web Remote. This facility can be used by Telnet from any machine. The following parameters must be configured for the TCP socket to be available:
1: ENABLE_TCP_NETWORK_REMOTE = 0
2: REMOTE_CONTROL_TCP_HOST = '0.0.0.0'
3: REMOTE_CONTROL_TCP_PORT = 16311
This configuration would disable the remote. To enable it, set ENABLE_TCP_NETWORK_REMOTE to `1.
- UDP Remote Control Socket: A UDP socket can also be used to remotely control the device, almost identical to the TCP remote. This is also used for the Web Remote in the Web Interface. The following parameters must be configured for the UDP socket to be available:
1: UDPREMOTE_PORTS = ''
2: UDPREMOTE_CLIENTS = ''
3: ENABLE_NETWORK_REMOTE = 1
4: REMOTE_CONTROL_HOST = '127.0.0.1'
5: REMOTE_CONTROL_PORT = 16310
This configuration enables the UDP remote control, but binds to the localhost, which is the default setting due to security. You can however change the REMOTE_CONTROL_HOST to 0.0.0.0 for network wide access.
- SSH2 Service: For advanced management purposes, the device provides Secure Shell access to the device. Note that this cannot be disabled by means of configuration and is only intended to be used by advanced users or the UMP support team. The service uses the default TCP port for SSH, 22.
- Rendezvous Interface: The device provides an experimental Rendezvous plugin which has been tested by its developers on IE6 with Howl on Windows XP and Safari on Mac OS 10.2 “Panther”. The plugin is listed under Plugins -> Global and is called ‘ump_rendezvous’.