Network Settings 3.x

This page is related to the Control Center interface present on HMP200, HMP130, and HMP100.
For newer players, see "Network settings" and "System" pages.

Description

The "Network Settings" page of HMP Control Center allows configuring different network-related settings, grouped within the following tabs: Connections, Advanced, Credentials, HTTPS, Proxy and SNMP.

Connections tab

Connections tab

The HMP can be configured to use as network interface one of the following:

• Ethernet
  • DHCP configuration (default). The device has an IP address assigned by the DHCP server on the network.
  • Fixed IP. The user must specify the IP settings.
• 3G Modem

Notes:

• If the HMP is configured to use DHCP, but no DHCP server is found, the HMP is using an autoconfigured IP in the range 169.254.1.0-169.254.254.255.
• When using fixed IP, only the "Address" and the "Netmask" fields are mandatory. However, the "Gateway" and the "DNS" fields should also be entered to be able to access the Internet and to resolve domain names (for instance, to update the Firmware or get RSS feeds).
• When using a USB cellular modem, the device is still accessible on the Ethernet port using either its IPv6 address or the link local address. See Get Connected for more details.
• See the Troubleshooting section of the Get Connected page for more troubleshooting on connecting to the HMP.

Advanced tab

Advanced tab

On this tab you can configure:

1. Identification elements for the player (which by default are both set to the player serial number):
   • Device name - can be used to assign a human-friendly name to the player.
   • Multiscreen ID - useful when the HMP is part of a video wall displaying a multiscreen project.
2. The Network API status:
   • You can enable / disable the Network API server, which is part of the "Shared Variables" mechanism. If necessary, you can also change the default port (1234).
3. RPC Security

   Available since firmware 3.4

   • You can enable / disable RPC request using AJAX (CORS) and configure the API Key to protects the HMP against CSRF (Cross-site request forgery) when using CORS (Cross-origin resource sharing).

   When doing an RPC request using AJAX from a web page located on another host, i.e. using CORS, an additional query string parameter spx-api-key must be present in the request and the content of the query must be set to the value of the API Key configured above, i.e /rpc?spx-api-key=[rpc-api-key].

4. Network Watchdog conditions:
   • The Network Watchdog is activated if any of the two conditions are set to a value other than 0 (0s by default). Both parameters can be configured using a time defined in seconds (e.g. 10s), minutes (e.g. 10m) or hours (e.g. 1h).
   • When activated, the HMP will reboot if one of the condition is no longer valid. Link-local (i.e. Zeroconf) addresses are not taken into account.
   • The watchdog may be used in case of using a 3G modem, as sometimes it's necessary to reset the 3G dongle by doing a reboot of the HMP to restore a lost connection. Please be aware that a quick succession of restarts will make the HMP to enter into Safe mode and even Recovery mode.

Credentials tab

For DiVA, HMP300 and HMP350 devices, this section can be found under System > Saved Passwords page.

Credentials tab

On this tab, you can configure credentials to be used by the HMP when accessing resources from remote servers (e.g., direct reference, Client/Server mode, Pull Mode etc.) requiring authentication.

To add / modify credentials follow these steps:

1. Enter the following information:
   • The server URI (it can also include a path on the server if different credentials are needed for different parts of the server).
   • The username & password.
   • The realm (optional - used to specify different credentials based on the realm returned by the server).
2. If you need additional servers, press the "Add server row" button.
3. Press the "Apply" button to save the credentials.

To remove credentials follow these steps:

1. Press the red cross icon next to the credentials set.
2. Press the "Apply" button.
3. Restart the HMP.

HTTPS tab

Added in firmware 2.2.5. Updated in firmware 3.0.0.

HTTPS tab

On this section, you can enable / disable the full verification of HTTPS certificates (enabled by default) and upload additional root certificates to be trusted by the HMP.

SSL certificates are used to verify the authenticity of servers to which the player connects to via secure HTTP (https). The player already has a built-in database of the root certificates of public certification authorities matching those in web browsers. You only need to add extra root certificates if the player needs to connect to servers that use a certificate delivered by a private, or enterprise internal, certification authority. It may also be required if the player needs to access secure sites via a firewall with SSL inspection enabled.

See also the HTTPS section on the Security page for possible SSL errors.

Warning:

Disabling the full verification of HTTPS certificates renders all secure HTTPS (https) connections insecure and vulnerable to man in the middle attacks, thus this should only be used for testing and diagnosis, never in a production environment.

Proxy tab

Proxy tab

On this tab, you can configure the proxy settings to be used by the HMP:

• The server hostname address (without the http part) and the port.
• Enable / disable bypassing the proxy server for local addresses.

  When enabled, the HMP will first query the hostname to find the corresponding IP address. It will then check if the IP address is in the same subnet as the player according to the subnet mask currently configured and if so, the proxy will be bypassed. If the IP is external or the hostname cannot be resolved, then the proxy will be used.

• The username and password. Note that the HMP supports only basic and digest authentication mechanisms.

For more details, see Proxy settings page.

SNMP tab

SNMP tab

On this tab, you can configure the SNMP settings of the player. The HMP supports SNMP version 2c (with read-only access), does not generate SNMP traps and runs the Net-SNMP 5.4 (fully patched).

By default, the access to SNMP is disabled (closed); it can be opened to a specific IPv4 addresses range or opened without restrictions (IPv6 is accepted in this case), and can be accessed via UDP and TCP.

For the list of MIBs that the HMP makes available, see SNMP monitoring page.