|
Horms wanted us to know:
>> >> I would like to see a "noisy gratuitous arp" setting where you can tell
>> >> heartbeat to occassional resend the gratuitous arp. Something like:
>> >> noisy_arp 720 # 720 minutes = 12 hours
>> >Actually, that was my original design, and that is the way
>> >fake, which heartbeat was subsequently based on works.
>> >But the way things stand now it could easily be added as an
>> >option to send arp. Do you want to have a look at patching that,
>> >unfortunately I am a touch busy?
>> I will take a look at it but I think it is a low priority. I read the
>> section of the LVS HOWTO on the arp problem carefully and noticed
>> something that I had not noticed before: the noarp module. I have since
>> started using that on my real machines with the older kernels and it
>> seems to be working so far. (Hence my posts from late last night about
>> the noarp module).
>Understood. That is probably a better solution anyway.
Following up, the noarp module has been working properly for me. So
extra emphasis in the docs may be called for that forcing gratuitous
arps is not a reliable fix.** Instead, fix it at the source. Make the
real machine which is erroneously arping stop. The proper solutions are
the noarp module (fast and effective) or a modern kernel with these
capabilities enabled.
** I observed that gratuitous arps only replace mac entries in arp
tables, not create them (at least not on the Cisco router and PIX we
have). Sending gratuitous arps does nothing for you if there's no entry
in the arp table (low traffic volume sites, which arguably might not
need HA to begin with).
--
Regards... Todd
We should not be building surveillance technology into standards.
Law enforcement was not supposed to be easy. Where it is easy,
it's called a police state. -- Jeff Schiller on NANOG
Linux kernel 2.6.8.1-12mdkenterprise 2 users, load average: 0.00, 0.02, 0.03
|
