diff options
| author | Ondrej Zajicek <santiago@crfreenet.org> | 2010-01-27 17:22:57 +0100 |
|---|---|---|
| committer | Ondrej Zajicek <santiago@crfreenet.org> | 2010-01-27 17:22:57 +0100 |
| commit | 6cb8f742f1adf99881334b8ae21c398d98571aa1 (patch) | |
| tree | 3e20c14d7e25002cae145ac3bdb172cb2d3eac77 /doc/bird.sgml | |
| parent | a3062085827db3115961eacd9d945ac202728174 (diff) | |
Better handling of well-known communities.
Process well-known communities before the export filter (old behavior is
to process these attributes after, which does not allow to send route
with such community) and just for routes received from other BGP
protocols. Also fixes a bug in next_hop check.
Diffstat (limited to 'doc/bird.sgml')
| -rw-r--r-- | doc/bird.sgml | 11 |
1 files changed, 11 insertions, 0 deletions
diff --git a/doc/bird.sgml b/doc/bird.sgml index 220ac94a..c1fc3d88 100644 --- a/doc/bird.sgml +++ b/doc/bird.sgml @@ -996,6 +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. + <tag>ignore communities <m/switch/</tag> 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. + <tag>enable as4 <m/switch/</tag> BGP protocol was designed to use 2B AS numbers and was extended later to allow 4B AS number. BIRD supports 4B AS extension, but by disabling this option it can be persuaded not to advertise it and |