Known Limitations

Known Limitations

These limitations describe the current implementation and operating model. They are not automatically defects.

Transport Limitations

• Egress is UDP-only.
• Plain UDP ingress has no built-in authentication.
• Unix-domain control is POSIX-only.
• UDP does not guarantee delivery.

Routing and Control Limitations

• Runtime routing state is process-local.
• Runtime routing changes are non-persistent.
• There is no automatic config-file reload.
• There is no dynamic ingress or egress adapter creation.
• There is no multiprocessing coordinator.
• There is no IPC synchronization.
• There is no distributed control plane.
• There is no HTTP/TCP control API.
• There is no application-level control authentication.
• There is no automatic stale-update retry.

AIS and Domain Limitations

• There is no geographic filtering.
• There is no MMSI or vessel-type filtering.
• There is no spoof detection.
• There is no long-term AIS storage.
• AISMixer can supply normalized AIS streams to maritime-domain-awareness systems, but it does not itself perform analytics or produce an operational maritime picture.
• AISMixer supplies stream-processing infrastructure; it is not itself a complete vessel-tracking or maritime-surveillance application.

Operational Limitations

• The installer/systemd path does not yet provision the control socket runtime directory.
• aismixerctl is not yet installed globally by the current installer.
• Socket permissions are operator-managed.
• There is no persistent routing rollback history.
• Debug output is not a tamper-resistant audit trail.

See Operations and Deployment, Security Model, and Runtime Routing Control.