Add arping monitor type for devices that don't support ping

[derekoharrow]

⚠️ Please verify that this feature request has NOT been suggested before.

• [X] I checked and didn't find similar feature request

🏷️ Feature Request Type

New Monitor

🔖 Feature description

Some TCP/IP devices (specifically Amazon Echo devices) don't respond to IMCP ping requests, but they do respond to ARP scans.

✔️ Solution

It would be great to be able to use an ARping to check for specific devices to see if they're available - just in the same way as using an ICMP ping, but using ARP.

❓ Alternatives

No response

📝 Additional Context

No response

[BAYERNOLI]

Hi I would also like to use ARPing to Monitor several Devices!!

[moodyblue]

+1

This is also usefull to ping devices on different LAN's

[nicuj0r]

+1

I would also like this feature, especially for Amazon Echo Dot devices.

[merlinsvk]

+1

Yes.

Atleast something like: arping -f DEST_IP

for basic online check would be great.

[CommanderStorm]

@merlinsvk @nicuj0r @moodyblue @BAYERNOLI

Please refrain from posting +1 / requests for updates things on issues, as this makes issue-management harder. Issues are for discussing what needs to be done how by whom. We use 👍🏻 on issues to prioritise work.

[CommanderStorm]

Before somebody proposes a PR, we should discuss where this should be integrated: In an existing monitor or a new monitor. I could imagine this being a checkbox in the ping monitor, but am unfamiliar with arping. https://github.com/haf-decent/arpping seems like a good library choice.

[Alestrix]

I have the requirement to monitor whether a Windows 10 system is turned on or not. By default the Windows OS does not reply to ping commands, but AFAIK arping works. I'd rather use arping instead of opening up the Windows firewall to ICMP echo.

[RobertCSternberg]

In the meantime you can use HTTP Keyword monitor and the approach I describe here https://github.com/RobertCSternberg/ARPMonitorViaHTTP

[Alestrix]

Thanks @RobertCSternberg! I forked your repo and did a few changes, notably the possibility to hand over the scan target as a parameter to the docker command. Help yourself and copy along if you find something useful :smiley:. Or let me know and I send a PR along your way.

[RobertCSternberg]

@Alestrix I'm glad you liked the approach. The changes you made look very useful, send along a PR and we will get it merged!

[Alestrix]

@Alestrix I'm glad you liked the approach. The changes you made look very useful, send along a PR and we will get it merged!

Just sent you a PR. I initially thought about prettyfying and cleaning everything up and creating separate PRs for each added feature. But I decided to push everything I have and let you decide. I'm sorry that it's now all on you, but the initial option would have never been finished.

[RyderCragie]

Had the same issue with my Alexa. Just do a TCP on port 1080. Works great.

Alexa devices have the following ports open: 1080 6543 8888

[derekoharrow]

I get inconsistent results with those - some respond, some don't - I think the Echo devices may be going into some kind of sleep mode where they don't always respond.

[RyderCragie]

I get inconsistent results with those - some respond, some don't - I think the Echo devices may be going into some kind of sleep mode where they don't always respond.

I've only just done it so I'll let you know. All good so far.