我正在尝试让Quagga做一些简单的事情,比如向另一个连接到eBGP的邻居通告一个eBGP获知的前缀。很简单,对吧?
BGPd配置代码段
!
router bgp 64620
bgp router-id 172.29.253.80
bgp log-neighbor-changes
network 172.29.253.80/32
timers bgp 10 30
neighbor 10.35.253.2 remote-as 64901
neighbor 10.35.253.2 next-hop-self
neighbor 10.35.253.2 soft-reconfiguration inbound
neighbor 10.47.0.254 remote-as 64621
neighbor 10.47.0.254 ebgp-multihop 255
neighbor 10.47.0.254 next-hop-self
neighbor 10.47.0.254 soft-reconfiguration inbound
!前缀10.47.0.0/16从邻居10.47.0.254获知,并重新通告到10.35.253.2
# sh ip bgp 10.47.0.0/16
BGP routing table entry for 10.47.0.0/16
Paths: (1 available, best #1, table Default-IP-Routing-Table)
Advertised to non peer-group peers:
10.35.253.2
64621
10.47.0.254 from 10.47.0.254 (10.47.0.254)
Origin IGP, localpref 100, valid, external, best
Last update: Mon Mar 19 08:35:28 2018但是检查通向10.35.253.2的通告路由发现它(10.47.0.0/16)确实没有通告。我还用tcpdump验证了这一点。
# sh ip bgp neighbors 10.35.253.2 advertised-routes
BGP table version is 0, local router ID is 172.29.253.80
Status codes: s suppressed, d damped, h history, * valid, > best, = multipath,
i internal, r RIB-failure, S Stale, R Removed
Origin codes: i - IGP, e - EGP, ? - incomplete
Network Next Hop Metric LocPrf Weight Path
*> 172.29.253.80/32 10.35.253.1 0 32768 i
Total number of prefixes 1BGPd版本
# /usr/lib/quagga/bgpd --version
bgpd version 0.99.24.1发布于 2018-03-21 22:13:55
这被证明是Quagga中的一个bug;https://bugzilla.quagga.net/show_bug.cgi?id=972
通过切换到FRR来解决,这似乎更积极地维护。
https://stackoverflow.com/questions/49358344
复制相似问题