I have run into a problem with the routing table not being created properly
if one or more IP aliases is present. With an IP alias setup, if I reboot
the machine, two default routes are setup. This causes problems because
the machine uses the last default route that is created, which ends up
being my secondary interface. Any application that is set to listen to one
interface but not the other never sees packets destined for eth0:0.
If I rerun /etc/init.d/rc.d/network by hand and restart the network, the
second default route goes away, as does the host route to my aliases IP
address. This is better than the above scenario but it seems the routing
setup is a bit broken with IP aliases present.
I've tested this on an older 5.2 box and everything works fine.
*** This bug has been marked as a duplicate of 11400 ***