[Xorp-hackers] Here's some bgp config files that work.

[Ben Greear]

I seem to have BGP working now, at least to some degree.

I fixed one exception that was thrown when route destination
is 0.0.0.0 (pushed the fix to xorp.ct), and it's included
below.

The rest of my problems were self-inflicted mis-configuration of
the peers and export policies.

I'm attaching two working configurations in hopes they prove
useful to someone.  There may still be issues with these,
but it works enough for BGP to exchange routes and let clients
attached to the two routers send traffic through them.

Here's the fix for 0.0.0.0 destination.  It should also
just catch the exception and ignore the route instead
of crash..but that's a fix for another day.

[greearb at ben-dt2 libxorp]$ git diff
diff --git a/bgp/path_attribute.cc b/bgp/path_attribute.cc
index f1326b2..b82475c 100644
--- a/bgp/path_attribute.cc
+++ b/bgp/path_attribute.cc
@@ -318,7 +318,7 @@ NextHopAttribute<A>::NextHopAttribute(const uint8_t* d)

      _next_hop = A(payload(d));

-    if (!_next_hop.is_unicast())
+    if (!(_next_hop.is_unicast() || _next_hop.is_zero()))
         xorp_throw(CorruptMessage,
                    c_format("NextHop %s is not a unicast address",
                             _next_hop.str().c_str()),


Thanks,
Ben

-- 
Ben Greear <greearb at candelatech.com>
Candela Technologies Inc  http://www.candelatech.com

-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: xorp-vr10001.conf
Url: http://mailman.ICSI.Berkeley.EDU/pipermail/xorp-hackers/attachments/20100420/3142715f/attachment.ksh 
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: xorp-vr10002.conf
Url: http://mailman.ICSI.Berkeley.EDU/pipermail/xorp-hackers/attachments/20100420/3142715f/attachment-0001.ksh