26

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?

top 5 comments
sorted by: hot top controversial new old
[-] FrostyCaveman@lemm.ee 3 points 3 weeks 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.dev 3 points 3 weeks 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.pub 1 points 3 weeks ago* (last edited 3 weeks 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.com 0 points 3 weeks ago

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

OPENVPN_MSSFIX='1350'

[-] pe1uca@lemmy.pe1uca.dev 1 points 3 weeks ago

Same problem.
I tried a few values and the same, ping works but curl doesn't.

this post was submitted on 01 Dec 2024
26 points (93.3% liked)

Selfhosted

40719 readers
348 users here now

A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.

Rules:

  1. Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.

  2. No spam posting.

  3. Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.

  4. Don't duplicate the full text of your blog or github here. Just post the link for folks to click.

  5. Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).

  6. No trolling.

Resources:

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

founded 2 years ago
MODERATORS