CentOS 7

As commented on IRC

23:42 < volter > RoyK: I wonder, does it also happen if you specify a name that resolves to an IPv6 address?

It doesn't, that is, it works with choosing "Connect to DNS"

...and as further discussed on IRC, it's just that Zabbix does not include the IP address in square brackets when ipv6 address is used together with port

The problem is not that port is put inside "[...]" but that "[...]" are not put around IPv6 address (URL and port are set with independent curl_easy_setopt()). Misleading log message can be improved too:

		zabbix_log(LOG_LEVEL_DEBUG, "%s: curl_easy_perform failed for [%s:%hu]: %s",
				__function_name, host, port, curl_easy_strerror(err));

As a workaround you can try net.tcp.service[https,"[{HOST.IP}]"].

Fixed in svn://svn.zabbix.com/branches/dev/ZBX-11864

Added an explicit check in the check_https() function located in ./src/libs/zbxsysinfo/simple/simple.c:167.
Improved also the failure message in case the check will fail.

Successfully tested

(1) I think libcurl will handle URL with IPv6 address even if Zabbix is compiled without --enable-ipv6 option.

abs Of course it boils down on how the customer compiled LibCURL itself (or how it was packaged by the distributor of the system you are using), Do you think we should explicitly deny the functionality IF we encounter an IPv6 address, in the case zabbix is compiled without IPv6 support (BTW, the converse is also true. There is the potential case where Zabbix will be compiled with IPv6 support and LibCURL not)?

glebs.ivanovskis I think that since Zabbix does not do any IPv6 work in this case (except validation and wrapping in "[...]") we should always pass URL to libcurl and see what happens.

abs Make sense, if we get rid of the HAVE_IPV6 check:

#ifdef HAVE_IPV6
	if (SUCCEED == is_ip6(host))
		zbx_snprintf(https_host, sizeof(https_host), "%s[%s]", (0 == strncmp(host, "https://", 8) ? "" : "https://"), host);
	else
#endif
		zbx_snprintf(https_host, sizeof(https_host), "%s%s", (0 == strncmp(host, "https://", 8) ? "" : "https://"), host);

In the worst case the communication between server and agent will not work, but the https checks yes. So, going to get rid of the pre-processor check

abs FIXED in r66360

wiper The is_ip6() function is no defined without HAVE_IPV6 define
REOPENED

abs Right, completely forgot that we can't use that without the HAVE_IPV6 flag glebs.ivanovskis, we must keep the implementation as it was, unless we move the is_ip6() function out from the HAVE_IPV6 range, but this doesn't make sense. IMHO, leave the HAVE_IPV6 condition as it was.

abs Fixed in 66370

Reverted last commit to previous state. Keep the HAVE_IPV6 as conditional compilation

wiper Actually I liked Gleb's idea, so I thought we could simply remove HAVE_IPV6 define for is_ip6() function.

abs RESOLVED in r66373

Me, glebs.ivanovskis and wiper agreed that it's a good idea to have the is_ip6() function generally available.

wiper CLOSED

Successfully tested

Fixed in:

• 2.2.18rc1
• 3.0.9rc1
• 3.2.5rc1
• 3.4.0alpha1 (trunk)