You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
FPing binary is called without the -4 option, although it defaults to IPv4 but it makes both A and AAAA queries, and when the same host is probed with both FPing and FPing6 then an additional AAAA query is made by fping -6 binary just within a fraction of second.
This results in an unecessary 3 queries per dual stack host and unncessary traffic.
Proposed Change
+ FPing
binary = /usr/sbin/fping
protocol = 4
A simple change i.e. adding protocol = 4 to the FPing Probe config solves this issue.
Now fping -4 only makes A query and fping -6 only makes AAAA query.
After making the proposed change, number of queries are decreased significantly
Expected Behavior
No response
Steps To Reproduce
Run container as is with defaults and add a target to be probed with both FPing and FPing6
+ Microsoft
menu = Microsoft
title = Microsoft
++ v4
menu = Microsoft v4
title = Microsoft v4
probe = FPing
host = microsoft.com
++ v6
menu = Microsoft v6
title = Microsoft v6
probe = FPing6
host = microsoft.com
Capture DNS queries with packet capture or see logs in your configured DNS server.
There will be 3 queries for microsoft.com, one A and two AAAA.
This issue has been automatically marked as stale because it has not had recent activity. This might be due to missing feedback from OP. It will be closed if no further activity occurs. Thank you for your contributions.
Activity
github-actions commentedon Feb 15, 2026
Thanks for opening your first issue here! Be sure to follow the relevant issue templates, or risk having this issue marked as invalid.
LinuxServer-CI commentedon Mar 17, 2026
This issue has been automatically marked as stale because it has not had recent activity. This might be due to missing feedback from OP. It will be closed if no further activity occurs. Thank you for your contributions.
LinuxServer-CI commentedon Jun 16, 2026
This issue is locked due to inactivity