Skip to content

Fragment routing

Enable Fragment

Open Routing → Smart Routing → Edit, or edit an ordinary Custom route, and enable Fragment. Each route stores its own switch, off by default. All via VPN does not use it.

OneXray adds a freedom helper tagged fragment. Newly generated defaults use streamSettings.finalmask.tcp with type: fragment and settings packets: tlshello, length: 100-200, delay: 10-20. Entry nodes use this helper for the underlying connection. Fragment is optional and does not guarantee reachability.

Smart Routing keeps the final-exit chain final exit → entry → fragment; balancing still selects complete chains. Windows and Linux bind the helper’s physical socket to the selected interface.

Saved and advanced configurations

An ordinary Custom document has 1–3 leading empty entry slots and may include the freedom/fragment helper, followed by the controlled dnsOut helper when other DNS queries explicitly use direct/empty answers. Imported Fragment parameters survive edits to other fields.

An Advanced Custom template owns its helper parameters. A freedom outbound tagged fragment enables entry wiring; Freedom helpers can use streamSettings.finalmask, while node transport/security and physical-interface overrides remain outside the template’s managed boundary.

Existing settings.fragment and settings.noises remain authored data and are not batch-migrated. Creating a new default helper, including turning Fragment off and back on, uses FinalMask. Raw and provider configurations keep their own chains; the tag alone does not create wiring there.

Ordinary Custom Routing · Advanced templates · Raw JSON

Last updated on