Network access on HMP

From SpinetiX Support Wiki

(Redirected from Network access)
Jump to: navigation, search
It is not recommended to have the HMP connected directly to the Internet as it does not have a firewall and thus it is exposed to all sorts of threats. The player is not designed to be used in this manner - alternatives for remote access are detailed below.


The HMP provides different network interfaces which can be accessed via HTTP when the player is connected to the network and properly configured. In case of HMP350 and HMP300, the HTTPS protocol can be used as well.

The HMP also uses the WebDAV protocol for pushing content and raw TCP socket connection for accessing the Shared Variables interface.

Other protocols, like SSH, Telnet, FTP etc., are not supported.

HMP addresses

The player web interface can be accessed from a web browser using http://HMP_address/ where HMP_address can be any of the following: the hostname address, the IPv4 address, the IPv6 address.

Note Notes:
  • Briefly press and release the HMP blue button to trigger On Screen Display (OSD) which displays these addresses.
  • The HMP350 and HMP300 devices can also be accessed via the HTTPS protocol.

Hostname address

  • {Serial_Number} represents the serial number of the HMP, for example http://spx-hmp-001d502000b2.local/
  • The hostname address of the HMP cannot be changed.
  • Bonjour has to be installed on your computer to use this address. Note that installing Elementi / HMD will automatically install Bonjour as well. On Mac OS X, Bonjour™ is already installed as part of the operating system.
  • To avoid a common behavior of some browsers which try "guessing" the URL by adding "www." at the beginning and / or ".com" and the end of the URL when the address is not reachable, make sure to type http at the beginning or add a trailing dot (period) at the end of the URL (i.e. http://spx-hmp-{Serial_Number}.local./ )

IPv4 address
  • Four octets IPv4 address written as decimal numbers, ranging from 0 to 255, separated by a dot / full stop.
  • The HMP is configured by default to use DHCP, so its IPv4 address is allocated automatically by the DHCP server. If there is no DHCP server found or there is an IP conflict or the network link is not detected, then IPv4 address of the HMP is auto-configured in the range -
  • Example:

IPv6 address

  • Link-local IPv6 address to use on Windows Vista or later. Example: http://[fe80::21d:50ff:fe10:0014]/

Note Note:
The {XX:XXXX} notation above needs to be replaced with the the last six digits of the serial number of the HMP.

HMP internal web servers

On HMP350 and HMP300

There are two internal web servers running on the HMP350 and HMP300 devices, accessible using HTTP / HTTPS:

  1. http(s)://HMP_address/
    A web server running on TCP port 80 / 443, providing access to player web interface, HMP status or RPC interfaces.
  2. http://HMP_address:81/, respectively https://HMP_address:9802/
    A WebDAV-enabled web server running on TCP port 81 / 9802, providing access to the content stored on the HMP.
Note Note:
The access to these interfaces can be password protected from the "Security" page in User manager tool.

On HMP200, HMP130, and HMP100

There are two internal web servers running on the HMP200, HMP130, and HMP100 devices, accessible using HTTP:

  1. http://HMP_address/
    A web server running on TCP port 80, providing access to HMP Wizard, HMP Control Center, Fusion, HMP status or RPC interfaces.
  2. http://HMP_address:81/
    A WebDAV-enabled web server running on TCP port 81, providing access to the content stored on the HMP.
Note Note:
The access to these interfaces can be password protected from the "Security" page in HMP Control Center.

Remote access

Remote access to the HMP on the relevant Ports can be done via simple port mapping on your router. Ensure you are using the correct protocol for the port (TCP/UPD). For managing multiple HMPs behind a NAT router, Port forwarding must be employed, as the access ports on the HMP cannot be changed.

There are different ways to control an HMP behind a Firewall:

  1. Use the HMP Pull mode to update contents and to retrieve monitoring and accounting logs. For extended functionality, you can use an RPC Concentrator.
    • pro: secure, easy to set up, no extra costs
    • con: allows only indirect access, needs access to a Web server
  2. Set up a VPN so that from your PC you have access to the HMP local network
    • pro: very secure, allows direct access
    • con: more complex to manage, may require extra hardware (VPN server)
  3. Forward ports 80,81 to the internal IP address:
    • Pro: easy to reach from anywhere
    • con: security issues, the HMP is exposed to any Internet threat

Dynamic DNS

Dynamic DNS is typically implemented by router devices and is not natively supported by the HMP.

  • Devices from Netgear, among others, support built-in dynamic DNS. These were not tested by SpinetiX.

A software alternative to dynamic DNS is to do the following:

  1. Add a JavaScript code to your project that uses the getURL function to make a request to an external page (e.g. your server).
    • This code will be executed each time the HMP starts (and implicitly the project), therefore each time the HMP has a new IP.
  2. On your web server, write a script (php or similar) that analyses the HTTP headers sent by HMP and logs somewhere the IP and the serial number of the HMP.
  3. Having the serial number of your HMP, lookup the currently assigned IP in that log.
This page was last modified on 15 November 2018, at 10:32.