something strange about bgp community
maxtul at netassist.ua
Thu Jan 8 14:50:49 UTC 2015
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.
where /\/\/\ is disrupted path with packet loss. AS104-AS105 is better
as AS-PATH lengh. If "target" accepts community, I can add
"target:notaccept" to AS104 and avoid that path.
Some brain-dead ;) transit providers clear all community when import
announces, but for me it is at least unfair.
On 07.01.15 15:35, Song Li wrote:
> Hi everyone,
> Today when I check one route in Routeviews I find something strange as
> route-views>sh ip bgp 184.108.40.206
> BGP routing table entry for 220.127.116.11/19, version 23405621
> Paths: (33 available, best #28, table default)
> Not advertised to any peer
> Refresh Epoch 1
> 202018 35320 35320 57800
> 18.104.22.168 from 22.214.171.124 (126.96.36.199)
> Origin IGP, localpref 100, valid, external
> Community: 702:120 2914:429 20485:52990 20485:53990 20485:54040
> 20485:54050 47541:10001
> rx pathid: 0, tx pathid: 0
> the AS-Path is "202018 35320 35320 57800" but the community is 702:120
> 2914:429 20485:52990 ....
> According to RFC 1997, the community format is AA:NN and AA means the
> AS#. Here, AS702, AS2914 and AS20485 do not appear in the AS-Path and as
> a result they should not appear in the community. Could anybody tell me
> what's the reason they do appear in the community of this route?
More information about the NANOG