[ZBX-7209] Pinging IPv4 and v6 addresses can result in some hosts not being processed Created: 2013 Oct 25 Updated: 2023 Apr 28 |
|
| Status: | Open |
| Project: | ZABBIX BUGS AND ISSUES |
| Component/s: | Proxy (P), Server (S) |
| Affects Version/s: | 2.0.9 |
| Fix Version/s: | None |
| Type: | Incident report | Priority: | Trivial |
| Reporter: | Volker Fröhlich | Assignee: | Unassigned |
| Resolution: | Unresolved | Votes: | 3 |
| Labels: | fping, icmpping, ipv4, ipv6 | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Attachments: |
fping-2.4.txt
fping-3.5.txt
|
||||||||
| Issue Links: |
|
||||||||
| Description |
|
Mixing IPv4 and v6 for pinging is creating problems and these problems are also different depending on your version of fping. I have created 4 different example files with different address types and order and went across them with fping and fping6: for f in pure-ipv4 pure-ipv6 mixed-ipv4-first mixed-ipv6-first; do for fp in fping fping6; do echo "${fp}" "${f}"; "${fp}" -f "${f}"; echo $?;echo ""; done; done The most noteworthy discovery is that the fping and fping6 commands in version 2 simply bail out of the file as soon as they encounter an address from a family they don't understand. Consequent hosts are not pinged at all; there are no results. Version 3 binaries on the other hand throw errors on unknown family's addresses but continue to go through the file. |
| Comments |
| Comment by Aleksandrs Saveljevs [ 2013 Nov 05 ] |
|
Here is another example of the problem. In the default installation, we have host "Zabbix server" at 127.0.0.1. We use fping6 to determine its reachability and, since fping6 does not like 127.0.0.1 address, it does not ping the host. However, the item does not become unsupported. Rather, it shows the host as being down. |
| Comment by Volker Fröhlich [ 2013 Nov 11 ] |
|
As found in https://www.zabbix.com/forum/showthread.php?t=22676 2 years ago already |
| Comment by richlv [ 2014 Jan 08 ] |
|
ZBX-6688 might be related |
| Comment by Volker Fröhlich [ 2014 Feb 16 ] |
|
How about getting rid of the whole concept of having temporary files for this purpose? |
| Comment by Aleksandrs Saveljevs [ 2014 Feb 25 ] |
|
Does anybody know what the rationale is for having two utilities: ping and ping6, fping and fping6? Why a single utility cannot ping both IPv4 and IPv6? |
| Comment by Volker Fröhlich [ 2014 Feb 25 ] |
|
Looking at their ChangeLog file, it seems support for IPv6 was introduced in 2002 by Jeroen Massar:
... only came in 2012's 3.3. I suggest to ask the fping3 developer [email protected] about it. |
| Comment by richlv [ 2014 Mar 05 ] |
|
same as source ip, ipv6 was available as a patch initially. i guess the patch was not implemented in a way to cleanly support both address families at first - thus separate utilities might be a historical thing |
| Comment by richlv [ 2016 Dec 23 ] |
|
for the record, this problem still there in 2.4. probably in 3.0 as well, but haven't tested that one yet. |
| Comment by alex dekker [ 2018 Sep 14 ] |
|
Yes, bug is very much still present in 3.4. I am unclear as to what the logic is here - why try the A record and the AAAA record, if the A record is responding? AAAA record should not be attempted if the server [or proxy] doesn't have a v6 global address [because it's never going to work]. |
| Comment by Oliver Krüger [ 2021 Jun 15 ] |
|
I ran into this on the current LTS version (5.0). (Have a few ipv4 addr only hosts, which reported 50% packet loss until I temporarily disabled ipv6 by setting an empty Fping6location.) Tried to work around this bug with a recent version of fping, but unfortunately v5.0 of fping is not backward compatible. |
| Comment by Oleksii Zagorskyi [ 2021 Oct 27 ] |
|
ZBX-18467 might be related. |
| Comment by Mihails Prihodko [ 2023 Apr 28 ] |
|
Note: Starting from fping-4.0 (2017-04-23), there is a single binary for IPv4 and IPv6 https://github.com/schweikert/fping/blob/develop/CHANGELOG.md#fping-40-2017-04-23 |