[afnog] AS Path transparency on Route Server

[Joe Abley]

Hi there,

Perhaps a more basic question is why you are trying to strip the AS number of your route server from the AS_PATH at all. You might well have good reasons, but you could consider this more basic question before proceeding with the andyware or more debugging of quagga.

Having a route server AS number in the AS_PATH attribute of routes learnt from it has the potential to influence your exit decision (as a customer of the route server) but if you're already managing that with LOCAL_PREF (customers > peers > transit) then it will make no difference.

It is frequently handy for debugging (I find) to be able to identify quickly whether a route was learnt from a route server or learnt in some other way.


Joe

On 2013-06-10, at 10:41, Anibe Onuche <a.onuche at nixp.net> wrote:

> 
> Hello All,
> 
> I quite appreciate the multiple response I have gotten .
> 
> 1. When i implement the route server client.. the Established BGP session goes into active mode. so it has nothing to do with Layer 2
> 2. My BGP logs shows invalid or corrupt ASN received when the route server client is implemented.
> 3.  My research shows that there are issues with quagga Route server client : Mostly issues with rs-client code ,  Due to structure locking issues
>   source: http://www.uknof.org.uk/uknof13/Hughes-IXP_routeservers.pdf     ( page 8 )
> 4. Bird..ah Bird .. Please Andy, i will be grateful if i can have the perl script. We are a non profit IXP and as such welcome any contribution like your to the exchange point.
> 
> 
> Regards
> Anibe Onuche