In article <xoavy8alew49.fsf@sun.com>,
James Carlson <james.d.carlson@sun.com> wrote:
>(As an aside, if it works fine with regular routing, why would you
>want to hard-code it into a configuration file? Doing so just means
>that this machine, and all others like it, will need to be modified
>the next time the network topology changes. That seems like an
>operational problem to me ...)

Our network topology rarely changes and when it does there is almost
always prior notice and an expectation of at least some service
interuption.

For simple, relatively static networks I see having to edit a config
file preferable and more secure than a constantly running root priv'ed
daemon that listens to the network for routing info.
--
Jim Prescott - Computing and Networking Group jgp@seas.rochester.edu
School of Engineering and Applied Sciences, University of Rochester, NY