Remember to clear your browser cache before downloading :)
10.10.5.12
) and the “normal” eBGP neighbor (10.63.0.2
) are handled from the same router. In other words, no dedicated “CO-BGP router” is needed.Debian (in this example configuration, CO-BGP and the “normal” BGP are handled from the same process):
CentOS: Same as with Debian.
Note that no IPv4 networks are advertised to CO-BGP neighbor (10.10.0.12), and no IPv6 networks to CL-BGP neighbor (10.63.0.1):
# vtysh -c 'show ip bgp neighbors 10.63.0.1 advertised-routes' > 10.10.5.0/24 10.63.0.2 0 32768 i # vtysh -c 'show ipv6 bgp neighbors 10.63.0.1 advertised-routes' % No such neighbor or address family # vtysh -c 'show ip bgp neighbors 10.10.0.12 advertised-routes' # vtysh -c 'show ipv6 bgp neighbors 10.10.0.12 advertised-routes' *> 2001:db8:941:215::/64 2001:db8::10:10:5:12 0 32768 i
(Scipts, configuration and documentation by Visa Holopainen -2013)