Ciao Daniele.
On Tue, 1 Nov 2011, Guazzoni Daniele, CH wrote:
Undocumented community ???
I was looking at RIPE but can't find 3303:9999
...
You are right. This is one of a handful of internally used BGP
communities received by AS3303 customers on their BGP feed.
It is possible to add 3303:9999 to the list of communities visible in the
RIPE DB, if you wish.
Are there other feature loaded IP-Plus communities we should be aware of ?
...
I do not think there is any, but it depends on what you mean by
"feature-loaded".
Should an AS3303 customer
- require an explanation for the meaning of an undocumented (non-public)
AS3303 community
- require a new/particular/feature-loaded community on routes received by
AS3303
(s)he is always welcome to contact <engineer...@ip-plus.net>.
Regards,
Paolo Moroni
IP-Plus Engineering
------------------------------------------------------------------------
<-- snip -->
=======================================================================
remarks:
remarks: COMMUNITY SUPPORT
remarks:
remarks: Community Action/Effect
remarks:
---------------------------------------------------------------------
remarks: 3303:300 set local-pref to 300 (same as peers). Default
is 400
remarks: 3303:888 blackhole within AS3303 (up to /32 allowed)
remarks: 3303:2199 Treat as peering route
remarks:
remarks: 3303:2050 prepend 3x to any peer in London
remarks: 3303:2051 prepend 3x to any peer in Amsterdam
remarks: 3303:2052 prepend 3x to any peer in Frankfurt
remarks: 3303:2053 prepend 3x to any peer in Paris
remarks: 3303:2054 prepend 3x to any peer in Stockholm
remarks: 3303:2056 prepend 3x to any peer in Vienna (AT)
remarks: 3303:2057 prepend 3x to any peer in Hong Kong
remarks: 3303:2058 prepend 3x to any peer in Singapore
remarks: 3303:2060 prepend 3x to any peer in Ashburn
remarks: 3303:2061 prepend 3x to any peer in Palo-Alto
remarks: 3303:2062 prepend 3x to any peer in Chicago
remarks: 3303:2063 prepend 3x to any peer in Dallas
remarks:
remarks: 3303:2150 do not announce to any peer in London
remarks: 3303:2151 do not announce to any peer in Amsterdam
remarks: 3303:2152 do not announce to any peer in Frankfurt
remarks: 3303:2153 do not announce to any peer in Paris
remarks: 3303:2154 do not announce to any peer in Stockholm
remarks: 3303:2156 do not announce to any peer in Vienna (AT)
remarks: 3303:2157 do not announce to any peer in Hong Kong
remarks: 3303:2158 do not announce to any peer in Singapore
remarks: 3303:2160 do not announce to any peer in Ashburn
remarks: 3303:2161 do not announce to any peer in Palo-Alto
remarks: 3303:2162 do not announce to any peer in Chicago
remarks: 3303:2163 do not announce to any peer in Dallas
remarks:
remarks: 3303:2040 prepend (1x) to all US peers/upstreams
remarks: 3303:2041 prepend (2x) to all US peers/upstreams
remarks: 3303:2009 prepend (3x) to all US peers/upstreams
remarks: 3303:2109 do not announce to ANY US peers/upstreams
remarks:
remarks:
remarks: 3303:2000 prepend (3x) to ALL ASes listed below
remarks: 3303:2100 do not announce to any AS listed below
remarks:
remarks: AS Name prepend (3x) do not announce to
remarks:
---------------------------------------------------------------------
remarks: 209 Qwest 3303:2015 3303:2115
remarks: 559 Switch 3303:2001 3303:2101
remarks: 1299 Telia 3303:2012 3303:2112
remarks: 1299 NY Telia USA 3303:2014 3303:2114
remarks: 3320 DTAG 3303:2002 3303:2102
remarks: 3356 Level(3) 3303:2018 3303:2118
remarks: 3356 NY Level(3) USA 3303:2008 3303:2108
remarks: 6730 Sunrise 3303:2003 3303:2103
remarks: 6830 UPC / Cablecom 3303:2004 3303:2104
remarks:
remarks:
---------------------------------------------------------------------
remarks: Outbound
remarks:
remarks: 3303:3050 route received in London
remarks: 3303:3051 route received in Amsterdam
remarks: 3303:3052 route received in Frankfurt
remarks: 3303:3053 route received in Paris
remarks: 3303:3054 route received in Stockholm
remarks: 3303:3056 route received in Vienna
remarks: 3303:3057 route received in Hong Kong
remarks: 3303:3058 route received in Singapore
remarks:
remarks: 3303:3002 route received from Telia in EU
remarks: 3303:5002 route received from Telia in USA
remarks: 3303:3004 route received from Level(3) in EU
remarks: 3303:5004 route received from Level(3) in USA
remarks: 3303:3008 route received from FLAG in EU
remarks:
remarks: 3303:1000 customer route
remarks: 3303:1004 peering route
remarks: 3303:1005 North American peering route
remarks: 3303:1006 European peering route
remarks: 3303:1007 Swiss peering route
remarks: 3303:1009 Asian peering route
remarks:
remarks:
========================================================================
<-- /snip -->
-----Original Message-----
From: swinog-boun...@lists.swinog.ch [mailto:swinog-boun...@lists.swinog.ch] On
Behalf Of Rene Luria
Sent: Montag, 31. Oktober 2011 09:38
To: swinog@lists.swinog.ch
Subject: Re: [swinog] AS3303 overlapping prefix
On 03. 04. 11 13:01, Simon Leinen wrote:
Andy Grawehr writes:
when i check our prefix 193.105.5.0/24 on www.ris.ripe.net i get an
overlapping prefix: 192.0.0.0/3 announced by AS3303.
Google "AS3303 semi-default". AS3303 announces this /3 to their
customers and possibly use it internally. It's part of an elaborate
mechanism to trade off routing table size against path quality.
With 3303, you can filter these annoucements using bgp community
attribute 3303:9999 Additionnaly it contains the no-export attribute
too.
Look for "bgp filtering swinog" on google, you'll find the presentation Andre
Chapuis made at swinog 7 back in 2003.
http://www.swinog.ch/meetings/swinog7/BGP_filtering-swinog.ppt
(look for "semi-default")
--
Rene Luria
_______________________________________________
swinog mailing list
swinog@lists.swinog.ch
http://lists.swinog.ch/cgi-bin/mailman/listinfo/swinog
