BGP aggregate addresses posted 08/09/2007
- Subject: BGP aggregate addresses
- From: "Patrick Galligan" <pgalligan@xxxxxxxxx>
- Date: Fri, 10 Aug 2007 13:57:33 +1000
- Dkim-signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:to:subject:mime-version:content-type:content-transfer-encoding:content-disposition; b=KyzzUOn8BaDqgSL6rHl5b9Q/fIk+ce5atilGNhl4FihLPXnieCL7xsRzQTGikbmKWQQmAETv8r2WYXS83aHvpaMNxGokLR9svCCp/b/4ccukVKupmSVsvJyTDTdAIItCnYPRBPkEsAQUJCRNkh7o5XgDuU97bSVG5FLlXVK3a2Q=
- Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:mime-version:content-type:content-transfer-encoding:content-disposition; b=nZ2cUlOmr7SxJHaozfLZNvJ6dEi6NhRUeuLeJ0MB7+BJOyedlgKgmavuiF1NYIOmFvBmg8YpaUX3b9/Ud2MrYqgVSDlZqmheeHQ4KyPxSUuD6NbLxzrJbXzvQQ2yIkUIeLJ4kKsX1lx0Fo1gGHtAp8mSQPnpbTmYPcmLtUvb2hQ=
My understanding of BGP aggregate addresses is that it will advertise
the aggregate if there is at least one network within the aggregate in
the BGP table. However, I have the following problem:
I am aggregating 10.64.192.0/19 from an iBGP peer which is a route
reflector client. It has loopbacks within this range, eg
10.64.200.1/24, but the aggregate only gets advertised if
10.64.192.0/24 is in the BGP table. Is this normal behaviour?
You can't cheat death forever, but you can make the b!stard work for it.