-
Quick praise: gluetun is super impressive. I'm relatively new to docker and self-hosting. But this is one of the most polished, well-documented and easy to use projects I've come across. I set it up and it's working flawlessly so far. Kudos! My question: let's say the connection to the VPN is lost or some other error happens, is there any possibility of information leaking? I'm guessing there isn't, since all traffic goes through the gluetun container and I'm sure that one is set up to not leak any information. But if I read a line somewhere confirming this, my mind would be a lot more at ease. Maybe it would also make sense to add a line explaining this to the main readme? I'm sure I'm not the only noob-ish person wondering about this. |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 1 reply
-
Praise appreciated thanks!!
Yes the firewall takes care to only allow inbound from your lan and outbound is allowed only though the vpn network interface, at the vpn server ip and at the vpn server port. This gets enabled about 15ms after container start (can't do faster for now) and gets removed before container shutdown only. I should probably add this to the wiki somewhere 😄
There are too many features in the readme haha, but it's already in there (with a grammar/typo I just spotted):
|
Beta Was this translation helpful? Give feedback.
Praise appreciated thanks!!
Yes the firewall takes care to only allow inbound from your lan and outbound is allowed only though the vpn network interface, at the vpn server ip and at the vpn server port. This gets enabled about 15ms after container start (can't do faster for now) and gets removed before container shutdown only.
I should probably add this to the wiki somewhere 😄
There are too many features in the readme haha, but it's already in there (with a grammar/typo I just spotted):