2nd Network Card Configuration - Dapper

[Clint Tinsley]

Not sure what you want to do with the second card, but most common is bonding for failover. Info on that is at http://pmjdebruijn.blogspot.com/2006/04/ubuntu-bonding.html 

I am setting up a DRBL Server for cloning computers in a lab which needs its own subnet/interface.

Something simple I think, hoping for a quick answer. 

I added a second network card to a Dapper server build and configured DHCP3 to provide services on the second NIC. 
I can manually make it all work.  I have the second NIC configured in the interfaces as eth1 and properly defined but it won't come activate at boot time and DHCP services fail to start.  With it configured this way, if I do an ifconfig -a, the card is actually shown as eth2 with no configuration.  If I rem it out in interfaces, then reboot, un rem it, manually restart networking, it does come up as eth1 and I can start the DHCP services.  And I can verify this by pulling DHCP on another computer from this system which then works. 

I am sure I am missing a configuration setting that would make it all work automatically so that eth1 correctly configured and and active on boot such that DHCP Server would start properly as well on boot.  The suggestion box is open. 

Thanks, 

Clint