Split Tunnel Docker Containers
|
Posts: 3
Threads: 1
Joined: Mar 2021
Reputation:
0
[Not Solved]
Mar 16, 2021, 05:02 PM
Hi,
I have setup the split tunnel, following the excellent guide posted on this site. I however run my BT app in a container and the container is not being routed through the VPN, but directly.
The container is being run with the same UID/GUID as the vpn user (as per the tutorial)
Does anyone have any suggestions on what changes need to be made to the iptables and routing files to force the container to use the split tunnel?
Thanks a stack.
Posts: 3
Threads: 1
Joined: Mar 2021
Reputation:
0
[Not Solved]
Mar 31, 2021, 01:41 PM
(Mar 16, 2021, 05:02 PM)nie Wrote: Helow all,
Found a solution to the below question.
If you would prefer to run your services in containers and have them route out over a VPN, you can share the network of your VPN container with your other containers.
I have used this container as my vpn service https://hub.docker.com/r/qmcgaw/gluetun, follow the instructions and deploy the vpn container (it is preconfigured to work with a number of popular VPN services, but sadly lacks one or two of the big names.
1. Deploy the glueton container, as part of the configuration, you will need to map the ports you would normally expose for your other containers (e.g for Jackett "-p 9117:9117" and any other ports you need.
2. When deploying your service container (e.g linuxserver/jackett) you need to remove the port mappings from the configuration (as they now reside in the vpn container) and you need to share the network: e.g. "--network container:gluetun"
3. Check that the jackett container is using the VPN but "docker exec -ti jackett /bin/bash" and run "curl ipinfo.io" and you should see your VPNs IP if all worked well.
Things to check are the configuration of the VPN Region, this needs to be worded exactly, check the gluetun logs to see if there are any issues and what needs to be corrected.
-----------
Hi,
I have setup the split tunnel, following the excellent guide posted on this site. I however run my BT app in a container and the container is not being routed through the VPN, but directly.
The container is being run with the same UID/GUID as the vpn user (as per the tutorial)
Does anyone have any suggestions on what changes need to be made to the iptables and routing files to force the container to use the split tunnel?
Thanks a stack.
Posts: 38
Threads: 1
Joined: Oct 2021
Reputation:
0
[Not Solved]
Mar 11, 2023, 04:32 AM
(This post was last modified: Jun 02, 2023, 01:33 AM by jonescelinaa.)
(Mar 31, 2021, 01:41 PM)neiliid Wrote: (Mar 16, 2021, 05:02 PM)nie Wrote: Helow all,
Found a solution to the below question.
If you would prefer to run your services in containers and have them route out over a VPN, you can share the network of your VPN container with your other containers.
I have used this container as my vpn service https://hub.docker.com/r/qmcgaw/gluetun uno online , follow the instructions and deploy the vpn container (it is preconfigured to work with a number of popular VPN services, but sadly lacks one or two of the big names.
1. Deploy the glueton container, as part of the configuration, you will need to map the ports you would normally expose for your other containers (e.g for Jackett "-p 9117:9117" and any other ports you need.
2. When deploying your service container (e.g linuxserver/jackett) you need to remove the port mappings from the configuration (as they now reside in the vpn container) and you need to share the network: e.g. "--network container:gluetun"
3. Check that the jackett container is using the VPN but "docker exec -ti jackett /bin/bash" and run "curl ipinfo.io" and you should see your VPNs IP if all worked well.
Things to check are the configuration of the VPN Region, this needs to be worded exactly, check the gluetun logs to see if there are any issues and what needs to be corrected.
-----------
Hi,
I have setup the split tunnel, following the excellent guide posted on this site. I however run my BT app in a container and the container is not being routed through the VPN, but directly.
The container is being run with the same UID/GUID as the vpn user (as per the tutorial)
Does anyone have any suggestions on what changes need to be made to the iptables and routing files to force the container to use the split tunnel?
Thanks a stack.
Nice solution, I tried it and it worked, thanks for sharing
Posts: 9
Threads: 0
Joined: Feb 2022
Reputation:
0
[Not Solved]
Mar 25, 2023, 11:08 AM
ทางเข้าเล่น mega gameสนุกสนานได้บนเบราว์เซอร์เพลิดเพลินผ่านโทรศัพท์มือถือและอุปกรณ์เคลื่อนที่สะดวกรองรับทุกแพลตฟอร์มอยู่ที่ไหนก็เดิมพันกันได้สัมผัสความสนุก ความตื่นเต้นทุกครั้งที่เข้าเล่นด้วยตัวเองสำหรับสมาชิกรับโบนัส โปรโมชั่นพิเศษได้ทันที
Posts: 38
Threads: 1
Joined: Oct 2021
Reputation:
0
[Not Solved]
Nov 02, 2023, 02:05 AM
(This post was last modified: Nov 02, 2023, 02:05 AM by jonescelinaa.)
pyramids continue to be a subject spacebar clicker of study and fascination. Archaeologists, historians, and tourists from around the world visit these ancient wonders to unlock their mysteries and learn about the civilizations that built them.
Posts: 70
Threads: 1
Joined: Jul 2021
Reputation:
0
[Not Solved]
Mar 27, 2024, 03:10 AM
Online gaming can help Spotle improve self-confidence, as players often feel a sense of pride when they succeed.
|
|
Recent Posts
|
About Swap
jonescelinaa Apr 10, 2024, 06:58 AM
|
Tracker Status: Error Connection Time Out
jonesPhedra Apr 04, 2024, 08:17 AM
|
Split Tunnel Docker Containers
jonesPhedra Mar 27, 2024, 03:10 AM
|
Plex server not powerful enough, but only with s...
jonesPhedra Mar 27, 2024, 03:02 AM
|
game Geometry Dash Scratch
jonescelinaa Jan 31, 2024, 04:21 AM
|
Latest unread posts | Unanswered posts |
|