You can connect Remote and Speaker Stations on one of the Digital Intercom Lines, point-to-point to a Main Station or
Ethernet interface module (HLI-ET2) over an IP network.  Pairing to a Main Station over an IP network requires an Ethernet interface module fitted to the extension bay of the Main Station (HLI-ET2).
Note: If you change the network topology between any two stations, you must reboot the stations.
Note: If the IP address on a Remote Station or Speaker Station changes, you must either reboot the Remote Station or disable and then re-enable the DHCP on the Remote Station.
Warning: Digital intercom lines and the Ethernet connections are mutually exclusive on Remote and Speaker Stations.
If both are connected it will be detected as a fault, communication over both ports will stop and both status LEDs will blink
RED. This requires a reboot of the station using Administration > Reset > Reboot
Warning: When changing the connection from digital intercom line to Ethernet or vice-versa, you must disconnect one cable
and then wait until the unit has detected a loss of connection before connecting the other cable. Otherwise, they will briefly be
detected as both connected.
Warning: When changing the power connections to a Remote Station, a *network storm error message may appear. If so,
disconnect the power cable, and reboot the Remote Station.

*Ethernet network traffic is classified as unicast, multicast, or broadcast traffic. Unicast traffic refers to a message being sent directly from one Ethernet device to another Ethernet device on the network. Multicast traffic refers to when one Ethernet device sends a message to a specific group of Ethernet devices. Broadcast traffic refers to one Ethernet device sending a message to all other devices on the network. All three types of Ethernet traffic are common to any Ethernet network and are essential to the proper operation of the Ethernet network. However a problem can arise when excessive broadcast traffic results in a broadcast storm.
Broadcast traffic by itself is a normal part of Ethernet network communications. One example of Broadcast traffic is the Address Resolution Protocol (ARP) message. Ethernet devices use ARP messages to resolve their IP addresses on the network. Broadcast storms happen when a network is saturated with a large volume of broadcast traffic. They can occur for a short duration or for an extended period of time. Broadcast storms consume precious resources from every Ethernet device on the network. This is because every device needs to queue the broadcasts to be processed. Ethernet devices will also have to queue broadcast protocol messages that they do not support. In an Ethernet network, broadcast storms need to be reduced in order to minimize unnecessary CPU usage
and to keep the network operating properly.