James Carlson wrote:
>>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.

Excellent -- many thanks, that's exactly what I was looking for.

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

Covered elsewhere in the thread I think. I personally hate using
router broadcasts, as they tend to cause odd problems (just last week
I had a machine drop off the network because of a change on a bridging
firewall that had the side effect of blocking said broadcasts).

- Ian

--
Ian Chard, Unix & Network Administrator | E: ian.chard@sers.ox.ac.uk
Systems and Electronic Resources Service | T: 80587 / (01865) 280587
Oxford University Library Services | F: (01865) 204937