Raymarine RNS-8, Manual, Page: 59 / 66

Appendix A Ethernet (IPv4) networking of
Raymarine devices with third-party products
Raymarine uses a custom Ethernet (IPv4) networking configuration. Use
the following information to help you understand how Raymarine’s Ethernet
(IPv4) implementation interacts with third-party Ethernet (IPv4) devices on
your vessel, such as routers, switches, Access Points (APs) etc.
Important:
• Third-party networking products such as routers, switches, and Access
Points (APs) may work when connected to Raymarine networks, when
configured correctly. However, correct operation is not guaranteed. It’s
important to refer to the instructions provided by the relevant third-party
device manufacturer, to ensure that your intended use of a third-party
device is consistent with the device’s design intent.
• Raymarine does not warrant that Raymarine products are compatible with
products manufactured by any person or entity other than Raymarine.
• When using third-party products in your Raymarine electronics network,
you should be aware of, and understand, the concepts and limitations
described in the following Disclaimer:
p.7 — Disclaimer
Overview
• Ethernet (IPv4) networking is a method for interconnecting multiple
electronic devices, allowing many devices to function in a network and
share data using only a single RJ45 or RayNet connection for each device.
• In order to function correctly, every Ethernet (IPv4) device (whether
Raymarine or third-party) must have a unique IP address allocated to it, and
it must not conflict with that of any other device.
• IPv4 addresses can be centrally-allocated to devices either automatically ,
using a method known as DHCP (Dynamic Host Configuration Protocol), or
manually (i.e. allocated a static IP address). The most common method for
allocating IPv4 addresses on vessel electronics networks is DHCP . In this
configuration, the server device is known as a DHCP server .
Client / Server device Example(s)
Raymarine IPv4 DHCP client • Radar scanner (e.g. Quantum )
• Sonar module (e.g. CP470 )
• IP camera (e.g. CAM300 )
Raymarine IPv4 DHCP server and
self-addressing device
• Multifunction display (MFD /
Chartplotter), running LightHouse
3 or LightHouse 4 (e.g.
Axiom )
• Marine Router (e.g. YachtSense
Link Router )
Third-party IPv4 DHCP client
IP camera
Third-party IPv4 DHCP server • Router
• Switch
• Access Point (AP)
Note:
The DHCP server maintains a pool of IP addresses and “leases” an address
to any DHCP-enabled client, when the client device first powers up and
announces its presence on the network. Because the IP addresses are
dynamic (leased) rather than static (permanently assigned), addresses no
longer in use are automatically returned to the DHCP server’s pool, for
subsequent reallocation.
It’s also possible to have multiple DHCP servers issuing addresses on an
IPv4 network, but to avoid addressing conflicts, all DHCP servers must be
carefully configured to only allocate IP addresses in distinct address ranges.
The
subnet mask must also be carefully configured, to ensure that devices
can correctly communicate with one another.
Implementation
• Raymarine Ethernet (IPv4) devices expect to use a private Raymarine IPv4
network , which is designed to be internal to the vessel only. Raymarine
has carefully chosen a specific IP address range ( 198.18.0.0/21 ) to ensure
that it does not interfere with any external IP address ranges, or other
legacy and real-world addressing constraints (including but not limited
to marina Wi-Fi networks).
Ethernet (IPv4) networking of Raymarine devices with third-party products
59