When trying to perform a NFS install on a machine with
several NICs the installer correctly detects them
and lets the user choose which one to use. However, after the correct NIC
is selected (in this case eth1), mounting the NFS directory fails
with a "no route to host" error. The machine does not respond
to pings on either interface to the IP that was configured into it.
I do multi-NIC installs all day using DHCP. I need more data.
Erk, now I figured it out. I redid the test (although on a different
machine, but same NICs) and it worked just fine.
Then I remembered I had problems some time ago on the original machine
with networking not working at all when a eepro100+tulip were plugged in, but
_only_ when IO-APIC was disabled. Remove the tulip or use SMP and everything
is happy again. Of course the install uses a non-SMP kernel, and
removing the tulip made the eepro100 work with the installer, so
I assumed it was a installer bug :)
So if there's a bug, it's most likely my hardware.