Aggregate outgoing address.
santiago at crfreenet.org
Thu Nov 17 22:50:16 CET 2011
On Thu, Nov 17, 2011 at 08:54:46PM +0100, damkol at gmail.com wrote:
> See this example:
> Where two aggregate routes (A.B.C.0/24 and D.E.F.0/24) are
> Of course i seen this example, but i need to route 22.214.171.124/25 via
> and the rest directly connected in this /24 prefix.
In that case you keep the route 126.96.36.199/25 via 188.8.131.52 in static,
there is no problem with that. You can have both 184.108.40.206/25 and
220.127.116.11/24 in the table, also you can have the directly connected subnets
(but as they are usually already provided by OS, so it is usually useless
to have them in BIRD table).
The use of aggregate 'reject' routes is explained in the opening text in
the example, but perhaps not clear enough. (i see that it is not
mentioned in the example that the propagated routes in static_bgp proto
may be aggregates of subnets used in OSPF). I don't really see the
problem with that way in your case. Perhaps if you want to have some kind of dynamic
aggregation, it might be problem.
Elen sila lumenn' omentielvo
Ondrej 'SanTiago' Zajicek (email: santiago at crfreenet.org)
OpenPGP encrypted e-mails preferred (KeyID 0x11DEADC3, wwwkeys.pgp.net)
"To err is human -- to blame it on a computer is even more so."
-------------- next part --------------
A non-text attachment was scrubbed...
Size: 197 bytes
Desc: Digital signature
More information about the Bird-users