Netgate Discussion Forum
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Search
    • Register
    • Login

    IPv6 & Docker Routing -can't ping IPv6 enabled container

    IPv6
    1
    1
    240
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • A
      alnico
      last edited by

      I have a PC that I have installed Docker on (host is Ubuntu 23.10). I am trying to ping the IPv6 address in the individual containers but I am unable to get the routing right.

      My ISP assigns me a /56 prefix. My docker server is on VLAN 9, VLAN id is "SERVER".

      This is the topology:
      docker.png

      • The docker host IPv6 address is '24xxxxx09:60e:3cff:fea7:702f'
      • The container network name is "proxy" having network details:'24xx:xxxx:xxx:xxd0::/112'

      From the Ubuntu host server, I can ping into a container IP
      pingin.png

      From a container shell, I can ping externally such as Google:
      9b805736-08ac-47fe-8eb6-c22cf3169466-image.png

      These are my Pfsense router settings:

      • I have defined a static route for network '24xx:xxxx:xxx:xxd0::1/112' to be reachable via '24xxxxx09:60e:3cff:fea7:702f' (Ubuntu host IP address)

      Gateway:
      10dcaed3-d169-4c21-8f17-dd0c00d2219b-image.png

      Static Route
      9c90d377-bac5-4f5a-b131-735b3167b92f-image.png

      Firewall rules
      For "SERVER" VLAN
      7ff29f30-e564-404e-b264-74e645ecef42-image.png

      Dockernet Alias
      088ecc21-c0ce-4d8f-b14a-e82646874dda-image.png

      Docker settings - this the default bridge defined in /etc/docker/daemon.json
      cb981397-bc08-4b73-a684-5b3ea43b995e-image.png

      Docker "proxy" network
      bf9d3b30-3288-4b97-a913-5bd2449d61c6-image.png

      When I ping a container IP address from Pfsense, I get no result
      2855305f-5fd3-4966-b87e-8ff6852137c8-image.png

      I am missing something very basic here, but I can't seem to figure out why it won't route properly to the containers' IPs. Any ideas?

      1 Reply Last reply Reply Quote 0
      • First post
        Last post
      Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.