[Xorp-users] Problems with "priviledged instruction fault" and 1.0RC

[Pavlin Radoslavov]

> 2/. I'm being thick here.....  Reading documentation, its not
> clear to me whether, using LiveCD, I have to set IP addresses
> of interfaces using ifconfig logged on as root, or whether I can do
> all of that via xorpsh etc, or am I better editing some config files or....

You can do it all via xorpsh. Of course, if you want to keep the
configuration you created via xorpsh you would have to save it to a
file (on a floppy) so the next time when you reboot you don't have
to recreate all the configuration again.

> 3/.  I want to be able to use this xorp box in two ways. Once as basically
> a multicast router, but also as a backup unicast router.   We have for
> a long time (although not actually at the moment) often run two routers in parallel,
> one set to be our main unicast router and
> one set to do multicast routing (using mrouted which we of course we have now not used for ages).
> On the multicast router (which was a multiinterface sun workstation) we artifically
> increased the metric/cost associated with each interface so as
> the other router became "preferred" by other machines on our networks,
> but would get used automatically if the other one failed.  Cutting a long tale short,
> is it fairly easy to set up Xorp to artifically high costs associated with interfaces?

I think the answer is "yes".

In the RIP configuration, when you assign addresses per vif, there
is a variable called "metric", which by default is "1".
According to the xorpsh online help, that metric is used to:
"Set the cost metric added to routes received on address."

In addition, when you export, say, the connected or static routes in
the "export connected" or "export static" RIP configuration section,
there is another variable "metric" that can be used to assign the
metric for those exported routes.

> We would then run RIP for unicast and PIM-SM etc for multicast...
> 
> 4/. I've read through the XORP command line interface guide and the
> Live CD web pages, but I still feel short of knowledge/understanding here.
> Any pointers to which other document I really should read as opposed
> to which is internals etc.

>From user's perspective, the "Getting Started" web page, the Live CD
web page, the "CLI Manual (PDF)" and "Configuration Guide (PDF)" are
the documents you need to read.
The "XORP Design Overview" PDF/PS document from the "Design docs"
list is useful for high-level overview of the XORP design.

Those documents are probably a good starting point, but they are far
from being completed. We are continuously trying to improve things
so any input or help in improving the documentation is appreciated.

Thanks,
Pavlin