<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<div class="moz-cite-prefix">Hello Tayeb<br>
<br>
Thanks.<br>
The Mikrotik option is a nice one but lacking documentation.<br>
Do you have any? <br>
<br>
<br>
<br>
On 6/10/2013 10:38 AM, Tayeb Meftah wrote:<br>
</div>
<blockquote cite="mid:3472536561272389744@unknownmsgid" type="cite">
<meta http-equiv="content-type" content="text/html;
charset=ISO-8859-1">
<div>
<div style="text-align:left;direction:ltr"><span style="">Try
routeros</span></div>
<div style="text-align:left;direction:ltr">
<span style="">Mikrotik</span></div>
<br>
<span style="">Envoyé de mon iPhone</span></div>
<div style=""><br>
Le 10 juin 2013 à 10:47, Anibe Onuche <<a
moz-do-not-send="true" href="mailto:a.onuche@nixp.net">a.onuche@nixp.net</a>>
a écrit :<br>
<br>
</div>
<blockquote type="cite" style="">
<div><span></span><br>
<span>Hello All,</span><br>
<span></span><br>
<span>I quite appreciate the multiple response I have gotten .</span><br>
<span></span><br>
<span>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</span><br>
<span>2. My BGP logs shows invalid or corrupt ASN received
when the route server client is implemented.</span><br>
<span>3. My research shows that there are issues with quagga
Route server client : Mostly issues with rs-client code ,
Due to structure locking issues</span><br>
<span> source: <a moz-do-not-send="true"
href="http://www.uknof.org.uk/uknof13/Hughes-IXP_routeservers.pdf">http://www.uknof.org.uk/uknof13/Hughes-IXP_routeservers.pdf</a>
( page 8 )</span><br>
<span>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.</span><br>
<span></span><br>
<span></span><br>
<span>Regards</span><br>
<span>Anibe Onuche</span><br>
<span></span><br>
<span></span><br>
<span></span><br>
<span>On 6/10/2013 3:57 AM, Andy Davidson wrote:</span><br>
<blockquote type="cite">
<span>Hi, Anibe --</span><br>
</blockquote>
<blockquote type="cite"><span></span><br>
</blockquote>
<blockquote type="cite"><span>You wrote:</span><br>
</blockquote>
<blockquote type="cite">
<blockquote type="cite"><span>For the purpose of AS Path
transparency, I implemented a Quagga</span><br>
</blockquote>
</blockquote>
<blockquote type="cite">
<blockquote type="cite"><span>Route server with the
following configuration</span><br>
</blockquote>
</blockquote>
<blockquote type="cite"><span>[...]</span><br>
</blockquote>
<blockquote type="cite">
<blockquote type="cite"><span>Unfortunately, the status on
my BGP shows active :-(</span><br>
</blockquote>
</blockquote>
<blockquote type="cite"><span>Your config looks correct.
(That said, your peer client in production</span><br>
</blockquote>
<blockquote type="cite"><span>configuration should use
route-maps or at the bare minimum</span><br>
</blockquote>
<blockquote type="cite"><span>prefix-lists/distribute-lists in
order to prevent leaks of non-customer</span><br>
</blockquote>
<blockquote type="cite"><span>prefixes to the route-server.)</span><br>
</blockquote>
<blockquote type="cite"><span></span><br>
</blockquote>
<blockquote type="cite"><span>You should use standard BGP
troubleshooting to look into this (I.e. Check</span><br>
</blockquote>
<blockquote type="cite"><span>that layer 1/2 connectivity
exists (you can ping); Check that you can</span><br>
</blockquote>
<blockquote type="cite"><span>telnet from the route-server
client to the route-server on port 179 and</span><br>
</blockquote>
<blockquote type="cite"><span>get a tcp connection; check logs
and debug output).</span><br>
</blockquote>
<blockquote type="cite"><span> </span><br>
</blockquote>
<blockquote type="cite">
<blockquote type="cite">
<span>Tried working with BIRD routing protocol but some
features lacking</span><br>
</blockquote>
</blockquote>
<blockquote type="cite">
<blockquote type="cite"><span>(i.e peer groups),also the
learning curve is somewhat steep.</span><br>
</blockquote>
</blockquote>
<blockquote type="cite"><span>Please do look again at BIRD.
If you are a not for profit Internet</span><br>
</blockquote>
<blockquote type="cite"><span>Exchange point then you are
welcome to my perl scripts that build the BIRD</span><br>
</blockquote>
<blockquote type="cite"><span>route-server configuration at
LONAP and IXLeeds in the UK. The same</span><br>
</blockquote>
<blockquote type="cite"><span>Scrips are used on the excellent
NAP Africa IX in South Africa too.</span><br>
</blockquote>
<blockquote type="cite"><span></span><br>
</blockquote>
<blockquote type="cite"><span>They perform IRRDB filtering
(which is a useful thing for you to do in</span><br>
</blockquote>
<blockquote type="cite"><span>order</span><br>
</blockquote>
<blockquote type="cite"><span>To build trust in the
route-server service), and also individual RIBs</span><br>
</blockquote>
<blockquote type="cite"><span>(routing tables) for each ASN
connected to the route-server (which is</span><br>
</blockquote>
<blockquote type="cite"><span>useful in the event that you
want to offer filtering between route-server</span><br>
</blockquote>
<blockquote type="cite"><span>participants.)</span><br>
</blockquote>
<blockquote type="cite">
<span></span><br>
</blockquote>
<blockquote type="cite"><span>In my experience, BIRD scales
further than Quagga, especially when you</span><br>
</blockquote>
<blockquote type="cite"><span>have a routing table per
connected ASN.</span><br>
</blockquote>
<blockquote type="cite"><span></span><br>
</blockquote>
<blockquote type="cite"><span>Good luck with your project.</span><br>
</blockquote>
<blockquote type="cite"><span></span><br>
</blockquote>
<blockquote type="cite">
<span>Andy</span><br>
</blockquote>
<blockquote type="cite"><span></span><br>
</blockquote>
<blockquote type="cite"><span></span><br>
</blockquote>
<span></span><br>
<span></span><br>
<span>-- </span><br>
<span> Anibe Onuche</span><br>
<span>Internet Exchange Point of Nigeria</span><br>
<span>Network /Communication Department</span><br>
<span></span><br>
<span>Tel:+234-809-3878-113</span><br>
<span>NOC:+234-809-3878-110</span><br>
<span>Website:<a moz-do-not-send="true"
href="http://www.ixp.net.ng">www.ixp.net.ng</a></span><br>
<span></span><br>
<span></span><br>
<span>_______________________________________________</span><br>
<span>afnog mailing list</span><br>
<span><a moz-do-not-send="true"
href="http://afnog.org/mailman/listinfo/afnog">http://afnog.org/mailman/listinfo/afnog</a></span><br>
</div>
</blockquote>
</blockquote>
<br>
<br>
<pre class="moz-signature" cols="72">--
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 </pre>
</body>
</html>