We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Trippy currently supports a subset of the combinations of protocol, src and dest ports, and ecmp modes. These are set using the following parameters:
-p, --protocol <PROTOCOL> Tracing protocol [default: icmp] [possible values: icmp, udp, tcp] -P, --target-port <TARGET_PORT> The target port (TCP & UDP only) [default: 80] -S, --source-port <SOURCE_PORT> The source port (TCP & UDP only) [default: auto] -R, --multipath-strategy <MULTIPATH_STRATEGY> The Equal-cost Multi-Path routing strategy (IPv4/UDP only) [default: classic] [possible values: classic, paris, dublin]
These are modelled using the TracerProtocol, PortDirection and MultipathStrategy types.
TracerProtocol
PortDirection
MultipathStrategy
The goal is to unify these types and provide a simpler set of parameters.
For IPv4/UDP the supported combinations are:
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Trippy currently supports a subset of the combinations of protocol, src and dest ports, and ecmp modes. These are set using the following parameters:
These are modelled using the
TracerProtocol
,PortDirection
andMultipathStrategy
types.The goal is to unify these types and provide a simpler set of parameters.
For IPv4/UDP the supported combinations are:
The text was updated successfully, but these errors were encountered: