Bug: VPN_PORT_FORWARDING_LISTENING_PORT not working #2354
Comments
|
@qdm12 is more or less the only maintainer of this project and works on it in his free time.
|
|
Hi @N47H4N ! To be honest, I haven't tested it really since I don't have VPN port forwarding with my current provider. to redirect traffic coming on 46843 to port 80, for both tcp and udp. What you can try is to:
|
|
Hi @qdm12 Thx for your answer. I tried to add prerouting rule without the -d 127.0.0.1 without success. still not working If needed, I can give you a ProtonVPN account in PM. Let me know. thx |
Yes let's do this (as long as you can revoke and update the credentials 😉). If you want you can send me your Wireguard private key only, since Protonvpn now supports Wireguard! Curious also to see if port forwarding works with Wireguard 😄 ! My email [email protected] |
|
Well received 👍 basically was meant to be: and there was a missing INPUT table rule: (Same applies for UDP, and ip6tables for IPv6). This all fixed now, and tested to be working 😉 If you don't mind, can you please leave your wireguard key un-revoked until #2334 is resolved? I'm about to do a v3.39.0 release and jump on this issue, and having VPN server port forwarding helps to reproduce this issue. You may also be impacted by that issue I guess! You can subscribe to that other issue, and revoke the key when it gets closed (in case I forget to tell you to revoke it!). If that's a problem, no problem either, feel free to go ahead and revoke it 👍 Thanks again! |
|
Closed issues are NOT monitored, so commenting here is likely to be not seen. This is an automated comment setup because @qdm12 is the sole maintainer of this project |
|
Hi @qdm12 , Thx for the update ! but I still can't make it works. I'm running the version 74ea1a0.
but if I do a curl outside the gluetun container, nothing inside my second container: Here is my url with ProtonVPN: http://79.135.104.13:37670/ no worries for the wireguard key, you can keep it as long as you want ! |
|
It's working for me, but, be warned, oddly, it doesn't work if querying the public-ip:port-forwarded from within Gluetun for some reason. My commands are:
However, replacing step 3 with: Does not work, and I'm not sure why, the firewall doesn't look like it's handling it at all either (checking |
Blocking port access from the same connection can be part of mitigating the Port Fail vulnerability. ProtonVPN however seems to be masking IPs instead of outright blocking connections, sooo... 🤷 |
|
@N47H4N any news now? Does it work fine / can this issue be closed? |
|
@qdm12 still not working. it's working into the gluetun container, but not with another container linked to my gluetun with --network=container:GluetunVPN-WG |
Whoops, that's odd, I'll check! |
|
It's still working for me:
Are you sure you don't have some extra firewall somewhere blocking it? What program are you using to listen through gluetun? |
|
I was wrong, the problem was on my side! Your work is awesome! thank you for your support ! |
|
Closed issues are NOT monitored, so commenting here is likely to be not seen. This is an automated comment setup because @qdm12 is the sole maintainer of this project |
Is this urgent?
No
Host OS
Unraid 6.12.10
CPU arch
x86_64
VPN service provider
ProtonVPN
What are you using to run the container
Unraid
What is the version of Gluetun
Running version latest built on 2024-07-09T14:47:46.048Z (commit 0501743)
What's the problem 🤔
The feature VPN_PORT_FORWARDING_LISTENING_PORT seems not to work.
from my gluetun container, I can see my 2 listening port from my Speedtest container (the two first line 80 + 443)
If I do a tcpdump in my gluetun container, I can see traffic coming from my VPN Port Forwarded
but nothing on my second docker container on port 80
So basically, I tried to forward my VPN port 46843 to my Speedtest Container on port 80
Am I doing something wrong ? Thx for your help
Share your logs (at least 10 lines)
Share your configuration
The text was updated successfully, but these errors were encountered: