[Xorp-hackers] XORP, Click and its configuration...

[Pavlin Radoslavov]

> This is a multi-part message in MIME format.
> --------------060504090302010507020407
> Content-Type: text/plain; charset=ISO-8859-1; format=flowed
> Content-Transfer-Encoding: 7bit
> 
> Hello,
> 
> I was trying to use the click element KernelTun in my click 
> configuration in order to allow packets generated by the same computer 
> to be routed through click. In order to do this, I have changed the 
> xorp_fea_click_config_generator script. This new script (which I am 
> attaching to this email) works fine, it creates a new TUN interface 
> (tun0) with 172.16.0.1 as its address. Finally, I have to create a 
> default route to this new interface and delete every other route (so 
> that all generated packets go through tun0) and configured linux not to 
> do forwarding (in order to let this functionality to click).
> 
> By doing this, I am able to ping to every node and almost everything 
> goes fine. The only problem is that, whenever I create a new route (I 
> tried through static_routes), the TUN interfaces changes from tun0 to 
> tun1. And if I create another route (or delete an existant one), it goes 
> from tun0 to tun1. Why is this happening? Does XORP reinitiate Click 
> after each route change? How can I avoid this?

Rafael,

The only time the script should be invoked is when something about
the network interfaces has changed.

Creating a new route (I guess you used xorpsh in your test,
correct?) should not trigger an execution of the generator script.
Could you confirm that you are running a very recent code from the
CVS repository. The reason I ask is because approximately a month
ago the following bug was fixed in the rtrmgr:
http://www.xorp.org/bugzilla/show_bug.cgi?id=72

Prior to that fix, the Click generator script may have been executed
(as a side effect of the bug) whenever you change the config via
xorpsh.

Regards,
Pavlin