converting our anycast node from quagga
Hi, I just started to play with bird. My anycast node setup is as follows. - each anycast server is serving form 1 up to 3 anycast prefixes - the anycast adresses are assigned to the dummyX interfaces as /32(IPv4) or /128(IPv6) - the BGP/quagga/ is advertising the /24 or /48 (added aggregate-address ......../24 (/48) summary-only - if I put the dummyX interface down, the BGP will stop announce the route associated to this interface, both IPv4 and IPv6 - if I put the dummyX interface up, the BGP will start announce the route The setup is a little more complex (metric, communities, preferencies, ..), but this is the main idea how it works. In another words I could stop/start announce the anycast prefix without reconfiguring the bgp daemon. Please, could someone point me how to do this in bird. There is direct protocol, but I see /32 routes, not /24 best regards Peter -- *Peter Hudec* Infraštruktúrny architekt phudec@cnc.sk <mailto:phduec@cnc.sk> *CNC, a.s.* Borská 6, 841 04 Bratislava Recepcia: +421 2 35 000 100 Mobil:+421 905 997 203 *www.cnc.sk* <http:///www.cnc.sk>
On Fri, Jul 03, 2015 at 04:26:26PM +0200, Peter Hudec wrote:
Hi,
I just started to play with bird.
My anycast node setup is as follows.
- each anycast server is serving form 1 up to 3 anycast prefixes - the anycast adresses are assigned to the dummyX interfaces as /32(IPv4) or /128(IPv6) - the BGP/quagga/ is advertising the /24 or /48 (added aggregate-address ......../24 (/48) summary-only - if I put the dummyX interface down, the BGP will stop announce the route associated to this interface, both IPv4 and IPv6 - if I put the dummyX interface up, the BGP will start announce the route
The setup is a little more complex (metric, communities, preferencies, ..), but this is the main idea how it works. In another words I could stop/start announce the anycast prefix without reconfiguring the bgp daemon.
Please, could someone point me how to do this in bird. There is direct protocol, but I see /32 routes, not /24
Hi Direct protocol just create routes based on assigned addresses. You could define static device routes using static protocol. These should also appear/disappear based on whether the associated interface goes up/down. -- Elen sila lumenn' omentielvo Ondrej 'Santiago' Zajicek (email: santiago@crfreenet.org) OpenPGP encrypted e-mails preferred (KeyID 0x11DEADC3, wwwkeys.pgp.net) "To err is human -- to blame it on a computer is even more so."
Hi Ondrej, you're right. I used static protocol, added routd to interfaces and added 'check link' switch. So the basic principe is working, thanks. Peter On 03/07/15 17:18, Ondrej Zajicek wrote:
On Fri, Jul 03, 2015 at 04:26:26PM +0200, Peter Hudec wrote:
Hi,
I just started to play with bird.
My anycast node setup is as follows.
- each anycast server is serving form 1 up to 3 anycast prefixes - the anycast adresses are assigned to the dummyX interfaces as /32(IPv4) or /128(IPv6) - the BGP/quagga/ is advertising the /24 or /48 (added aggregate-address ......../24 (/48) summary-only - if I put the dummyX interface down, the BGP will stop announce the route associated to this interface, both IPv4 and IPv6 - if I put the dummyX interface up, the BGP will start announce the route
The setup is a little more complex (metric, communities, preferencies, ..), but this is the main idea how it works. In another words I could stop/start announce the anycast prefix without reconfiguring the bgp daemon.
Please, could someone point me how to do this in bird. There is direct protocol, but I see /32 routes, not /24
Hi
Direct protocol just create routes based on assigned addresses. You could define static device routes using static protocol. These should also appear/disappear based on whether the associated interface goes up/down.
-- *Peter Hudec* Infraštruktúrny architekt phudec@cnc.sk <mailto:phduec@cnc.sk> *CNC, a.s.* Borská 6, 841 04 Bratislava Recepcia: +421 2 35 000 100 Mobil:+421 905 997 203 *www.cnc.sk* <http:///www.cnc.sk>
On Fri, Jul 03, 2015 at 05:41:32PM +0200, Peter Hudec wrote:
Hi Ondrej,
you're right. I used static protocol, added routd to interfaces and added 'check link' switch.
This should work even without 'check link' option. That option is for link up/down events (e.g. on ethernet) while admin up/down events should be handled always. -- Elen sila lumenn' omentielvo Ondrej 'Santiago' Zajicek (email: santiago@crfreenet.org) OpenPGP encrypted e-mails preferred (KeyID 0x11DEADC3, wwwkeys.pgp.net) "To err is human -- to blame it on a computer is even more so."
participants (2)
-
Ondrej Zajicek -
Peter Hudec