-
-
Notifications
You must be signed in to change notification settings - Fork 385
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Bug: cannot remove allowed input port from firewall #2426
Comments
@qdm12 is more or less the only maintainer of this project and works on it in his free time.
|
Thanks for reporting the issue with so much details and help, 10/10 would fix again 💯 😄 ! Fixed in 946f055 - the code was expecting CIDR ranges suffixes to end with 1 to 2 digits, not 3 ( |
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 |
This isn't fixed, my bad, it's fixed for sure in 3f13093 😉 |
Hooray! Thanks :) Also thanks for gluetun. It sure makes docker vpns easy. :) |
Is this urgent?
No
Host OS
Ubuntu 22.04.4 LTS
CPU arch
x86_64
VPN service provider
ExpressVPN
What are you using to run the container
docker-compose
What is the version of Gluetun
Running version latest built on 2024-08-17T18:15:23.123Z (commit bc55c25)
What's the problem 🤔
In #2334 it was reported and fixed that removing iptables rules failed unless they were CIDR's. I then realized the fix may have broken ipv6 support, as shown in #2334 (comment)
Copied in here:
I just tried to set gluetun up with an asian VPN endpoint and I'm seeing stuff like the below. I think the endpoint is broken, so the container can't connect - that's fine, but I noticed the error below. :)
2024-08-18T11:54:32.769580445Z 2024-08-18T11:54:32Z ERROR [firewall] cannot remove outdated VPN interface rule: finding iptables chain rule line number: parsing chain list: parsing chain rule "3 0 0 ACCEPT 0 -- * eth0 ::/0 ff02::/104 ": parsing chain rule field: parsing destination IP CIDR: netip.ParsePrefix("ff02::/104/32"): ParseAddr("ff02::/104"): each colon-separated field must have at least one digit (at "/104")
I'm running a gluetun docker image with the source revision bc55c25 which is quite recent. So I found this issue.
Might the fix have missed something related to IPv6 addresses.. ff02::/104/32 seems like a mangled CIDR :)?
Share your logs (at least 10 lines)
The text was updated successfully, but these errors were encountered: