[6bone] Re: routing concern
John Fraizer
tvo@EnterZone.Net
Tue, 30 Jul 2002 17:25:27 -0400 (EDT)
OK. Lets address a couple of things.
If you continued to see 2001:400::/24 with an ORIGIN of 6175 after
8:38AM EST 30JUL2002, either:
(1) You have a broken BGP implementation.
(2) One or more of your peers have a broken BGP implementation.
(3) Both 1 and 2.
XS4ALL: You show a path of 1275_5623_9044_10566_6175 below but, the route
we saw was 109_513_3265_4538_6175.
I am at this very moment still seeing it (with XS4ALL in the path):
109 15180 3265 4538 6175
3ffe:c00:8023:4::1 from 3ffe:c00:8023:4::1 (128.107.240.254)
(fe80::806b:f0fe)
Origin IGP, localpref 100, valid, external, best
Last update: Tue Jul 30 12:13:38 2002
Again, if you continue to see this route with 6175 as the ORIGIN, start
contacting the peers you're seeing it from. It *ISN'T* being originated
by 6175 any longer. Your peers (and perhaps you) have broken BGP
implementations.
If you're running a broken BGP implementation, I submit that you owe it to
the REST of the DFZ operators to depeer until such time as you replace
your broken implementation with something that is not going to pollute the
DFZ.
This is one prefix that we know about. Who knows how much other garbage
your BGP implementation is spewing.
---
John Fraizer | High-Security Datacenter Services |
EnterZone, Inc | Dedicated circuits 64k - 155M OC3 |
http://www.enterzone.net/ | Virtual, Dedicated, Colocation |
On Tue, 30 Jul 2002, Joop Joosten wrote:
> Folks,
>
> I received 2001:400::/24 from a number of places and I announced it to
> some peers, because of an old filter (shame on me). I think it is fixed
> now.
>
> Joop..
>
> On Tue, 30 Jul 2002, Erik Bos wrote:
>
> > On Tue, Jul 30, 2002 at 10:21:29AM -0400, John Fraizer wrote:
> > > > sl-bb1v6-rly#sho bgp ipv 2001:400::/24
> > > > BGP routing table entry for 2001:400::/24, version 3963
> > > > Paths: (0 available, no best path)
> > > > Flag: 0x820
> > > > Not advertised to any peer
> > > >
> > >
> > > Looks like someone out there (?513? ?3265? ?4538?) is running broken a BGP
> > > implementation. I don't see the route direct from 6175 and I trust from
> > > the output above that 6175 isn't announcing it but, (?513? ?3265? ?4538?)
> > > is holding on to the prefix (and redistributing it) for dear life!
> >
> > We, AS3265, receive it from from AS1275:
> >
> > sh bgp ipv6 2001:400::/24
> > BGP routing table entry for 2001:400::/24, version 799862
> > Paths: (1 available, best #1)
> > Advertised to peer-groups:
> > XS4ALL-IPv6
> > 1275 5623 9044 10566 6175, (received & used)
> > 3FFE:401:0:1::27:1 from 3FFE:401:0:1::27:1 (128.176.191.66)
> > Origin IGP, localpref 100, valid, external, best
> >
> > sh bgp ipv6 neighbors 3FFE:401:0:1::27:1 received-routes | begin 2001:400::/24
> > *> 2001:400::/24 3FFE:401:0:1::27:1
> > 0 1275 5623 9044 10566 6175 i
> >
> > The box is running Cisco ios 12.2(8)T2.
> >
> > > Border2-BGP> sh ipv6 bgp 2001:400::/24
> > > BGP routing table entry for 2001:400::/24
> > > Paths: (4 available, best #3, table Default-IP-Routing-Table)
> > > Advertised to non peer-group peers:
> > > 2001:4f0::1 2001:630:0:f001::1 3ffe:1ced:ff02::2 3ffe:1ced:ff06::2
> > > 3ffe:1ced:ff07::2 3ffe:1ced:ff0a::2 3ffe:2900:d:e::1
> > > 3ffe:31ff:0:ffff::50 3ffe:4005:0:1::26 3ffe:80c0:200:5::36
> > > 3ffe:8160:0:1::c 3ffe:81d0:ffff:2::44
> > > 6435 2549 513 3265 4538 6175
> > > 3ffe:8160:0:1::c from 3ffe:8160:0:1::c (64.65.64.152)
> > > (fe80::4041:4098)
> > > Origin IGP, localpref 100, valid, external
> > > Last update: Tue Jul 30 08:38:19 2002
> > >
> > > 4554 109 513 3265 4538 6175
> > > 3ffe:1ced:ff06::2 from 3ffe:1ced:ff06::2 (192.0.1.1)
> > > (fe80::c620:401)
> > > Origin IGP, metric 1, localpref 100, valid, external
> > > Last update: Tue Jul 30 08:38:37 2002
> > >
> > > 109 513 3265 4538 6175
> > > 3ffe:c00:8023:4::1 from 3ffe:c00:8023:4::1 (128.107.240.254)
> > > Origin IGP, localpref 100, valid, external, best
> > > Last update: Tue Jul 30 08:38:35 2002
> > >
> > > 22 109 513 3265 4538 6175
> > > 3ffe:1ced:ff05::2 from 3ffe:1ced:ff05::2 (198.253.28.59)
> > > (fe80::c6fd:1c3b)
> > > Origin IGP, localpref 100, valid, external
> > > Last update: Tue Jul 30 08:38:42 2002
> > >
> > >
> > >
> > > ---
> > > John Fraizer | High-Security Datacenter Services |
> > > EnterZone, Inc | Dedicated circuits 64k - 155M OC3 |
> > > http://www.enterzone.net/ | Virtual, Dedicated, Colocation |
> > >
> > >
> > > _______________________________________________
> > > 6bone mailing list
> > > 6bone@mailman.isi.edu
> > > http://mailman.isi.edu/mailman/listinfo/6bone
> > >
> > _______________________________________________
> > 6bone mailing list
> > 6bone@mailman.isi.edu
> > http://mailman.isi.edu/mailman/listinfo/6bone
> >
>
>
> +-----------------------------------------------------------------------+
> | Joop Joosten, IT Division, CERN, 1211 Geneva 23, Switzerland |
> |Tel: +4122 767 3361; Fax: +4122 767 7155; Email: Joop.Joosten@cern.ch|
> +-----------------------------------------------------------------------+
>
>
> _______________________________________________
> 6bone mailing list
> 6bone@mailman.isi.edu
> http://mailman.isi.edu/mailman/listinfo/6bone
>