http://bugzilla.suse.com/show_bug.cgi?id=1146440 http://bugzilla.suse.com/show_bug.cgi?id=1146440#c2 --- Comment #2 from Martin Wilck <martin.wilck@suse.com> --- After applying the commit from comment 1, arping works correctly with and without -D: apollon:~ # arping -D -c 2 192.168.1.19; echo RESULT=$? ARPING 192.168.1.19 from 0.0.0.0 obr0 Sent 2 probes (2 broadcast(s)) Received 0 response(s) RESULT=0 apollon:~ # arping -c 2 192.168.1.19; echo RESULT=$? ARPING 192.168.1.19 from 192.168.1.40 obr0 Sent 2 probes (2 broadcast(s)) Received 0 response(s) RESULT=1 apollon:~ # arping -D -c 2 192.168.1.20; echo RESULT=$? ARPING 192.168.1.20 from 0.0.0.0 obr0 Unicast reply from 192.168.1.20 [00:19:99:C4:C2:2F] 1.625ms Sent 1 probes (1 broadcast(s)) Received 1 response(s) RESULT=1 apollon:~ # arping -c 2 192.168.1.20; echo RESULT=$? ARPING 192.168.1.20 from 192.168.1.40 obr0 Unicast reply from 192.168.1.20 [00:19:99:C4:C2:2F] 1.414ms Unicast reply from 192.168.1.20 [00:19:99:C4:C2:2F] 1.256ms Sent 2 probes (1 broadcast(s)) Received 2 response(s) RESULT=0 -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=1146440 http://bugzilla.suse.com/show_bug.cgi?id=1146440#c3 Marcus Schaefer <ms@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|ms@suse.com |robert.simai@suse.com --- Comment #3 from Marcus Schaefer <ms@suse.com> --- Since some years I'm no not maintaining iputils anymore @Robert: This was still an issue we had while you were my manager. I thought the changed maintainer setup, irrc into Stefan Fents team had been applied successfully ? Thus I'll assign this to you for clarification on responsibilities. My plate is full ;) Thanks -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=1146440 http://bugzilla.suse.com/show_bug.cgi?id=1146440#c5 --- Comment #5 from Martin Wilck <martin.wilck@suse.com> --- This is probably a non-issue on ordinary systems. I encountered it in a test setup using rapido (https://github.com/rapido-linux/rapido). Rapido sets up dracut with "legacy" networking which would fall back to arping in my special case. Because of this bug, the VM configured in that way would always think the IP address it just received was already taken. I probably would never have encountered this problem if my system had had "arping2" installed. -- You are receiving this mail because: You are on the CC list for the bug.