zombie routes to 3ffe:1ce1::/32 ?

[Bill Sommerfeld]

[resent, since it didn't seem to get through the first time..]

I'm attempting to implement some of the 6bone hardening
recommendations at my site (MIT-SIPB, AS3)..

While doing so, I (stupidly) tried an experiment with the use of the
"no-export" community which appears to have backfired and left some of
what Itojun refers to as "zombie routes" floating around.

It appeared from source-routed traceroutes that the no-export-tagged
route propagated further than I expected it to, so I stopped bgp and
restarted it without this; however, I have reason to believe that the
route is still floating around in the 6bone bgp cloud..

My understanding is that dropping the bgp connection should have
caused the bgp peer to withdraw any routes it learned from
me.. unfortuneately, that doesn't seem to have happened.  

I have reason to believe that there are currently some "zombie routes"
to 3ffe:1ce1::/32 floating about as a result of this.

Anyone have any advice as to what I can do from here to get the route
withdrawn for real?  (I'm using zebra bgp 0.80 on NetBSD+KAME).

					- Bill