Re: NIC War
> Take a look at arp_filter in
> /usr/src/linux/Documentation/networking/ip-sysctl.txt (assuming
> /usr/src/linux is your unpacked kernel source).
>
> Now, I've never come accross this problem myself, but does it seem
> plausible that the default behavior here is creating the problem for
> you? Maybe I misunderstand your situation.
I was really hoping this would work---looks exactly like the problem I'm
having. Perhaps I'm doing it incorrectly.
echo 1 > /proc/sys/net/ipv4/conf/all/arp_filter
echo 1 > /proc/sys/net/ipv4/conf/eth0/arp_filter
echo 1 > /proc/sys/net/ipv4/conf/eth1/arp_filter
The second nic continues to accept for the first one, and once I bring
the first one back up, the conflict returns. Do I need to take the
second one down, first??
Here's some more strange behavior. Second NIC responds fine to pings via
arping (ping MAC). However, when first NIC is brought up, it doesn't
respond to mac pings anymore. When I configure the third NIC (which I
know works for sure) to work in place of the first NIC, it *also* does
not respond to mac pings. icmp_echo_ignore_all & broadcast are both set
to 0. No iptables configuration to drop it either.
What else can I try?
Thanks
Reply to:
- References:
- NIC War
- From: Ian Melnick <dazed@vonsteuben.cps.k12.il.us>
- Re: NIC War
- From: dircha <dircha@dircha.com>
- Re: NIC War
- From: Ian Melnick <dazed@vonsteuben.cps.k12.il.us>
- Re: NIC War
- From: dircha <dircha@dircha.com>