We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
There was an error while loading. Please reload this page.
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
dhcpcd uses the interface metric (priority) with respect to default route and DNS configuration.
My multi-interface use-case is taking other factors into consideration, resulting in a dynamic interface metric.
dhcpcd wlan0 -m <val> --reconfigure had no effect, whereas dhcpcd wlan0 -m <val> --rebind did.
However, the latter involves an unnecessary exchange with the server. Am I missing something that would allow the former?
The text was updated successfully, but these errors were encountered:
I don't see a reason why --recconfigure shouldn't work. I'll see if I can find the time to look into it.
Sorry, something went wrong.
No branches or pull requests
Uh oh!
There was an error while loading. Please reload this page.
dhcpcd uses the interface metric (priority) with respect to default route and DNS configuration.
My multi-interface use-case is taking other factors into consideration, resulting in a dynamic interface metric.
dhcpcd wlan0 -m <val> --reconfigure had no effect, whereas dhcpcd wlan0 -m <val> --rebind did.
However, the latter involves an unnecessary exchange with the server. Am I missing something that would allow the former?
The text was updated successfully, but these errors were encountered: