Raymarine QUANTUM 2 Installation Instructions Manual page 89

Note: Raymarine's IP address range is for local traffic within the
vessel's private Raymarine network only, and does NOT traverse
across Raymarine products to external networks, or to the Internet.
• In a Raymarine Ethernet (IPv4) network, IP addresses are self-allocated
by certain Raymarine equipment in the following range: 198.18.0.32 to
198.18.3.255 (inclusive). You must avoid placing any devices in this
range using manual (static) IP addresses.
• Whether your network includes only Raymarine Ethernet (IP) devices, or a
mixture of Raymarine and third-party Ethernet (IPv4) devices, you have 3
options for configuring the Ethernet (IPv4) network and managing the IP
addresses for your devices:
1. Use a Raymarine device as the sole DHCP server to allocate IP
addresses automatically to all Raymarine and third-party Ethernet
(IPv4) devices on the network. For the purposes of simplicity and
reliability, this is the recommended option for most vessels. The
following Raymarine devices can act as DHCP servers:
a. Raymarine multifunction display (MFD) / Chartplotter, running
LightHouse 3 or LightHouse 4; or:
b. Raymarine YachtSense Link Router
Note: If both a Raymarine MFD and YachtSense Link Router are
present in the same network, the YachtSense Link Router MUST be
configured as the DHCP server for that network. To facilitate this, the
Raymarine MFD's DHCP setting defaults to Automatic as standard. On
power up, if the YachtSense Link is detected in the RayNet system,
any MFDs in the network will disable their own DHCP Server, to
permit the YachtSense Link to manage the network's IP addresses.
Only Raymarine MFDs running LightHouse 4 are compatible with the
YachtSense Link Router. Additionally, the most recent versions of the
LightHouse 4 and YachtSense Link software must be used.
2. Use a third-party Ethernet (IPv4) device (such as a router or Access
Point) to allocate IP addresses automatically, as a sole DHCP server.
To do this, refer to the Configuring a third-party router as DHCP server
section, below.
Ethernet (IPv4) networking of Raymarine devices with third-party products
Note: Any Raymarine LightHouse 3 or LightHouse 4 MFDs will
still self-allocate their own IP address, even if a third-party DHCP
server is being used to allocate IP addresses to other Raymarine or
non-Raymarine DHCP client devices (Camera, Radar, Sonar etc.) on
the network.
3. Manually configure static IP addresses for your devices. The address
range 198.18.0.32 to 198.18.3.255 (inclusive) is used by Raymarine
equipment, and any other third-party equipment on the network should
not be set to a static IP address in this range. It should instead be set
elsewhere in the 198.18.0.0/21 range.
Adding third-party devices to your Raymarine Ethernet (IP)
network
• It is recommended that any third-party products connecting to a Raymarine
Ethernet (IPv4) network (e.g., a third-party IP camera) are configured as
DHCP clients, so that they automatically get allocated a correct IP address
within the range used by the Raymarine IPv4 network. If this is not
possible, (for example, in the scenario that your third-party IP Camera
requires a static IP address), you should configure the product to have
a static IP address within the following range: 198.18.0.1 to 198.18.0.31
(inclusive).
• Any third-party router in your network should be performing IPv4 Network
Address Translation (NAT) from the private address to another one on an
upstream interface.
Configuring a third-party router as DHCP server
In the scenario that you wish to use a third-party DHCP server to allocate the
IP addresses for your vessel's IPv4 network, use the following information
to help you configure the third-party DHCP server to work with Raymarine
Ethernet (IPv4) client devices:
1. Configure the third-party DHCP server / router to use Raymarine's subnet
details, which are as follows:
a. Set the DHCP server's IP address to 198.18.0.1
b. Set the netmask to /21, i.e. 255.255.248.0
c. Set the DHCP range from 198.18.4.0 to 198.18.7.254 (inclusive). If
this is not possible, ensure that the address range is smaller than this
(but within the range of 198.18.4.0 to 198.18.7.254 (inclusive)).
89