[Xorp-hackers] BGP issue in test harness (xorp.ct)
atanu at xorp.org
Fri Apr 23 17:19:43 PDT 2010
I think that there are two problems, BGP shouldn't be sending an
update with with a nexthop of zero and the test shouldn't be expecting
to see a nexthop of zero. I would expect that the nexthop should be
the IP address of the router. The test is failing to set a nexthop
address for IPv6 as it does for IPv4, it looks like in the past an
IPv6 address of zero passed through the system and now BGP is no
longer allowing it.
My suggestion is to log this as a bug and add this to the
TEST_NOT_FIXED variable and remove it from TESTS.
On Fri, Apr 23, 2010 at 4:03 PM, Ben Greear <greearb at candelatech.com> wrote:
> I've got at least partial functionality in the bgp test harness
> working in my xorp.ct tree.
> I am getting a failure (with crash due to uncaught exception)
> in test_peering1.sh:
> echo "TEST28 (IPV6) - Verify that routes originated by BGP reach an EBGP peer"
> echo "Also verify that the nexthop is rewritten and the provided nexthop"
> echo "is ignored"
> coord reset
> coord target $HOST $PORT4
> coord initialise attach peer1
> coord peer1 expect packet open asnum $AS bgpid $ID holdtime $HOLDTIME \
> afi 2 safi 1
> coord peer1 expect packet keepalive
> coord peer1 expect packet update \
> origin 0 \
> aspath 65008 \
> med 1 \
> nlri6 2000::/3 \
> nexthop6 ::
> It is crashing because :: isn't a unicast address. I think this is basically
> the same problem I hit the other day with IPv4, and I can fix it by catching
> the exception and ignoring the update. But, assuming this test case should
> function...should we perhaps allow :: for a nexthop?
> Ben Greear <greearb at candelatech.com>
> Candela Technologies Inc http://www.candelatech.com
> Xorp-hackers mailing list
> Xorp-hackers at icir.org
More information about the Xorp-hackers