-
-
Notifications
You must be signed in to change notification settings - Fork 407
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: Firewall fails to start on IPv6 rule #1583
Comments
I have this exact same issue, except I'm using docker instead of kubernetes: Is this urgent? Host OS CPU arch VPN service provider What are you using to run the container What is the version of Gluetun What's the problem thinking Share your logs
|
Just tested with this on v3.34.0 and v3.33.0.
|
Aha, can confirm that this issue is not present in 3.33.0. |
Probably due to 0a29337 I'll investigate |
Can someone post debug logs of the v3.33.0 image to compare please? I see the problem (mixing ipv4 and ipv6), but I'm trying to nail down why the heck this is happening now to ideally avoid an ugly obscure if block to resolve this 😄 EDIT: also once this finishes building, can someone try image |
Firewall debug logs on v3.33.0
|
Logs for 3.34.0:
Logs for 3.33.0 (connection info redacted):
|
Can you try image PS:
|
This image tag works for me now |
Same here. The PR image is working for me. |
Does it log something like |
I don't see this, but I do not have debug logging enabled at this time - I can try enabling it in a bit. |
The PR image works for me as well. I can give logs, but after a little Googling, still not sure how to change the log level to DEBUG, any pointers? I am using docker-compose. |
@cohenchris Add |
@qdm12 I do not see this message in my container. Thanks for this fantastic project! Have been using it daily for a few years. |
Thanks everyone for the confirmation! I made the minimal changes to fix v3.34.0 in 6d48f9c and released v3.34.1. The latest image has that fix as well, but the if check + debug log to prevent mixing IP families in the routing is removed, please feel free to try it 😉 |
Is this urgent?
None
Host OS
Debian Buster
CPU arch
x86_64
VPN service provider
Private Internet Access
What are you using to run the container
docker run
What is the version of Gluetun
qmcgaw/gluetun:v3.34.0
What's the problem 🤔
I'm running gluetun in a kubernetes cluster. The container fails to start with the firewall enabled when creating an ipv6 output rule. It's attempting to configure the rule with an IPv4 source address, which fails.
Share your logs
Share your configuration
The text was updated successfully, but these errors were encountered: