40-7705ii-UM
Page 26
Rev. 1 June 11, 2018
5.14
Suggested TCP/IP Settings for Second MultiNet Receiver
The table below shows some suggested settings for the TCP/IP devices in the second
MultiNet Receiver / 7170 IP-Link Transceiver pair of a dual system. These suggestions
should be appropriate for a network that is only made up of devices from a MultiNet
System. If you are connecting to an existing network, you must get these values from
the administrator of that network. Failure to get the proper values could prevent proper
operation of the MultiNet devices or other existing devices on the network.
Second 7705ii/ Suggested Ethernet Port Settings
Parameter
Ethernet Port 1 / eth0
Ethernet Port 2 / eth1
ONBOOT
Yes
Yes
BOOTPROTO
STATIC
STATIC
IPADDR
192.168.0.102
No Suggestion
NETMASK
255.255.255.0
255.255.255.0
GATEWAY
192.168.0.1
10.0.1.1
Second 7170 IP-Link Transceiver Suggested Ethernet Port Settings
IP Address
192.168.0.22
GATEWAY
192.168.0.1
NETMASK
255.255.255.0
Table 5-5 Suggested TCP/IP Settings for Second Receiver & 7170
5.15
A note on DHCP
DHCP is an acronym for Dynamic Host Configuration Protocol. This means IP
addresses are automatically assigned by a DHCP server on your network. Since the
MultiNet Receiver’s in a MultiNet system must have a unique static IP addresses, a
DHCP server would have to be configured to reserve and always provide the same
address to each specific receiver. Contact your IT department for additional
information. Do not use this option if you do not have a DHCP server on your network
or cannot configure it to provide static addresses to specific devices.
5.16
Configure TCP/IP, Linux Network Configuration:
As mentioned before, there are two Ethernet ports in the MultiNet receiver. The port
names are Ethernet Port 1 [eth0] and Ethernet Port 2 [eth1]. If you are using both ports,
you will need to enter the commands to configure each port separately.
Note that physical Ethernet connector labeled Port 1 is internally identified as eth0 and
that the Ethernet connector labeled Port 2 is internally identified as eth1. This is due to
a typical convention where components such as connectors are numbered beginning at
1 and a programmers’ convention that usually begin at 0.
