To complete this thread for anyone that might be interested ...
This was indeed a system/hardware problem. The ethernet interface in my
server had flaked out and would not transmit more than 10 or 12 packets in
rapid succession, as typically occurs when TFTP'ing a kernel to a requesting
thin
On Sunday 03 September 2006 01:32, [EMAIL PROTECTED]
wrote:
You could just keep it simple and ignore the second nic.
You would only need it if you want to route traffic, create another
subnet or make it a failover. I think if you assign each nic an ip on
the same subnet, that would cause
