-
-
Notifications
You must be signed in to change notification settings - Fork 50
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
IPv6 support missing since v4.0.0 #134
Comments
I will not undo it, as it fixes other issues. This is an upstream issue. Once that is fixed, I'm happy to extend it. |
Could you leave this issue open so we can keep track of it? Unfortunately I'll have to stay on 3.0.0 until IPv6 works again. Do you have any workaround for now? :) |
The issue is tracked upstream, there is nothing to do on this end. Keeping the issue open merely pollutes my work environment. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Problem/Motivation
Because of binding DNS server to IPv4 interface, the IPv6 interface is missing.
For my network setup, which consists of IPv4 and IPv6 addresses , ad blocking is broken ever since.
Expected behavior
Binding of DNS services to IPv4 and IPv6 relevant interfaces.
Actual behavior
Only blocking for IPv4 interface is enabled.
Steps to reproduce
Clean installation of add-on version 4.0.0
Proposed changes
Since there seems to be no option to add more than one standard interface to bind to (see issue), I would appreciate if you could undo PR #126 changes.
The text was updated successfully, but these errors were encountered: