DIVUS HEARTBEAT user manual .
29
3.13
SETTINGS NETWORK SETTINGS PAGE
The network settings for the home LAN or the RIN can be changed here if necessary. If you already chose the
correct settings during the first
r
3.13.1
DHCP
3.13.1.1
DSI
For the DIVUS HEARTBEAT to automatically manage a network also when changes are applied to the network
structure, it is mandatory to use DHCP and to avoid using static IP addresses for the DSI network. Although it is
possible to use fixed addresses, we strongly recommend not to use them. The role of DHCP server can be
assigned to the DIVUS HEARTBEAT, but it will automatically pass that role to another device if such a device is
detected. For this reason, the DIVUS HEARTBEAT continuously listens on the network for third-party DHCP activity
both when it is playing the DHCP server role and when it is itself a DHCP client of another device running a
DHCP server. This allows the DIVUS HEARTBEAT to switch roles as required. From server to client if another server
is there, from client to server if a previous server does not respond anymore.
3.13.1.2
RIN
1.
One single device connected to the Residential Intercom network
In this case, the best solution is to set the
address on the device (e.g. 192.168.69.10)
2.
Two or more devices connected to a DIVUS MANAGED SWITCH on the RIN
The address of t
A.
Manual configuration
will make
all devices reachable. Of course, all devices must be set to DHCP mode. Pre-requisite is
that no other device has a running DHCP service in the RIN. After activating the DHCP
server checkbox you will be required to define the range of addresses. Keep in mind that
the address of the manager (IP address field), the net mask field and the DHCP range fields
are all related and are checked to be correct on submission. The Gateway address field
may be left empty.
B.
Another device has a running DHCP service. In this case
activate the DHCP client function, making all the devices
reachable. Of course, all devices must be set to DHCP mode.