Ian Melnick wrote:
What else can I try?
Try googling for arp_filter hidden and related things; there are a few
archived discussions that will come up, although I don't know whether
any of them will be useful.
Also, look through some of the other arp related options in the
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?
Hello all,
The weirdest thing's been going on lately with the two NICs in my
machine. One has started to respond on behalf of the other (almost
like a proxy arp), and AFAIK, I never set it up to do that. The problem
now is getting them both to respond normally, as they did when I first
set them
Ian Melnick wrote:
The only problem was, external requests coming in weren't going anywhere.
There's some kind of switch at the main office that forwards requests
from the external IP to the internal one, which is what my first NIC
was set up for. When we used arping and other monitoring tools, it
nic1: ipA, macA
nic2: ipB, macB
On the network attached to nic1 one you send an arp request:
who-has ipA tell x.x.x.x
where ipA is the ip you believe is assigned to nic1. nic1 does not
respond. nic2 responds with:
ipA is-at macB.
Yes, this is what's happening.
At the time of this
Ian Melnick wrote:
nic1: ipA, macA
nic2: ipB, macB
On the network attached to nic1 one you send an arp request:
who-has ipA tell x.x.x.x
where ipA is the ip you believe is assigned to nic1. nic1 does not
respond. nic2 responds with:
ipA is-at macB.
Yes, this is what's happening.
Take a look
6 matches
Mail list logo
