ice: experimental local-relay candidate #30
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
algesten
force-pushed
the
feature/dynamic-local-ip
branch
from
8991f8c
to
4dc8340
Compare
algesten
force-pushed
the
main
branch
2 times, most recently
from
8c3903e
to
0ded9f5
Compare
algesten
force-pushed
the
main
branch
5 times, most recently
from
a491dda
to
32b0f89
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
If we configure a host candidate IP 2.2.2.2, but the incoming traffic actually appears from 3.3.3.3, this PR makes a "local relay" candidate. It's considered a relay because it most likely happens due to some NATed config.
This is a non-spec type that maybe it's a bad idea.