[afnog] AS Path transparency on Route Server

[Tayeb Meftah]

the wiki is full of documentation, and you can have a small router that could pass about 16GB/s for arround 1000USD, with 4 SFP ports and i think 13gbit ports, also you could use it on any x86 machine with a license for 250USD (i think)
we're all in the same room (africa), just with diferent family's;)
i could help you if you got any issue, i have a big lab with arround 7 mikrotik arround and 2 cisco switchs, 2 huawei switch... runing in a mpls network, (all at home):)

Tayeb Meftah
Voice of the blind T Broadcast Freedom
http://www.vobradio.org
Phone:447559762242
  ----- Original Message ----- 
  From: Anibe Onuche 
  To: Tayeb Meftah 
  Cc: afnog at afnog.org 
  Sent: Monday, June 10, 2013 10:47 AM
  Subject: Re: [afnog] AS Path transparency on Route Server


  Hello Tayeb

  Thanks.
  The Mikrotik option is a nice one but lacking documentation.
  Do you have any? 



  On 6/10/2013 10:38 AM, Tayeb Meftah wrote:

    Try routeros
    Mikrotik

    Envoyé de mon iPhone

    Le 10 juin 2013 à 10:47, Anibe Onuche <a.onuche at nixp.net> a écrit :



      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



      On 6/10/2013 3:57 AM, Andy Davidson wrote:

        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







      -- 
      Anibe Onuche
      Internet Exchange Point of Nigeria
      Network /Communication Department

      Tel:+234-809-3878-113
      NOC:+234-809-3878-110
      Website:www.ixp.net.ng


      _______________________________________________
      afnog mailing list
      http://afnog.org/mailman/listinfo/afnog




-- 
 
Anibe Onuche
Internet Exchange Point of Nigeria
Network /Communication Department

Tel:+234-809-3878-113
NOC:+234-809-3878-110
Website:www.ixp.net.ng 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://afnog.org/pipermail/afnog/attachments/20130610/461a3fee/attachment.html>