|
Hello,
Michael McConnell wrote:
Hello all. I've posted this here in the LVS mailing list after not
hearing back from any other mailing list. Hopefully I have not broken
the rules too bad (-;
We'll find you, hunt you down and you'll face severe punishment :)
I currently have a system which has a Tyan 2515 Motherboard. This
motherboard features a Dual Intel 82559 NIC.
ok.
The problem I am face is that which using both ports of this dual
interface network card (plugged into the same switch) I find that the
second interface is answering arp requests (on rare occasions) that the
first interface should be answering.
*cough*, on what what kind of rare occasions? Could you maybe be a
little bit more specific? Could you maybe send in the output of:
ip addr show
cat /proc/sys/net/ipv4/conf/eth*/hidden
cat /proc/sys/net/ipv4/conf/eth*/medium_id
I have used tcpdump and clearly seen eth1 answering arps requests that
eth0 should be answering... how odd.... It's rare, but when it happens
Could you please send those dumps?
of course that address is offline. (Note this only seems to happen on
alias IP address, it has never happened on the primary interface)
Is the 'alias IP address' in the same address scope as one of the
physical addresses?
I am using the open source drivers provided with the 2.2.19 kernel, I'm
wondering if the drivers provided by Intel would help this problem? Does
To me it sounds more like a routing/arp problem, since you're driver
obviously is sending packets, and that's about what it is supposed to do.
anyone have any other suggestions, or for that matter has anyone else
run into this problem? Could this possibly be a problem with aliasing?
Maybe, let's see your setup.
Thanks for all your thoughts,
Michael McConnell
No worries, hope we can help you,
Roberto Nibali, ratz
--
echo '[q]sa[ln0=aln256%Pln256/snlbx]sb3135071790101768542287578439snlbxq'|dc
|
