Ken Schneider wrote:
On Sun, 2005-12-25 at 15:59 -0500, James Knott wrote:
Eric Hines wrote: <snip> Either I'm missing something or you're missing something. Those files are tied directly to a NIC, with the corresponding MAC address. They don't work with any other. Now eth0, eth1 etc., may wander around, but why is that an issue? Servers talk to IP addresses, not NICs. It's up to the IP stack to figure out which NIC to talk to. You shouldn't have any need to worry about whether a NIC is eth0 or not.
Unless setting up the firewall with those names.
Again, no need. The SUSE firewall supports using the AMC IDs for NICs. For example, In my fireall, my NICs are listed as eth-id-00:05:5d:fe:fc:e4, eth-id-00:80:c6:f0:6a:5c and eth-id-00:c0:4f:a1:8f:94. There is no reason to specify eth0, eth1 etc. The only exceptions are my VPN which is tun0 and dial in port ppp0 which have no MAC addresses.