From 41677025ee67fcccd34493f9b205037dd68811c9 Mon Sep 17 00:00:00 2001 From: Ondrej Zajicek Date: Thu, 28 Jan 2010 15:59:18 +0100 Subject: Changes 'ignore communities' to 'interpret communities'. --- doc/bird.sgml | 17 +++++++++-------- 1 file changed, 9 insertions(+), 8 deletions(-) (limited to 'doc') diff --git a/doc/bird.sgml b/doc/bird.sgml index c1fc3d8..343d016 100644 --- a/doc/bird.sgml +++ b/doc/bird.sgml @@ -996,16 +996,17 @@ for each neighbor using the following configuration parameters: capability and accepts such requests. Even when disabled, BIRD can send route refresh requests. Default: on. - ignore communities RFC 1997 demands that - BGP speaker should process well-known communities like + interpret communities RFC 1997 demands + that BGP speaker should process well-known communities like no-export (65535, 65281) or no-advertise (65535, 65282). For example, received route carrying a no-adverise community - should not be advertised to any of its neighbors. BIRD has - such behavior hardwired (it is evaluated when a route is - exported to the protocol just before the export filter). This - option allows to disable such hardwired processing of - well-known communities (in that case, similar behavior can be - implemented in the export filter). Default: off. + should not be advertised to any of its neighbors. If this + option is enabled (which is by default), BIRD has such + behavior automatically (it is evaluated when a route is + exported to the protocol just before the export filter). + Otherwise, this integrated processing of well-known + communities is disabled. In that case, similar behavior can be + implemented in the export filter. Default: on. enable as4 BGP protocol was designed to use 2B AS numbers and was extended later to allow 4B AS number. BIRD supports 4B AS extension, -- cgit v1.2.3