gluetun: Bug: Containers behind gluetun not being able to access local LAN
TLDR: Describe your issue in a one liner here
-
Is this urgent?
- Yes
- No
-
What VPN service provider are you using?
- PIA
- Mullvad
- Windscribe
- Surfshark
- Cyberghost
-
What’s the version of the program?
latest
-
What are you using to run the container?
- Docker run
- Docker Compose
- Kubernetes
- Docker stack
- Docker swarm
- Podman
- Other:
-
Extra information
Logs:
Configuration file:
Host OS: Debian
Hi,
since the removal of the “extra subnets” environment variable, containers behind gluetun are not able to reach the local network any longer. Is this intentional? Any way around this, as it unfortunately completely breaks my setup.
Best regards!
About this issue
- Original URL
- State: closed
- Created 4 years ago
- Reactions: 2
- Comments: 22 (7 by maintainers)
Commits related to this issue
- Refers to #273 — committed to qdm12/gluetun by qdm12 4 years ago
- Source to local IP instead of local subnet (#273) — committed to qdm12/gluetun by qdm12 4 years ago
My containers reach Gluetun (and PIA network) perfectly fine, but can no longer communicate across container using LAN addresses after the latest update. I am on a v4 PIA network opvn file.
I have them configured as follows:
PIA Gluetun container is set up with image: qmcgaw/private-internet-access container_name: pia cap_add: - NET_ADMIN network_mode: bridge environment: - EXTRA_SUBNETS=192.168.0.0/24 ports: - xxxx:xxxx
other_containers network_mode: service:pia # run on the vpn network
My other containers used to communicate using their LAN ip and port with no problems (192.168.0.48:xxxx), but cannot see each other anymore.
Weirdly though I can access them individually via web-browser, so it is only docker containers communicating with each other that seems to struggle?