Fix local candidate priority assignment #103
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
In multi-homed or dual-stack (i.e. both IPv4 and IPv6) configurations,
local candidates must use unique local preferences for the same
candidate type preference and component ID. Otherwise, the controlling
and controlled agent could pick different candidates.
This commit uses a simple interleaved down-counter, starting the
local preference at 65534 for IPv4 and 65535 for IPv6, decrementing
each by two per local candidate.
Fixes #102