unfortunately, the actual data as paths can differ
133.10.0.0 2914 2907 133.11.0.0 2914 2907 2501 155.162.0.0/15 2914 155.164.0.0/14 2914
so, what i would like is a tool which takes something like the latter syntax and tells me what the origin ass could aggregate. i.e. i am specifically not inclined to proxy aggregation at this point.
So in this case, all you'd get back is:
133.10.0.0 2914 2907 133.11.0.0 2914 2907 2501 155.162.0.0/15 2914 155.164.0.0/14 2914
because the origin AS for each block couldn't aggregate the above blocks further?
correct.
What is CIDRadvisor? A lookup in some search engines doesn't turn up anything...
part of RAToolset randy
I once started a project that would do this, which would allow realtime aggregation by speaking ebgp to a router. I've not had time to play with it too much, but it does bring up a bgp session and receive routes properly. If I ever finish it, I'll run it and put up a telnet/http interface to it. I would also check out Tony Bates CIDR report, as you can do interesting things with that data, it will tell you if you can aggregatte better. - jared On Sat, Nov 28, 1998 at 09:06:57PM -0800, Randy Bush wrote:
unfortunately, the actual data as paths can differ
133.10.0.0 2914 2907 133.11.0.0 2914 2907 2501 155.162.0.0/15 2914 155.164.0.0/14 2914
so, what i would like is a tool which takes something like the latter syntax and tells me what the origin ass could aggregate. i.e. i am specifically not inclined to proxy aggregation at this point.
So in this case, all you'd get back is:
133.10.0.0 2914 2907 133.11.0.0 2914 2907 2501 155.162.0.0/15 2914 155.164.0.0/14 2914
because the origin AS for each block couldn't aggregate the above blocks further?
correct.
What is CIDRadvisor? A lookup in some search engines doesn't turn up anything...
part of RAToolset
randy
-- Jared Mauch | pgp key available via finger from jared@puck.nether.net clue++; | http://puck.nether.net/~jared/ My statements are only mine.
participants (2)
-
Jared Mauch
-
Randy Bush