<html><head><style type='text/css'>p { margin: 0; }</style></head><body><div style='font-family: Verdana; font-size: 10pt; color: #000099'>hi,<br><br>I saw that some blokes in this group have had similar problems while trying to startup the fai setup when booting a server with more that one nic connected, resulting in a nic infinitely waiting for a dhcp offer. (hang at ip-config)<br>I've got the same. however, while most had the problem with nics connected to different (v-)lans I've got it with all of them connected to the same lan. (at a later stage they are bonded).<br><br>weird thing is that te machine every now and then (1 out of 5, sometimes 6 times) continues. the difference seems to be if the second interface is also sending out a dhcp discovery, then the first accepts the offer he's receiving while there will be no response from the 1st nic after a offer when the 2nd hasn't sent out the dhcp discovery message.<br><br>(tcpdump on dhcp server learns me:)<br><br>so resume:<br>situation 1 (not successful)<br>server boots<br>ipconfig starts and eth0 sends dhcp discovery.<br>dhcp server sends offer<br>nothing happens... (hang)<br><span><br></span>situation 2 (successful)<br>
server boots<br>
ipconfig starts and eth0 sends dhcp discovery.<br>eth1 sends dhcp discovery as well<br>
dhcp server sends offer<br>eth0 sends dhcpd req to dhcpserver<br>get ack, boot continues<br>
nothing happens...<br><br>now, it could be that the switch config has something to do with this (i mean, while I am tcpdumping on a remote machine I only hear what comes in on the interface, what not necessarily means that nothing more has been sent out)<br><br>thanks for any help<br>Alex<br><br><span id="61bca160-188a-4d13-82ec-64b1eafd5506"><span name="x"></span><br>Met vriendelijke groet,<br>Alexander Swen<span name="x"></span><br></span><br></div></body></html>