I figured out my issue, I needed to include an empty AS list with my route instead of including my own AS.<br><br><div class="gmail_quote">On Tue, Dec 2, 2008 at 11:30 PM, Bruce M Simpson <span dir="ltr"><<a href="mailto:bms@incunabulum.net">bms@incunabulum.net</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">Russ,<br>
<br>
We need to see what the RIB thinks about the routes you're introducing from your collector daemon.<br>
<br>
Russ Dill wrote:<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
...<div class="Ih2E3d"><br>
<br>
However, no local routes are added:<br>
<br>
ip route<br>
</div><a href="http://192.168.1.0/24" target="_blank">192.168.1.0/24</a> <<a href="http://192.168.1.0/24" target="_blank">http://192.168.1.0/24</a>> dev eth0 proto kernel scope link src <a href="http://192.168.1.136" target="_blank">192.168.1.136</a> <<a href="http://192.168.1.136" target="_blank">http://192.168.1.136</a>> metric 2<br>
<a href="http://169.254.0.0/16" target="_blank">169.254.0.0/16</a> <<a href="http://169.254.0.0/16" target="_blank">http://169.254.0.0/16</a>> dev eth0 scope link metric 1000<br>
<a href="http://10.0.0.0/8" target="_blank">10.0.0.0/8</a> <<a href="http://10.0.0.0/8" target="_blank">http://10.0.0.0/8</a>> dev mea0 scope link<br>
default via <a href="http://192.168.1.1" target="_blank">192.168.1.1</a> <<a href="http://192.168.1.1" target="_blank">http://192.168.1.1</a>> dev eth0<div class="Ih2E3d"><br>
<br>
And no updates are sent to the backhaul peer.<br>
<br>
Both peers are running XORP 1.5-6 from debian.<br>
<br>
</div></blockquote>
<br>
The most likely explanation for the behaviour you are seeing, is that the updates are present in the BGP routing table, but the RIB is not selecting them as the candidate paths because of that <a href="http://10.0.0.0/8" target="_blank">10.0.0.0/8</a> entry, which the RIB will learn about from the FEA as a 'connected' route. That's pretty clear from the output you've provided.<br>
<br>
Note that whilst the iBGP routes are "valid", they are not "best", therefore there is absolutely no reason for iBGP to propagate them in updates -- unless you do some very specific tweaking using LOCAL_PREF and import policies, to cause those routes to win BGP's internal lookup.<br>
<br>
You're also going to have to do some tricks with administrative distance to get the RIB to choose the iBGP learned routes with the /24 prefixes. XORP defaults to an admin distance of 200 for iBGP and 0 for "connected" routes, so clearly, the iBGP routes will lose the RIB lookup every time.<br>
<br>
I believe the features to control admin distance on a per-protocol basis got added in the run up to the 1.5 release -- OLSR certainly makes use of them -- although they may not be fully documented until 1.6.<br>
<br>
thanks<br><font color="#888888">
BMS<br>
<br>
<br>
<br>
</font></blockquote></div><br>