Re: multi-IP ARP announcement bugs?

Thanks. During start-up I agree it's doing the right thing. I'm not so  
sure
I agree it does the right thing when a 'wackatrl -f' is issued on one  
of the machines.

That sequence includes a wackatrl -f / wackatrl -s (on s2 I think).  
Does your reading
indicated the failover case results in the "right" grat. arp packets?

I'll reread my playback to spell out what I believe is missing.

- Mark

On 23 Mar 2009, at 15:50, Theo Schlossnagle wrote:

> Looks right to me.  You are grat-arping from every IP to every IP on  
> your network...
>
> 82.138.255.16/28
> 82.138.254.16/28
>
> There are 16 address - 2 (net/bcast) ... so 14 people on each  
> network that need to be notified that the IPs are owned by new  
> machines.  You have 4 IPs configured on each box.... 3 are on one  
> subnet and 1 is on the other... So, you should see 3*14 + 1*14  
> gratuitous arp responses from each machine.  Your tcpdump looks  
> fine.  If you look inside the payload, you'll see all the  
> combinations represented in the source and target addresses.
>
>
> On Mar 22, 2009, at 6:53 PM, Mark Blackman wrote:
>
>> Ok, i've attached the correct config, wackamole debug output and  
>> tcpdump of arp-only
>> packets.
>>
>> The original config was the result of paring down the 4 IPs per  
>> group to a single IP
>> as a test.
>>
>> - Mark
>>
>> <wackamole-diag-correct.tgz>
>>
>>
>> On 22 Mar 2009, at 22:25, Mark Blackman wrote:
>>
>>>
>>> On 20 Mar 2009, at 17:18, Theo Schlossnagle wrote:
>>>
>>>> config file, and an arp-only tcpdump on every interface for the  
>>>> same time period and the relevant syslog output.
>>>>
>>>
>>> Attached as requested. Sent only to yourself as it include client  
>>> set-up details, but feel
>>> free to respond on the list.
>>>
>>> Two machines, s1 and s2 both on the following 3 subnets
>>>
>>> 10.10.10.0/24
>>> 82.138.255.16/28
>>> 82.138.254.16/28
>>>
>>> the spread daemon is configured to use the 10.10.10.0/24 subnet IPs
>>>
>>> the machines take responsibility for two groups of 4 IPs as
>>> the configuration file should indicate. With luck I've merely
>>> screwed up the configuration.
>>>
>>> I've attached the tcpdump output (arp) from each machine, suitable
>>> for tcpdump -r playback, both configuration files (hopefully  
>>> identical)
>>> and finally output from both wackamole daemons with '-d' specified.
>>>
>>> I ran wacktrl -f / wackatrl -s sequence while the daemons were  
>>> running
>>> as an example.
>>>
>>> Cheers,
>>> Mark Blackman
>>> Exonetric
>>>
>>>
>>>
>>> <wackamole-diag.tgz>
>>>
>>>
>>>
>>
>
> --
> Theo Schlossnagle
> Principal/CEO
> OmniTI Computer Consulting, Inc.
> Web Applications & Internet Architectures
> w: http://omniti.com   p: +1.443.325.1357 x201   f: +1.410.872.4911
>
>
>
>