Skip to main content

Manage Peplink WAN performance

BoatKit can connect to a Peplink router on the vessel LAN, keep a DHCP reservation for the BoatKit host, and run short download tests through individual WAN connections. You can gather history in observation mode first, then separately allow BoatKit to move tested connections between the Peplink priority tiers you choose.

This is an advanced local-network integration. It uses the long-standing API used by Peplink's local web administration portal because Peplink's published Device API does not provide the required outbound-policy and LAN configuration operations. Confirm behavior after Peplink firmware changes before relying on automatic priority management.

Before you start

You need:

  • A dedicated BoatKit device on the same reachable LAN as the Peplink router
  • Vessel administrator access in BoatKit
  • A dedicated local Peplink administrator account
  • At least one enabled Peplink WAN connection
  • Internet access on each WAN you want to test

BoatKit runs iperf3 in the vessel runtime. The target picker contains Leaseweb's published worldwide speed-test locations. When you open the settings panel, BoatKit makes a lightweight TCP handshake to each target, sorts reachable locations by latency, and marks the closest result as recommended. This probe does not run a speed test. BoatKit automatically allocates and maintains the narrow test routing needed to measure each visible, enabled WAN separately.

Tests consume metered data

Each test is a real download. BoatKit stops a test as soon as one complete interval reaches the global minimum acceptable rate, or after about ten seconds. Choose a conservative threshold and interval for cellular or satellite plans.

  1. Open Settings, then Integrations.
  2. Select Add Integration.
  3. Open Network Management, find Peplink, and select Add.
  4. Open the added Peplink integration and enable it.
  5. Enter the router's local hostname or IP address and local administrator username.
  6. Enter the password. BoatKit validates the candidate credentials before saving them.
  7. Confirm that the panel reports Connected and lists the router's WAN connections.

The password is a write-only device secret. Viewer clients cannot retrieve it, and portable BoatKit backups do not include it. Changing the router address or username clears the saved password so BoatKit cannot send an old credential to a different endpoint.

When the integration is enabled, BoatKit reconnects with the saved credentials at startup and refreshes the connection and WAN inventory periodically. If Peplink is still starting or temporarily unreachable, BoatKit retries automatically with a bounded backoff. Validate and refresh remains available as an immediate manual retry.

Reserve BoatKit's LAN address

The BoatKit Static IP section shows the source IP and hardware address of the interface the operating system actually uses to reach Peplink.

  1. Enter the private IPv4 address that Peplink should reserve. The current address is offered initially.
  2. Select Ensure reservation and confirm the router change.
  3. Confirm that BoatKit reports the reservation as present or created.

BoatKit reads the complete untagged LAN profile immediately before the change, preserves fields it does not own, and changes only the matching DHCP reservation. It refuses to use an address already reserved for a different MAC address. It also refuses to stage the edit while Peplink has another unapplied configuration change, because the Peplink apply operation commits the router's shared staged configuration.

If you choose an address different from the current lease, BoatKit may continue using the old address until its lease renews or the host network is restarted. Plan that transition so it does not interrupt active work aboard.

Configure performance testing

Choose the settings shared by the performance manager:

  • iperf3 test host: a worldwide Leaseweb target. The list is sorted by the latest lightweight latency probe from the BoatKit host.
  • Minimum acceptable download: the global Mbps threshold that can end every WAN test early.
  • Maximum test duration: the per-WAN cap, including the one-second warm-up. The default is five seconds, and the available range is 2 through 60 seconds.
  • Normal priority: the global Peplink connection-priority tier 1 through 4 after an acceptable result.
  • Low-bandwidth priority: the equal or lower global Peplink tier used after a low or failed result.

The connection board mirrors Peplink's priority layout: enabled WANs are grouped by their current tier, disabled WANs are grouped separately, and each row shows Peplink's live connection message plus a 30-day speed-history tape with axes and point details on hover. Peplink's hidden cellular child slots, such as names ending in /1, are not separate WAN rows.

Select Run tests now for an initial cycle. BoatKit automatically assigns and maintains the per-WAN test routing before each cycle. It repairs stale or conflicting internal assignments and never creates assignments for hidden or disabled WANs. BoatKit refuses to edit outbound policy when another administrator has left unapplied Peplink changes.

Tests run sequentially so they do not compete for the vessel connection or the public test server. A test still stops as soon as a complete interval meets the acceptable-download threshold; otherwise, it runs until the configured maximum duration. Each result updates the small history chart for that WAN and is also retained in BoatKit's time-series history.

Start in observation mode

After a manual test works:

  1. Set Maximum time between tests. The default is six hours.
  2. Set Movement test trigger. The default is ten statute miles.
  3. Enable Scheduled performance testing and confirm the metered-data warning.
  4. Leave Automatic priority enforcement off while you gather enough history to trust the threshold and target.

BoatKit starts a cycle when either the interval expires or the vessel has moved the configured distance since the last attempt. Finishing an attempt, including one stopped by a router or test error, resets both triggers so a persistent failure does not consume data every minute. Simulated or quarantined positions do not trigger a movement-based test. Time-based testing still works when a trusted position is unavailable.

Observation mode records the same results and history without changing WAN priorities. When the results look reliable, enable Automatic priority enforcement. An acceptable result then restores the global normal tier, while a low result or failed test selects the global low-bandwidth tier. Peplink applies connection-priority changes immediately; this tier change does not share the staged configuration transaction used by LAN and outbound-policy edits. Turning scheduled testing off also turns enforcement off.

History, backups, and removal

The panel shows recent download results for every WAN. The measurements live in BoatKit's ordinary time-series history and follow the time-series backup policy you selected.

Portable configuration backups include nonsecret settings such as the Peplink address, username, desired reservation, schedule, target, managed test routing, thresholds, and priority choices. They omit the password. Discovered WAN inventory, the last-test scheduling cursor, and the installed-rule reconciliation marker are device-local and are rebuilt from the attached router after restore.

Removing the integration clears its saved password, BoatKit-side router settings, WAN policy choices, and device-local inventory. It does not delete DHCP or outbound rules already applied on the Peplink; remove those in the Peplink local administration portal if they are no longer wanted.

Troubleshooting

Credentials are rejected

Confirm the address opens the intended Peplink local portal and that the account is a local administrator. Changing the address or username clears the password, so enter it again after either change.

BoatKit refuses a LAN or outbound-rule change

Open the Peplink local portal and apply or discard its pending configuration first. BoatKit will not combine its change with an unrelated staged change.

A test reports that iperf3 is missing

Use a current BoatKit vessel-runtime image. App-hosted vessels do not run this integration, and older custom images may not contain the iperf3 executable.

Results vary between cycles

Public speed-test servers are shared, and mobile or satellite links naturally vary. Treat a single result as an operational signal rather than a carrier-grade benchmark. Choose a minimum that reflects usable onboard service and confirm repeated demotions before lowering a WAN permanently.


Peplink is a trademark of Peplink. Leaseweb is a third-party public test service. BoatKit is not affiliated with, certified by, or endorsed by Peplink or Leaseweb.