YachtByte Official Resource
Fault boundary
- Affected network identified: guest, crew, owner, AV/control, CCTV, technical, bridge-adjacent or OT.
- Wired and wireless impact compared.
- One device, one area, one VLAN or whole-yacht impact recorded.
- Recent changes, support sessions, WAN failover, shore-power event or reboot recorded.
- Bridge, captain or duty officer informed where operationally relevant.
Addressing check
- Affected device IP address recorded.
- Gateway recorded.
- DNS server recorded.
- SSID or switch port recorded.
- VLAN or subnet checked against the IP plan.
- `169.254` or missing gateway condition noted where present.
- Known-good comparison device checked where available.
Connectivity check
- Gateway reachability tested.
- Public IP reachability tested where policy allows.
- Local service reachability tested.
- Firewall or router WAN status checked.
- SD-WAN, Starlink, VSAT, 5G/LTE or marina Wi-Fi status checked only after local tests.
- Result recorded before reboot or reset.
DNS check
- Public name resolution tested.
- Internal name resolution tested where used.
- DHCP-provided DNS server tested.
- Firewall DNS proxy or resolver status checked.
- Upstream DNS forwarder checked.
- Temporary DNS change recorded with approval and rollback note if used.
DHCP check
- Authoritative DHCP server identified.
- Scope enabled status checked.
- Lease pool exhaustion checked.
- Reservations and conflicts checked.
- DHCP relay or helper address checked where used.
- Duplicate or rogue DHCP source considered.
- Guest network lease time reviewed where device count is high.
Closeout
- Root cause or likely cause recorded.
- Temporary action recorded.
- Permanent corrective action assigned.
- IP plan, DHCP scope, DNS record or firewall notes updated where needed.
- Logs, screenshots and test results stored.
- Captain or management summary provided in plain language.