this post was submitted on 01 Dec 2024
25 points (90.3% liked)

Selfhosted

60861 readers
1146 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:

Detailed Rules Post

  1. Be civil.

  2. No spam.

  3. Posts are to be related to self-hosting.

  4. Don't duplicate the full text of your blog or readme if you're providing a link.

  5. Submission headline should match the article title.

  6. No trolling.

  7. Promotion posts require active participation, with an account that is at least 30 days old. F/LOSS without a paywall has exceptions, with requirements. See the rules link for details. Tags [CBH] or [AIP] are required, see the links in Rule 8 for details.

  8. AI-related discussions and AI-involved promotional posts have additional requirements for tagging, as noted in Rule 7 and the AI & Promotional Post Expanded Rules post, and find example disclosures here.

Resources:

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

Questions? DM the mods!

founded 3 years ago
MODERATORS
 

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?

all 5 comments
sorted by: hot top controversial new old
[–] FrostyCaveman@lemm.ee 3 points 2 years ago (1 children)

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 2 years 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  
[–] seang96@spgrn.com 0 points 2 years ago (1 children)

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 2 years ago

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