[Xorp-users] error with XRLs

Pavlin Radoslavov pavlin@icir.org
Fri, 04 Feb 2005 12:27:03 -0800


> > In general, please have a look in
> > static_routes/xorp_static_routes.cc how it is done. It is relatively
> > short and simple, so comparing it against your code may show you
> > where the problem is. E.g., in the static_routes code, there is
> > another declaration right before wait_until_xrl_router_is_ready(),
> > and this declaration _has_ to be before
> > wait_until_xrl_router_is_ready().
> 
> Ok, I see you are talking about calling the ctor() for XrlStaticRoutesNode.
>  I can copy that file and modify and make an XrlBGPBeaconNode class then. 
> Before I go too far on this though, I would like to check one thing: If I
> create my own module like this bgp_beacon, MUST it be an Xrl Target?  I
> started off with the simple plan of just writing a basic program to make a
> few Xrl calls on the XrlBgpV0p2Client object.  That is all I wanted to do -
> nothing more.  I truly hope that I don't have to build a full-blown Xrl
> Target module as well.  Can you just verify this for me, or tell me if I am
> wrong.

Jeff,

You don't have to implement XrlTarget in your module if you don't
need it. Obviously, that module will be able only to send XRLs and
receive the results, but it won't be able to receive XRLs on its
own.

In that case, you would have to call "xrl_std_router.finalize();"
after the XrlStdRouter constructor. E.g., see the source code for,
say, xorp/fea/tools/show_interfaces.cc which sends XRLs, but is not
an XrlTarget.

Regards,
Pavlin