Docker Compose setup: Native IPv6

[doschn]

Describe the Bug

Following the Docker Compose setup guide traefik doesn't reveal the client's IPv6 Addresses within logs if requests are performed with native IPv6 only.

This is causing Problems with GeoIP based rules (blocked in my case) and showing wrong IP-Adresses within the Access-Logs (see screenshots attached)

Traefik logs also recorded the internal docker gateway address (172.18.0.1 in this case) - the internal GW address have been confirmed by docker network inspect pangolin (renamed default network according to guide).

Please update docs containing the solution below or ask me to create a PR for the docs.

Environment

• OS Type & Version: Rocky Linux 9.7 (Blue Onyx)
• Pangolin Version: 1.14.1
• Gerbil Version: latest
• Traefik Version: 3.4.0
• Newt Version: N/A
• Olm Version: (if applicable)

To Reproduce

Manual Docker Compose setup with IPv6 enabled host (but not docker network) and clients requesting IPv6 only (IPv4 disabled).

Expected Behavior

Traefik to show Client's real IPv6 Addresses instead of the internal docker networks gateway address.

This can be achieved by enabling IPv6 within the docker network as following:

networks:
  default:
    driver: bridge
    name: pangolin
    enable_ipv6: true # Uncomment if host uses native IPv6 and AAAA DNS records for the pangolin domain are set 

after this change Traefik was enable to record the native IPv6, not the internal IPv4 NAT Docker Gateway Address.

[doschn]

accidentally closed by comment of a commit in my private repo containing a fixed compose file.

[AstralDestiny]

It's due to some badger stuff, Both devs have been bugged by me for a while now for fixing ipv6 issues. However backend services are not affected. The enable_ipv6 should be there it has to be there either way as most aren't running with full ipv6 on the daemon. Which at the same time can cause some issues if you use any vpn containers as they don't know how to handle v6 so it just complains.

[github-actions]

This issue has been automatically marked as stale due to 14 days of inactivity. It will be closed in 14 days if no further activity occurs.

[usmandilmeer]

Anybody help me solving the issue of getting docker pangolin network gateway IP in dashboard.

[doschn]

Anybody help me solving the issue of getting docker pangolin network gateway IP in dashboard.

Try to add ipv6 to the network configuration in the compose file as follows (see initial issue):

enable_ipv6: true

[github-actions]

This issue has been automatically marked as stale due to 14 days of inactivity. It will be closed in 14 days if no further activity occurs.