This message was posted by a user wishing to remain anonymous
Hi all, I'm working on a design challenge involving Starlink and Juniper SSR (Mist‑managed), and I'd appreciate insights from anyone who has dealt with real‑time traffic over LEO networks.
The environment
The goal
Maintain real‑time data integrity across unstable LEO links.
The challenge
On Juniper SSR, the usual way to protect real‑time traffic over unstable links is packet duplication (redundant service routes with redundancy: true). However:
-
Mist‑managed SSR does not support packet duplication
-
Mist does not expose the SSR configuration tree
-
SSH access only provides operational mode, not config mode
-
Mist overwrites any local config changes
So the usual SSR redundancy mechanisms are unavailable.
Are there any options with the Juniper Mist platform to counter this issue? Or going to Conductor is the only option for this?
If you need me to provide any further information to respond to this, let me know.
Many Thanks in advance.
-------------------------------------------