Re: [Nanog-futures] spam-l list
On Mon, May 11, 2009 at 01:41:13PM +1200, Simon Lyall wrote: A few people have pointed out that the spam-l list is being shutdown [1] Could anybody recommend an alternative open[2] anti-spam orientated list that people can be pointed to? Another list, run by long-time participants in spam-l, is being started. I'll pass along details as soon as I'm certain I have them straight. ---Rsk ___ Nanog-futures mailing list Nanog-futures@nanog.org http://mailman.nanog.org/mailman/listinfo/nanog-futures
ASPATH Loop
Hi， NANOG： When I was analyzing the BGP RIB data from RouteViews, I found that there were aspath loop in many bgp rib entries. For example, in the file rib.wide.20090301.0319, the peer 202.249.2.169 in AS2497 observed the following aspaths: 3130 29283 3130 2914 2497 3130 7337 3130 2914 2497 3130 34486 3130 2914 2497 3130 38001 3130 2914 2497 3130 13977 3130 2914 2497 3130 25147 3130 2914 2497 3130 5433 3130 2914 2497 3130 26164 3130 2914 2497 3130 34026 3130 2914 2497 3130 31535 3130 2914 2497 3130 14363 3130 2914 2497 3130 29648 3130 2914 2497 3130 27582 3130 2914 2497 3130 39737 3130 2914 2497 3130 33796 3130 2914 2497 3130 15108 3130 2914 2497 3130 9600 3130 2914 2497 .. As we know, BGP instance running on routers don't allow loop in ASPATH, why they can be seen in RIBs? It's some particular technical configuration in practice? OR What's wrong with AS3130?? Thanks Yangyang
Re: ASPATH Loop
On 10/05/2009, at 10:51 PM, yangyang. wang wrote: As we know, BGP instance running on routers don't allow loop in ASPATH, why they can be seen in RIBs? It's some particular technical configuration in practice? OR What's wrong with AS3130?? Look at the WHOIS entry for AS3130, and notice in the comments field: http://psg.com/as3130/ Regarding strange announcements by AS 3130 of prefixes in 98.128.0.0/16 is in the big headings on the top of that page. He is no doubt announcing it with an origin AS of 3130 so no person or router complains about inconsistent origins. -- Nathan Ward
