[jiml8]

When the built-in NIC dies, so you stick a card into a slot to get a working NIC, but the system insists on recognizing the built-in NIC as eth0 even though you keep trying to disable it...

So you have to change your configuration so that the system knows that the NIC eth1 is the one to use...

And you have to change the smb.conf that VMWare uses so that it knows to use eth1...

And you change the routing table so that the route to the internet is eth1...

And the route to DNS is through eth1...

And the default route is through eth1...

Then, if you FORGET to change the Freakin' Firewall so that IT is allowing traffic on eth1, you are gonna go 'round and 'round trying to figure out why things aren't working.

So don't forget.

[CouchMaster]

Heheh...
Boy, it might have been easier to have reinstalled the OS and picked up the new card that way.

[short101]

or use ifrename..

[jiml8]

yeah, I just knew there had to be a command that would simplify things...

[codejockey]

yeah, I just knew there had to be a command that would simplify things...

Well, perhaps on some versions of Linux/Unix. My slackware distro (10.0 -- not the latest, but close) doesn't feature ifrename. I suspect using the command: ifconfig eth0 down as root would effectively disable this interface (in software), so that eth1 would be the only viable choice. I'm also surprised that VmWare needs to know the specific interface (but since I don't run VmWare, that's likely just my ignorance showing).

Thanks for the informative post.