What is the status of IPv6 support for PRTG's web GUI? It seems to only listen on IPv4 addresses. In 2013, this is pretty unacceptable. IPv6 *is* getting used in the real world nowadays.
In a dual-stack environment, listening only on IPv4 means that the browser first tries reaching the web GUI on the server's IPv6 interface, introduces a short wait while this attempt fails, then tries the IPv4 address. Tolerable, but far from ideal.
Worse, this makes it impossible to access the web GUI from a Microsoft DirectAccess client. DirectAccess, being a technology of the modern "cloudy" "borderless" sort of paradigm, does not support IPv4 at all. It can connect to IPv4 servers using the DNS64/NAT64 transition mechanism, but the transition mechanism does not get invoked if the server has an IPv6 address. The client assumes that a server having both address families will provide its service on both, which is a reasonable assumption IMO.
I could disable the IPv6 stack on the server as a workaround... but then what if I need PRTG to monitor IPv6 devices?
I guess I could always install Apache on the server and have it listen on the IPv6 interface and be a reverse-proxy to the web GUI... but that would be an unpleasant hack more suited to 2005 than 2013.
Is there any timeline as to when PRTG will support IPv6 properly (i.e. completely)?