There's no guarantee in what order a network interface will initialize, so I think the confusion is with multiple default route specifications, and you're getting lucky with the other machine getting the right one. There should be only one default route specified. The route add/del flushes the extra entries and causes it to work.
I think I would try removing the default entry from the ifroute files for all but one interface (the one that should actually be the default network if there is not a more specific route) and add a init script to establish any other needed routes later in the boot process. That way you can control when the additonal connectivity becomes available and ensure that the routes are correctly inserted. ---------------------------------------------------------------------- For LINUX-390 subscribe / signoff / archive access instructions, send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
