[afnog] AS Path transparency on Route Server

[Andy Davidson]

Hi, Anibe --

You wrote: 
> For the purpose of AS Path transparency, I implemented a Quagga
> Route server with the following  configuration
[...]
> Unfortunately, the status on my BGP shows active  :-(

Your config looks correct.  (That said, your peer client in production
configuration should use route-maps or at the bare minimum
prefix-lists/distribute-lists in order to prevent leaks of non-customer
prefixes to the route-server.)

You should use standard BGP troubleshooting to look into this (I.e. Check
that layer 1/2 connectivity exists (you can ping); Check that you can
telnet from the route-server client to the route-server on port 179 and
get a tcp connection; check logs and debug output).
    
> Tried working with BIRD routing protocol but some features lacking
> (i.e peer groups),also the learning curve is somewhat steep.

Please do look again at BIRD.  If you are a not for profit Internet
Exchange point then you are welcome to my perl scripts that build the BIRD
route-server configuration at LONAP and IXLeeds in the UK.  The same
Scrips are used on the excellent NAP Africa IX in South Africa too.

They perform IRRDB filtering (which is a useful thing for you to do in
order 
To build trust in the route-server service), and also individual RIBs
(routing tables) for each ASN connected to the route-server (which is
useful in the event that you want to offer filtering between route-server
participants.)

In my experience, BIRD scales further than Quagga, especially when you
have a routing table per connected ASN.

Good luck with your project.

Andy