<Disclaimer> Please don't flame me if I am doing something wrong. Just tell me how to do it better. </Disclaimer> We are advertising 2 /20 which can be (theoretically) aggregated to one /19 route-server.cerf.net>sh ip bgp 200.62.0.0 BGP routing table entry for 200.62.0.0/20, version 5199340 Paths: (4 available, best #3) Not advertised to any peer 1740 4006 18747 198.32.176.25 from 198.32.176.25 (134.24.127.39) Origin IGP, metric 20, localpref 100, valid, external 1740 4006 18747 192.41.177.69 from 192.41.177.69 (134.24.127.131) Origin IGP, metric 20, localpref 100, valid, external 1740 4006 18747 192.157.69.5 from 192.157.69.5 (134.24.127.201) Origin IGP, metric 20, localpref 100, valid, external, best 1740 4006 18747 134.24.88.55 from 134.24.88.55 (134.24.127.27) Origin IGP, metric 20, localpref 100, valid, external route-server.cerf.net>sh ip bgp 200.62.16.0 BGP routing table entry for 200.62.16.0/20, version 5199341 Paths: (4 available, best #1) Not advertised to any peer 1740 4006 18747 192.157.69.5 from 192.157.69.5 (134.24.127.201) Origin IGP, metric 20, localpref 100, valid, external, best 1740 4006 18747 198.32.176.25 from 198.32.176.25 (134.24.127.39) Origin IGP, metric 20, localpref 100, valid, external 1740 4006 18747 192.41.177.69 from 192.41.177.69 (134.24.127.131) Origin IGP, metric 20, localpref 100, valid, external 1740 4006 18747 134.24.88.55 from 134.24.88.55 (134.24.127.27) Origin IGP, metric 20, localpref 100, valid, external route-server.cerf.net> The reason for doing this is simple: First /20 is in US, second /20 is in VE and I want to advertise Venezuelan part (and only this) to some local VE provider in addition to NetRail. If I would advertise aggregated /19 to NetRail, I would receive all traffic for this multihomed /20 only from second VE provider, as more specific advertisement would be preferred in route selection process. Maybe they are doing the same. Przemek -----Original Message----- From: owner-nanog@merit.edu [mailto:owner-nanog@merit.edu]On Behalf Of Omachonu Ogali Sent: Wednesday, February 21, 2001 9:56 AM To: Brandon Ross Subject: Re: Network for Sale On Tue, Feb 20, 2001 at 11:08:58PM -0500, Brandon Ross wrote:
On Tue, 20 Feb 2001, Nathan Stratton wrote:
On Tue, 20 Feb 2001, Roy wrote:
Sold???
360networks Snags NetRail
http://www.broadbandweek.com/newsdirect/0102/direct010220.htm
If they do I bet they don't know what they are getting into. NetRail still has a mess in the past that they need to clean up before they start fixing the current mess they have.
And exactly which part of your mess do you think I haven't cleaned up yet? Pray do tell.
Netrail's unnecessary deaggregated routes. BGP table version is 548878, local router ID is 216.74.127.225 Status codes: s suppressed, d damped, h history, * valid, > best, i - internal Origin codes: i - IGP, e - EGP, ? - incomplete Network Next Hop Metric LocPrf Weight Path --snip-- * 64.253.0.0/19 157.130.59.13 100 0 701 4006 i * 64.253.9.0/24 157.130.59.13 100 0 701 4006 i * 64.253.10.0/24 157.130.59.13 100 0 701 4006 i --snip-- Why announce two /24s terminating at the same AS out of the larger /19? --snip-- * 131.226.0.0/19 157.130.59.13 100 0 701 4006 i * 131.226.0.0 157.130.59.13 100 0 701 4006 ? * 131.226.32.0/19 157.130.59.13 100 0 701 4006 i * 131.226.64.0/19 63.211.88.5 100 0 3356 4006 i * 131.226.96.0/19 63.211.88.5 100 0 3356 4006 i * 131.226.128.0/19 157.130.59.13 100 0 701 4006 i --snip-- Why announce four /19s terminating at the same AS out of the larger /16? --snip-- * 205.215.0.0/18 157.130.59.13 100 0 701 4006 ? * 205.215.11.0 157.130.59.13 100 0 701 4006 i * 205.215.14.0 157.130.59.13 100 0 701 4006 ? * 205.215.36.0 63.211.88.5 100 0 3356 4006 i * 205.215.37.0 157.130.59.13 100 0 701 4006 i * 205.215.38.0 157.130.59.13 100 0 701 4006 i * 205.215.42.0 157.130.59.13 100 0 701 4006 i * 205.215.44.0 157.130.59.13 100 0 701 4006 i * 205.215.48.0 157.130.59.13 100 0 701 4006 i * 205.215.51.0 157.130.59.13 100 0 701 4006 i * 205.215.52.0 157.130.59.13 100 0 701 4006 i * 205.215.55.0 157.130.59.13 100 0 701 4006 ? * 205.215.56.0 157.130.59.13 100 0 701 4006 i * 205.215.57.0 157.130.59.13 100 0 701 4006 i * 205.215.58.0 157.130.59.13 100 0 701 4006 i * 205.215.62.0 157.130.59.13 100 0 701 4006 i --snip-- Why announce fifteen /24s terminating at the same AS out of the larger /18? --snip-- * 207.31.64.0/18 157.130.59.13 100 0 701 4006 ? * 207.31.72.0 157.130.59.13 100 0 701 4006 i * 207.31.74.0 157.130.59.13 100 0 701 4006 i * 207.31.76.0 157.130.59.13 100 0 701 4006 i * 207.31.81.0 157.130.59.13 100 0 701 4006 i * 207.31.82.0 157.130.59.13 100 0 701 4006 i * 207.31.83.0 157.130.59.13 100 0 701 4006 i * 207.31.84.0 157.130.59.13 100 0 701 4006 i * 207.31.87.0 157.130.59.13 100 0 701 4006 ? * 207.31.92.0/22 157.130.59.13 100 0 701 4006 i * 207.31.96.0/21 157.130.59.13 100 0 701 4006 ? * 207.31.104.0/21 157.130.59.13 100 0 701 4006 i * 207.31.115.0 157.130.59.13 100 0 701 4006 i * 207.31.118.0 157.130.59.13 100 0 701 4006 i * 207.31.120.0 157.130.59.13 100 0 701 4006 ? * 207.31.123.0 157.130.59.13 100 0 701 4006 i --snip-- Why announce twelve /24s, two /21s, and one /22 terminating at the same AS out of the larger /18? --snip-- * 207.153.64.0/18 157.130.59.13 100 0 701 4006 ? * 207.153.72.0 157.130.59.13 100 0 701 4006 i * 207.153.73.0 157.130.59.13 100 0 701 4006 i * 207.153.74.0 157.130.59.13 100 0 701 4006 i * 207.153.75.0 157.130.59.13 100 0 701 4006 i * 207.153.84.0/23 157.130.59.13 100 0 701 4006 i * 207.153.90.0 157.130.59.13 100 0 701 4006 i * 207.153.92.0 157.130.59.13 100 0 701 4006 i * 207.153.93.0 157.130.59.13 100 0 701 4006 i * 207.153.98.0/23 157.130.59.13 100 0 701 4006 i * 207.153.102.0 157.130.59.13 100 0 701 4006 i * 207.153.104.0 157.130.59.13 100 0 701 4006 i * 207.153.108.0 157.130.59.13 100 0 701 4006 i * 207.153.110.0 157.130.59.13 100 0 701 4006 i * 207.153.111.0 157.130.59.13 100 0 701 4006 i * 207.153.115.0 157.130.59.13 100 0 701 4006 i * 207.153.121.0 157.130.59.13 100 0 701 4006 ? * 207.153.122.0 157.130.59.13 100 0 701 4006 i * 207.153.124.0 157.130.59.13 100 0 701 4006 ? * 207.153.127.0 157.130.59.13 100 0 701 4006 i --snip-- Why announce seventeen /24s, and two /23s terminating at the same AS out of the larger /18? --snip-- * 209.44.64.0/23 157.130.59.13 100 0 701 4006 i * 209.44.64.0/18 157.130.59.13 100 0 701 4006 ? * 209.44.66.0 157.130.59.13 100 0 701 4006 i * 209.44.68.0/22 157.130.59.13 100 0 701 4006 i * 209.44.72.0 157.130.59.13 100 0 701 4006 i * 209.44.76.0/22 157.130.59.13 100 0 701 4006 i * 209.44.81.0 157.130.59.13 100 0 701 4006 i * 209.44.82.0 157.130.59.13 100 0 701 4006 ? * 209.44.85.0 157.130.59.13 100 0 701 4006 i * 209.44.87.0 157.130.59.13 100 0 701 4006 i * 209.44.114.0 157.130.59.13 100 0 701 4006 i * 209.44.116.0 157.130.59.13 100 0 701 4006 i * 209.44.127.0 157.130.59.13 100 0 701 4006 i --snip-- Why announce nine /24s, two /22s, and one /23 terminating at the same AS out of the larger /18? And I won't even start on the other ASes hanging off of NetRail...
Brandon Ross 404-522-5400 EVP Engineering, NetRail http://www.netrail.net AIM: BrandonNR ICQ: 2269442 Read RFC 2644!
-- Omachonu Ogali missnglnk@informationwave.net http://www.informationwave.net