I’m having issue making a container running in the network of gluetun to access the host.

In theory there’s a variable for this: FIREWALL_OUTBOUND_SUBNETS
https://github.com/qdm12/gluetun-wiki/blob/main/setup/connect-a-lan-device-to-gluetun.md#access-your-lan-through-gluetun
When I include 172.16.0.0/12 I can ping the ip assigned with host-gateway but I can’t curl anything.

The command just stays like this until it timesout

# curl -vvv 172.17.0.1
*   Trying 172.17.0.1:80...

I also tried adding 100.64.0.0/10 to connect to tailscale but is the same response, can ping and timedout curl.

Any other request works properly connected via the VPN configured in gluetun

Do you guys have any idea what I might be missing?

  • FrostyCaveman@lemm.eeEnglish
    3·
    3 days ago

    Networking is always fun to debug… haha. I tried to replicate your issue but was unable to. Are you using docker, kubernetes or something else? Would be helpful if you could post your docker-compose.yml, kubernetes object manifests or other relevant config.

    • pe1uca@lemmy.pe1uca.devOPEnglish
      3·
      2 days ago

      Found the issue '^-^
      UFW also blocks traffic between docker and host.
      I had to add these rules

      ufw allow proto tcp from 172.16.0.0/12 to 172.16.0.0/12 port 80  
ufw allow proto tcp from 172.16.0.0/12 to 172.16.0.0/12 port 443
  • alwayssitting@infosec.pubEnglish
    1·
    3 days ago

    There might be a conflict due to the fact that docker itself usually uses the 172.17.0.0/16 subnet for the default bridge network

  • seang96@spgrn.comEnglish
    0·
    4 days ago

    If you are using openvpn this env may be a good thing to try. It may need adjusted though.

    OPENVPN_MSSFIX=‘1350’