Skip to content
New issue

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

Group flows by AS CIDR prefix #1230

Open
fujiapple852 opened this issue Jul 22, 2024 · 0 comments
Open

Group flows by AS CIDR prefix #1230

fujiapple852 opened this issue Jul 22, 2024 · 0 comments
Labels
enhancement New feature or request

Comments

@fujiapple852
Copy link
Owner

fujiapple852 commented Jul 22, 2024

With ECMP routing we get multiple paths

Consider a path from A to C via Bn:

A > B1 > C
A > B2 > C
A > B3 > C

With ECMP, typically these Bn hops will share an AS with a given CIDR prefix. Consider the following Bn hop from a trace for AS13335 (CLOUDFLARENET, US) which has CIDR prefix 141.101.71.0/24:

AS13335 141.101.71.97 [11.8%]
AS13335 141.101.71.95 [8.8%]
AS13335 141.101.71.47 [17.6%]
AS13335 141.101.71.93 [11.8%]
AS13335 141.101.71.91 [8.8%]
AS13335 141.101.71.63 [14.7%] 
AS13335 141.101.71.2 [5.9%]
AS13335 141.101.71.105 [8.8%]
AS13335 141.101.71.107 [5.9%]

Today, when calculating flows, Trippy treat each Bn as independent and thus separate flows. This is problematic when there are several hops with ECMP (as is typical in large cloud and CDN providers) as the combination of possible paths becomes very large. i.e. consider a path with 5 hops, 3 of which have 10 ECMP paths (i.e. A > B(n) -> C(n) -> D(n) -> E where N is 10).

In such cases it may be useful to allow flows to be combined based on the AS CIDR prefix.

@fujiapple852 fujiapple852 added the enhancement New feature or request label Jul 22, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant