[Xorp-hackers] Interfacing for runtime config

[Atanu Ghosh]

Once the interface information is known you could generate a config.boot
file and then start XORP.

Another solution would be to invoke the xorpsh from a program to
configure the interfaces. The xorpsh will accept commands on its
standard input.

A combination of both solutions generate a new config.boot whenever
interfaces appear/disappear. Then instruct XORP to load the new
configuration file.

----------------------------------------
#!/bin/sh

xorpsh <<!
configure
load /etc/generated.config.boot
commit
!
----------------------------------------

	  Atanu.

>>>>> "Weaver" == Weaver John <John.Weaver@motorola.com> writes:

    Weaver> I am needing to find out how would be the best way to config
    Weaver> XORP at init.  Our system does not have predefined
    Weaver> interfaces until some our applications come up and do the
    Weaver> IPCP over the backhaul and read from a database.  We then
    Weaver> set up our interfaces and then bring up XORP for PIM and
    Weaver> IGMP functionality.  So for us to have a boot.config is not
    Weaver> possible.  Is there a way to write my our process that I can
    Weaver> allow the other apps to talk to and tell it what the
    Weaver> interface info is so I can config the VIFs?

    Weaver>  

    Weaver> Thanks,

    Weaver> John