[ Date Index ] [ Thread Index ] [ <= Previous by date / thread ] [ Next by date / thread => ]
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 > The issue is nothing to do with IP addresses. Sorry- should have made > that clearer. > The problem here is the naming of the devices. eth0 and eth1 are volatile. You can fiddle with the boot sequence to try to get one to precede the other but AFAICT nothing is guaranteed. The best advice would be to use the hardware address in each case. Are you trying to ensure certain subnets get routed via specific paths? > Example: I have a card in > PCI slot 2, a card in PCI slot 3 and a card in PCI slot 4. The card in > PCI2 must always be called eth0 (and not eth1 or eth2). Presumably this is because you have certain other hardware connected to these physical locations and have configured the internal networking to rely on the identifiers rather than the real address. Why not change that so that the system is not dependent on the eth.. identifier? - -- Neil Williams ============= http://www.data-freedom.org/ http://www.nosoftwarepatents.com/ http://www.linux.codehelp.co.uk/ -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.3 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFEWQbFiAEJSii8s+MRApsZAKC5KOTr60ZAypeGrDKewBL50o1ndACfc2Wh m6xSjL4z23P+emQOJEuF93A= =lxvg -----END PGP SIGNATURE----- - The Mailing List for the Devon & Cornwall LUG Mail majordomo@xxxxxxxxxxxxx with "unsubscribe list" in the message body to unsubscribe. FAQ: www.dcglug.org.uk/linux_adm/list-faq.html