warm at stack.ru
Mon Apr 26 03:45:18 CEST 2004
For example I get 220.127.116.11/24, 217.29.81/24, 18.104.22.168/25 and 22.214.171.124/25. Each subnet should be route to its own gateway. I redistribute this routes and I want redistribute their by aggregated blocks : 126.96.36.199/23 and 188.8.131.52/24 becouse they both (or four not aggregated) are routed though me for my customers :-). Customers want to get routes to know subnets for which traffic is very chip. As I said befor 130-150 routes can be aggregated to 20-50 - depends on weather ;-).
It is not a real problem for to have 150 routes, but my customers ask me to reduce numbers of routes. Finaly I can stand them befor the fact of 150 routes, but I try to find more clever way.
From: Бохонкович Юрий [mailto:byg at center-f1.ru]
Sent: Friday, April 23, 2004 6:31 PM
To: Zharovtsev, Anton
Cc: bird-users at bird.network.cz
Subject: Re: Routes aggregation
On Fri, 23 Apr 2004, Zharovtsev, Anton wrote:
> Have anyone some ideas how to aggregate routes ?
> May be it possible whith a filter ?
I guess so.
> ip ro sh | wc -l
> And I want redistribute their aggregated. I don't know how.
I didn't catch this what's wrong with routes?
WBR, Yury Bokhoncovich, Senior System Administrator, NOC of F1 Group.
Phone: +7 (3832) 106228, ext.140, E-mail: byg at center-f1.ru. Unix is like a wigwam -- no Gates, no Windows, and an Apache inside.
More information about the Bird-users