|
Hello,
> 1. Kernel 2.2x seems to be far more proliferic in completing these arps.
What makes you think this is the case? The arp prefsrc code hasn't
really changed from 2.2.x to 2.4.x. What did I miss this time from
your statement?
> Try going to 2.4x. Since we've gone to 2.4.18 we haven't had anymore
> incidients. Also do you start the second NIC with -arp options?
'-arp' in the linux world doesn't mean that the device should not
reply to arp anymore. Read the mailing list entries about 'hidden'
and 'arp' from about a year ago. An interesting thing is the ip arp
feature from Julian: http://www.linux-vs.org/~julian/route-noarp.txt
> 2. The drivers make no difference, we've also tried the native intel
> ones. In fact I believe they are the same in almost all respects.
The drivers indeed can't make the difference but not because they
are the same (which is actually not even true) but because the
driver doesn't have anything to do with the arp/routing issue which
seems clearly to be the problem here.
Best regards,
Roberto Nibali, ratz
--
echo '[q]sa[ln0=aln256%Pln256/snlbx]sb3135071790101768542287578439snlbxq' | dc
|
