Connection Monitor IPv6 not working

[s0ftcorn]

Im pretty sure this isnt an issue about my setup, but i i just recently started using this awesome project, which means i cant confirm this 100%. Im using docker compose.
Basically the connection monitor is unable to ping any IPv6 address, but any other containers can. Even the docsight container can when installing inetutils-ping. I tried different DNS servers (google, cloudflare), the DNS servers assigned to me by my ISP, golem.de and heise.de
Since another container im using is meshping and it works fine over there, i think we can rule out any issues with my setup.
Is there maybe anything missing in the documentation?

Here is my docker-compose.yml:

services:
  docsight:
    image: ghcr.io/itsdnns/docsight:latest
    container_name: docsight
    restart: unless-stopped
    network_mode: "host"
    cap_add:
      - NET_RAW
    ports:
      - "8765:8765"
    volumes:
      - docsight_data:/data
    environment:
      - TZ=Europe/Berlin  # fallback; timezone is configurable via the web UI

volumes:
  docsight_data:

Adding or removing network_mode: "host" doesnt have any influence on the issue.

[itsDNNS]

Confirmed, this is a DOCSight limitation rather than a Docker Compose issue.

Connection Monitor is IPv4-only in the current implementation:

• ICMP uses IPv4 raw sockets and gethostbyname().
• The bundled ICMP helper resolves with AF_INET only.
• TCP fallback also opens AF_INET sockets only.

So IPv6 literals or IPv6-only hostnames can be reachable from the container, but DOCSight still records them as timeouts because it never attempts ICMPv6 or IPv6 TCP.

Tracked here: #361

[itsDNNS]

This should be implemented now in the latest build via #362.

Please update to the latest version and test the same target again.

[s0ftcorn]

Confirmed, IPv6 addresses are now reachable.

Not sure if this is the right place to bring this up, but the traceroute functionality of the connection monitor might have been overlooked. I didnt have the time to make sure its not an issue with my setup, though meshping doesnt have the issue.

[itsDNNS]

Good catch. The IPv6 fix in #362 covered the normal Connection Monitor probes, but traceroute uses the separate docsight-traceroute-helper, and that path was still IPv4-only.

Fixed now in #364, merged to main. It adds ICMPv6 traceroute support and keeps the existing IPv4 output/exit behavior compatible.

Once the next image from main is available, please update and test traceroute again.

[s0ftcorn]

Yup, works as intended.