Ian Chard <ian.chard@sers.ox.ac.uk> writes:
> My fault for being vague :-)
>
> If I don't run in.routed, I can't replicate the above configuration:
> if I add both default routers, they aren't tied to interfaces (i.e. the
> sixth column is empty), and all packets used the first default route
> in the table.

You'll need to write your own start-up script that does 'route add'
with the '-ifp' option to accomplish that.

(A future release will have a static route configuration feature, but
no current release does.)

(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 ...)

--
James Carlson, KISS Network <james.d.carlson@sun.com>
Sun Microsystems / 1 Network Drive 71.234W Vox +1 781 442 2084
MS UBUR02-212 / Burlington MA 01803-2757 42.497N Fax +1 781 442 1677