Arping Related Network Binding Issue

Hi,

but as if you can see the -I option already offers the interface.
In my case the default should then be without -I and only one instance of arping.
If someone likes to restrict then “arping -I eth0” could be used in the command.

ARPing 2.19, by Thomas Habets <thomas@habets.se>
usage: arping [ -0aAbdDeFpPqrRuUv ] [ -w <sec> ] [ -W <sec> ] [ -S <host/ip> ]
              [ -T <host/ip ] [ -s <MAC> ] [ -t <MAC> ] [ -c <count> ]
              [ -C <count> ] [ -i <interface> ] [ -m <type> ] [ -g <group> ]
              [ -V <vlan> ] [ -Q <priority> ] <host/ip/MAC | -B>
For complete usage info, use --help or check the manpage.
root@raspi:/openhab# arping -w 5 -C 1 192.168.3.28
ARPING 192.168.3.28
60 bytes from 68:a4:0e:4d:ab:66 (192.168.3.28): index=0 time=97.459 msec

--- 192.168.3.28 statistics ---
1 packets transmitted, 1 packets received,   0% unanswered (0 extra)
rtt min/avg/max/std-dev = 97.459/97.459/97.459/0.000 ms

I have submitted a PR to address this bug, enabling arping from ip utils.

Hi,
i have exactly same that one dest address is pinged from about 20 threads from my more than 20 source-networks and not from selected network card. This causes extrem high load on my system.
https://community.openhab.org/t/openhab-4-0-1-and-network-pingdevice-on-docker-install-results-in-massive-threads/148658

Dis you found a solution to ping only from main network which selected?