The DataHub is a feature-packed device that supports connecting to various communications devices via Wi-Fi and Ethernet and to your boat instruments through the NMEA2000 network.
The DataHub includes two Ethernet ports and has two Wi-Fi networks, one 2.4 GHz and one 5 GHz network. The Ethernet ports are labelled LAN and WAN.
The LAN port is designed to connect to a device such as a laptop. The WAN port is designed to connect to an Internet communications device, such as a cellular modem router, Starlink or GO exec.
By default, the DataHub Wi-Fi on the 5Ghz network is provided for your onboard devices to connect to. This leaves the long-range 2.4Ghz Wi-Fi available for connecting to marina Wi-Fi, a Wi-Fi hotspot, Starlink, the Iridium GO! or GO exec.
DataHub Internet Routing priority
By default, the DataHub will route Internet requests by priority through:
The WAN port
2.4 GHz Wi-Fi
USB-tethered devices, first iOS, then Android
If you have Starlink, an Iridium GO! or GO exec connected, the DataHub will automatically route first via Starlink, then via any USB-tether devices, and then via the Iridium GO! or GO exec. It makes no difference whether Starlink or GO exec are connected via Ethernet WAN or 2.4 GHz Wi-Fi. The DataHub will always prioritize Iridium connections last.
DataHub System Profiles - why use them?
Most customers find the default Ethernet port and Wi-Fi network arrangements suitable for connecting their devices. In some circumstances, however, activating a custom System Profile to reprogram the Ethernet ports or Wi-Fi network to support the devices and use case you have on the boat can be helpful.
Below is a guide to the various System Profiles available for Starlink, with examples of when you might consider using them.
Important Note: Using Starlink profiles is only required if you are in an area with high Starlink usage and congestion. During times of peak load, Starlink may deprioritise PING traffic.
This means the DataHub PINGer, which informs the Internet Status widgets, may not be able to detect a Starlink internet connection to the DataHub.
Using the Starlink Profiles disables the DataHub PINGer and instead instructs it to assume the connection is always active if there is a network connection, so it will always try Starlink first.
Since regular internet traffic is not sent via PING, it will continue to flow as usual, though in a congested area you may notice degraded internet speeds.
In the picture below, you can see the DataHub Internet Status PINGer for Ethernet WAN is GREEN with Status: Online. This means the DataHub can PING via the Ethernet WAN port:
When the DataHub cannot detect an internet connection via Starlink it will attempt to fall over to other devices such as cellular or Iridium.
If the PINGer cannot detect the internet, the Ethernet WAN widget will be coloured RED with the Status: Offline.
How to activate System Profiles
To activate a system profile:
Log into the DataHub via your web browser on 10.10.10.1
Click on Settings, then click the top menu Profiles.
Click on the red INSTALL button next to the profile name and allow 30 seconds for it to be applied.
If you get stuck, install the resetNet profile to revert the DataHub to its default configuration.
Starlink specific Profiles
SLonWAN profile - When Starlink stops working via WAN
Activating this profile will route Internet data first via the Ethernet WAN port with the least-cost fallover to other interfaces, prioritising 2.4 GHz Wi-Fi first, then USB-tethered mobile devices.
The SLonWAN profile is helpful for customers who:
Have Starlink connected to the DataHub Ethernet WAN port, with either an Iridium GO! or GO exec connected to the 2.4 GHz DataHub Wi-Fi and a mobile phone connected with USB-tethering to share cellular Internet.
SLonWAN+Iridium GO - When Starlink stops working via WAN and you have an Iridium GO! or GO exec too
Activating this profile will route first via the Ethernet WAN port, with the least cost fallover to an Iridium GO! or GO exec only via DataHub 2.4 GHz Wi-Fi. With this profile enabled, the DataHub will not fall over to other Wi-Fi-connected devices on 2.4Ghz or USB-tethered devices.
The SLonWAN+Iridium GO profile is helpful for customers who:
Have Starlink connected to the DataHub Ethernet WAN port, with an Iridium GO! or GO exec connected to the DataHub 2.4 GHz Wi-Fi.
SLonWWAN+Iridium GO
Activating this profile will route Internet data first via the DataHub 2.4Ghz Wi-Fi, with the least cost fall over to the Ethernet WAN port only when connected to a GO exec. With this profile enabled, the DataHub will not fall over to other Ethernet WAN or USB-tethered devices.
The SLonWWAN+IridiumGO profile is helpful for customers who:
Have Starlink connected to the DataHub 2.4 GHz Wi-Fi, with a GO exec connected to the DataHub Ethernet WAN port.
LAN2WAN2
Activating this profile will switch the DataHub LAN port into a WAN port. This means both the DataHub Ethernet ports are configured as WAN ports, meaning they will not offer DHCP and will receive it from connected devices.
The LAN2WAN2 profile is helpful for customers who:
Want to connect both Starlink and the GO exec via Ethernet to the DataHub.
Have a Peplink multi-sim router in addition to Starlink or the GO exec while keeping spare the DataHub 2.4Ghz Wi-Fi available to connect to marina Wi-Fi and DataHub 5 Ghz Wi-Fi to connect onboard devices.
When using the LAN2WAN2 Profile, we recommend connecting your fastest, highest-priority Internet source to the WAN port and your GO exec to the LAN port e.g. Starlink to WAN port, GO exec to LAN port.