Illustrative scenario. A yacht berthed in Porto Cervo hosts a family while the crew handles bookings and documents. Two TVs stream video and several phones upload photographs. A speed test looks promising, but a work call becomes difficult when everyone uses the connection at once.
Separate access before allocating bandwidth
In this example, guests and crew work devices have separate networks. Administration of routers, access points and other equipment remains restricted. Define the destinations each group may reach. Navigation and safety-critical systems are outside this example: integrating them requires a specific assessment with the vessel's qualified specialists.
A VLAN identifies a logical network, but traffic between networks and between devices also needs control. The UniFi isolation documentation distinguishes gateway, switch and access-point controls. The design must follow actual traffic paths, including any wired sockets accessible to guests.
Priorities do not create additional capacity
Quality of Service, or QoS, manages traffic priorities and limits. Peplink describes policies for applications and user groups; available features need checking against the actual model and firmware. The aim in our example is to keep a non-urgent upload from consuming all available resources while crew members work.
There is no universal number of megabits to assign per cabin. First measure download and upload performance in the intended operating conditions and agree which activities take priority. If the connection's capacity falls, prioritisation can allocate what remains; it cannot guarantee capacity the connection does not provide.
A test that resembles life on board
- Establish a baseline. Record the active connection, test location and connected devices. Make a test call without other traffic.
- Add the expected load. Start the TVs and an authorised upload on the guest network, after checking the data allowance.
- Repeat the priority task. Assess the call and access to work services; record interruptions and slowdowns.
- Check access. From a guest device, verify that crew files and administration panels cannot be reached.
- Test alternatives. If a second connection exists, repeat the test on it. Results in port do not establish performance along every route or at every anchorage.
A handover that survives a crew change
The operating sheet should explain which network to use, who can change priorities, how to check data consumption and how to revoke guest access. A metered connection also needs alert thresholds and assigned responsibility. Discovering an exhausted allowance when the connection is needed is too late.
Our marine connectivity service starts with actual onboard use. Prepare the device inventory, available connections and areas requiring coverage. For each connection, check coverage and contractual usage conditions separately.
