zcip: defend problem

[Steven Scholz]

Hi all,

I just build zcip (from svn) for my embedded ARM system and started it with

	/sbin/zcip -r 169.254.73.83 eth0 /etc/zcip/zcip.script

It actually configured my interface appropriatly.

To test defending I connected a different board to the network and
configured it statically to the above IP (without zcip) to force a
collision. After starting a ping on this board zcip on the first one starts
giving out:

zcip: eth0 recv arp type=2054, op=1,
zcip: ^Isource=0:a0:33:2:8b:41 169.254.73.83
zcip: ^Itarget=0:0:0:0:0:0 169.254.0.0
zcip: state = 3, source ip conflict = 0, target ip conflict = 0
zcip: ...wait -1 eth0 nprobes=3, nclaims=2
zcip: eth0 recv arp type=2054, op=1,
zcip: ^Isource=0:a0:33:2:8b:41 169.254.73.83
zcip: ^Itarget=0:0:0:0:0:0 169.254.0.0
zcip: state = 3, source ip conflict = 0, target ip conflict = 0
zcip: ...wait -1 eth0 nprobes=3, nclaims=2
zcip: eth0 recv arp type=2054, op=1,
zcip: ^Isource=0:a0:33:2:8b:41 169.254.73.83
zcip: ^Itarget=0:0:0:0:0:0 169.254.0.0
zcip: state = 3, source ip conflict = 0, target ip conflict = 0
zcip: ...wait -1 eth0 nprobes=3, nclaims=2

and goes on until I stop the ping. Funny enough zcip already selected a
different IP. ifconfig revealed that the interface is configured for
169.254.7.189. So for it looks like zcip is still "arguing" about the old
(discarded) IP! Why is that?

-- 
Steven