The eth1/2 thing could be a udev configuration.

Post #304,290 by static 2/17/09 7:11:44 PM Reply	The eth1/2 thing could be a udev configuration. I had a similar problem when I last installed etch. I found that /etc/udev/rules.d/z25_persistent-net.rules uses the MAC address to map your devices so pulling a faulty card didn't make the on-board one eth1 like I expected. :-/ Wade. "Ah -- I take it the doorbell doesn't work?"
Post #304,298 by scoenye 2/18/09 12:05:12 AM Reply	Thought so too, but that file didn't change The timestamp is well in the past. It now seems that Lenny is running right and Etch was somehow using the incorrect descriptor. Both NICs are integrated in the motherboard chipset, so unless PCI enumeration is doing strange things, I'm at a loss to explain the flip.
Post #304,302 by folkert 2/18/09 6:34:22 AM Reply	There was a point where one of the maintainers... put in a fix for a certain NIC that would mostly ignore the persistent rules. It had to do with restarting a network service like SSH or something. The NICs would flip flop upon this service restart (after updates) and the machine would be unreachable except by console (or remote console device). It seems to me these problems were due to the versions of udev/hal in Etch and the crossover updates from Sarge. I could be wrong, as I got out of Debian's foray (mailing lists) when I took a troll to task and got swatted on the hands by Sam Hovecar (the DPL newly elected).

Welcome to IWETHEY!