summaryrefslogtreecommitdiffstats
path: root/bgpd
diff options
context:
space:
mode:
authorDonald Sharp <sharpd@cumulusnetworks.com>2015-06-12 16:59:09 +0200
committerDonald Sharp <sharpd@cumulusnetworks.com>2015-06-12 16:59:09 +0200
commit276468936b08068d91b7f8edc1c7e89762e13c35 (patch)
tree91f238cf92d3777c9983f51854ea7c5948db2ec8 /bgpd
parentFix route-map peer-address configuration and operation. (diff)
downloadfrr-276468936b08068d91b7f8edc1c7e89762e13c35.tar.xz
frr-276468936b08068d91b7f8edc1c7e89762e13c35.zip
When a route-reflector is configured with "next-hop self" towards an IBGP
peer, it will only set the nexthop to "self" for non-reflected routes. To force the nexthop to "self" for reflected routes, a "next-hop self force" configuration is required. With the introduction of the update groups function, these two configurations are not distinguished correctly leading to inconsistent behavior. Resolve by introducing the proper distinction.
Diffstat (limited to 'bgpd')
-rw-r--r--bgpd/bgp_updgrp.h1
1 files changed, 1 insertions, 0 deletions
diff --git a/bgpd/bgp_updgrp.h b/bgpd/bgp_updgrp.h
index c34d2bc8e..b4e1078b0 100644
--- a/bgpd/bgp_updgrp.h
+++ b/bgpd/bgp_updgrp.h
@@ -41,6 +41,7 @@
PEER_FLAG_REFLECTOR_CLIENT | \
PEER_FLAG_NEXTHOP_SELF | \
PEER_FLAG_NEXTHOP_UNCHANGED | \
+ PEER_FLAG_FORCE_NEXTHOP_SELF | \
PEER_FLAG_AS_PATH_UNCHANGED | \
PEER_FLAG_MED_UNCHANGED | \
PEER_FLAG_NEXTHOP_LOCAL_UNCHANGED | \