New upstream release and new maintainer

[quagga-debian.git] / doc / bgpd.texi

diff --git a/doc/bgpd.texi b/doc/bgpd.texi
index d5aa30c4a5c4ee0921cfb436743c1f0a6ae7ebd1..3cd442d191e0b206292e70269202ea4c19a96549 100644 (file)
--- a/doc/bgpd.texi
+++ b/doc/bgpd.texi
@@ -104,6 +104,8 @@ so @code{router-id} is set to 0.0.0.0.  So please set router-id by hand.
 @deffn {BGP} {distance bgp <1-255> <1-255> <1-255>} {}
 This command change distance value of BGP.  Each argument is distance
 value for external routes, internal routes and local routes.
 @deffn {BGP} {distance bgp <1-255> <1-255> <1-255>} {}
 This command change distance value of BGP.  Each argument is distance
 value for external routes, internal routes and local routes.

+
+To have this command applied to existing routes requires a hard clear.

 @end deffn
 
 @deffn {BGP} {distance <1-255> @var{A.B.C.D/M}} {}
 @end deffn
 
 @deffn {BGP} {distance <1-255> @var{A.B.C.D/M}} {}


@@ -1163,7 +1165,7 @@ route-map RMAP permit 10
 
 Following configuration is an example of BGP route filtering using
 communities attribute.  This configuration only permit BGP routes
 
 Following configuration is an example of BGP route filtering using
 communities attribute.  This configuration only permit BGP routes

-which has BGP communities value 0:80 or 0:90.  Network operator can
+which has BGP communities value 0:80 and 0:90.  Network operator can

 put special internal communities value at BGP border router, then
 limit the BGP routes announcement into the internal network.
 
 put special internal communities value at BGP border router, then
 limit the BGP routes announcement into the internal network.