Hi,
IPv6 adresses, unlike IPv4, can have letters (a to f) in them. Currently (5.36.0), it is not really possible to use ICMP with IPv6:
icmp://[2a07:6b44:27:11::ac]
=> gatus starts, but no pings for this endpoint are performed.
icmp://2a07:6b44:27:11::ac
=> gatus refuses to start, interpreting the ac part of the address as a invalid port number
icmp://[2a07:6b44:27:11::21]
=> gatus starts and no pings are performed.
icmp://2a07:6b44:27:11::21
=> gatus starts and pings are performed.
I'm wondering why address handling is a problem, I haven't looked at the code yet, but I would expect that there's a golang module to use that does evertyhing right.
Regards,
Daniel
Hi,
IPv6 adresses, unlike IPv4, can have letters (a to f) in them. Currently (5.36.0), it is not really possible to use ICMP with IPv6:
icmp://[2a07:6b44:27:11::ac]=> gatus starts, but no pings for this endpoint are performed.
icmp://2a07:6b44:27:11::ac=> gatus refuses to start, interpreting the
acpart of the address as a invalid port numbericmp://[2a07:6b44:27:11::21]=> gatus starts and no pings are performed.
icmp://2a07:6b44:27:11::21=> gatus starts and pings are performed.
I'm wondering why address handling is a problem, I haven't looked at the code yet, but I would expect that there's a golang module to use that does evertyhing right.
Regards,
Daniel