On Thu, Jan 8, 2015 at 9:50 AM, Max Tulyev wrote:
> Some brain-dead ;) transit providers clear all community when import
> announces, but for me it is at least unfair.
hrm, it's possible that cleaning the communities (after dealing with
the local/customer-added ones) means you may not get multipl
Hi Song,
that's normal. This is a signat to AS702 to do some special with this
route when it will see this route.
Community is transistive by its design, so you don't need to be directly
connected to AS702 to send some signal to it.
For example:
you->AS101-AS102-AS103-target
\->AS104-/\/\/\-A
Thanks!
Because there is no standard syntax on the description of BGP community,
I think the problem is hard to understand.
在 2015/1/7 23:25, joel jaeggli 写道:
2914:429 is ntt's do not advertise to any peer community
bgp communities are transitive attributes, e.g. you can just pass them
to pe
2914:429 is ntt's do not advertise to any peer community
bgp communities are transitive attributes, e.g. you can just pass them
to peers unmolested. so someone that's presumably not ntt ( e.g. the
neighbor is digital ocean) is sending that commmunity to route views as
part of their export.
Their
Also note there is nothing stopping anyone from adding any community
they want.
The effect and how long the community stays attached to a route is
another matter.
On 1/7/2015 8:35 AM, Song Li wrote:
Hi everyone,
Today when I check one route in Routeviews I find something strange as
follows:
On Wed, Jan 7, 2015 at 9:29 AM, Jared Mauch wrote:
> 2914:429 is a community to signal to NTT to not announce the route to peers
> which would perhaps be why you don't see NTT doing that.
>
it looks like this is the 'customer' of several networks (701, 2914)
and they just blindly add carrier com
2914:429 is a community to signal to NTT to not announce the route to peers
which would perhaps be why you don't see NTT doing that.
You can see the documented NTT communities here:
http://www.us.ntt.net/support/policy/routing.cfm
Jared Mauch
> On Jan 7, 2015, at 5:35 AM, Song Li wrote:
>
>
Hi everyone,
Today when I check one route in Routeviews I find something strange as
follows:
route-views>sh ip bgp 176.108.0.0
BGP routing table entry for 176.108.0.0/19, version 23405621
Paths: (33 available, best #28, table default)
Not advertised to any peer
Refresh Epoch 1
202018 353
8 matches
Mail list logo