From: Michael Tremer <michael.tremer@ipfire.org>
To: Robin Roevens <robin.roevens@disroot.org>
Cc: development@lists.ipfire.org
Subject: Re: ARP ping instead of ICMP ping for gateway latency check ?
Date: Tue, 22 Apr 2025 15:35:49 +0100 [thread overview]
Message-ID: <C00AD9A3-9EFA-46F1-B4F7-BD52CC9B5D0A@ipfire.org> (raw)
In-Reply-To: <a57368df23e3c8048828a06c473456934eae54cb.camel@disroot.org>
Hello Robin,
> On 20 Apr 2025, at 23:52, Robin Roevens <robin.roevens@disroot.org> wrote:
>
> Hi All
>
> I recently changed my internet provider and I noticed that both the
> gateway graph on cgi-bin/netother.cgi and my Zabbix gateway ping check
> no longer work.
Yes, some ISPs don’t respond do ICMP echo requests to the gateway. I have no idea why really, but it is not uncommon.
> It seems that my current provider blocks ICMP pings on the gateway
> address.
> So I was wondering if it wouldn't be better to use arping instead of
> normal ping to check the latency of the gateway? This should always
> works regardless of firewalls of the provider.. I think?
This is a good idea. An ARP ping should always work, because otherwise there is no way to discover the layer 2 address of the gateway. But that obviously only applies to internet connections that actually use ARP. PPP connections don’t use ARP for example.
We are also using collectd which is using liboping and that only supports ICMP.
> I can quite easily change this Zabbix check. But I'm not sure about the
> graph on netother.cgi; I can look into that if you all think that
> change would be a good idea? Or if anyone could give me some pointers
> on where to start looking?
I think so. It could be an option for the future.
If the gateway does not respond to pings, you should automatically fall back to ping.ipfire.org <http://ping.ipfire.org/> though. So the graph should always have some data to show.
Best,
-Michael
>
> Regards
> Robin
>
> --
> Dit bericht is gescanned op virussen en andere gevaarlijke
> inhoud door MailScanner en lijkt schoon te zijn.
>
>
next prev parent reply other threads:[~2025-04-22 14:35 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-20 22:52 Robin Roevens
2025-04-22 14:35 ` Michael Tremer [this message]
2025-04-25 14:57 ` fairmont
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=C00AD9A3-9EFA-46F1-B4F7-BD52CC9B5D0A@ipfire.org \
--to=michael.tremer@ipfire.org \
--cc=development@lists.ipfire.org \
--cc=robin.roevens@disroot.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox