[Xorp-hackers] Error for XORP-OLSR when nodes are in different subnetwork

[Ben Greear]

On 02/24/2012 01:01 PM, Jiangxin Hu wrote:
> Recently I tested Xorp-OLSR for the scenario which nodes are belong to different sub network. I got following errors in XORP log and routes are not inserted
> into kernel table.
> The scenario is very simple. There are two nodes, one address is 10.0.0.2/24 and another address is 10.0.2.3/24.
> [ 2012/02/24 15:39:53.283729 ERROR xorp_rib:36 RIB rib/rib.cc:870 add_route ] Attempting to add IGP route to table "olsr" (prefix 10.0.2.3/32 next-hop
> 10.0.2.3): no directly connected interface toward the next-hop router
> [ 2012/02/24 15:39:53.284476 WARNING xorp_rib XrlRibTarget ] Handling method for rib/0.1/add_route4 failed: XrlCmdError 102 Command failed Could not add IPv4
> route net 10.0.2.3/32, nexthop: 10.0.2.3 to unicast RIB
> [ 2012/02/24 15:39:53.285360 ERROR xorp_olsr4:38 OLSR contrib/olsr/xrl_queue.cc:236 route_command_done ] callback: add_route: ribname rib net 10.0.2.3/32
> nexthop 10.0.2.3 102 Command failed Could not add IPv4 route net 10.0.2.3/32, nexthop: 10.0.2.3 to unicast RIB
> Is it a configuration error or it is a implementation limitation?

Does this work with another routing protocol like OSPF?

OLSR is not that well tested and I know it has at least some
bugs in more complex network topologies.

Thanks,
Ben

> Thanks,
> Jiang
>
>
> _______________________________________________
> Xorp-hackers mailing list
> Xorp-hackers at icir.org
> http://mailman.ICSI.Berkeley.EDU/mailman/listinfo/xorp-hackers


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