zcip: defend problem
Steven Scholz
steven.scholz at imc-berlin.de
Tue Sep 12 15:07:02 UTC 2006
Hi,
> 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.
A different test:
1st board (ARM):
/sbin/zcip -r 169.254.73.83 eth0 /etc/zcip/zcip.script
2nd board (PPC)
ifconfig eth0 169.254.73.84 netmask 255.255.0.0
ping 169.254.73.83
1st board:
zcip: eth0 recv arp type=2054, op=2,
zcip: ^Isource=0:a0:33:2:8b:41 169.254.73.84
zcip: ^Itarget=0:a0:33:2:53:49 169.254.83.73
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=2,
zcip: ^Isource=0:a0:33:2:8b:41 169.254.73.84
zcip: ^Itarget=0:a0:33:2:53:49 169.254.83.73
zcip: state = 3, source ip conflict = 0, target ip conflict = 0
zcip: ...wait -1 eth0 nprobes=3, nclaims=2
Please not the WRONG IP in "target="! Is it only printed in the wrong order?
Or is it actually handled in the wrong order!?
--
Steven
More information about the busybox
mailing list