-
Notifications
You must be signed in to change notification settings - Fork 21
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
Selected profile overrides IPv6 setting #182
Comments
Resolved by PR #183. |
The current implementation in #183 (commit 5fd9435 merged into develop) overrides the settings set in the For instance, disabling IPv4 in the
I think there is a precedence issue with #183. If no options are passed on the command line, the settings in the profile file should be used. |
It is a good observation. What #183 does is moving the setting of IPv4/6 until after the profile is loaded. I guess the issue was there before, but for some reason not observed or shadowed by the order. I will look into it, and provide a solution. |
Resolved by #185. |
If both profile (
--profile
) and IPv6 (--no-ipv6
/--ipv6`) are selected then the IPv6 setting will be overridden by the profile, but the other way around is expected.First run the test with
--no-ipv6
but no profile selected. Note the messages "IPv6 is disabled".Again run with
--no-ipv6
but also select a profile, which in this case is the same profile as would be used anyway. Note the messages "IPv6 is enabled".This issue was first reported as zonemaster/zonemaster-engine#856.
The text was updated successfully, but these errors were encountered: