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.
DisableIPv6Discovery
to revert the behavior back to IPv4 only. Default value isfalse
, so existing config will default to using IPv6 when possible without user manually changing the config file.Tested between my Windows 10 PC and a Raspberry Pi, using the hosted management and signal server (https://app.netbird.io/)
Closes #577
Some notes:
Link-local IPv6 addresses (e.g.
fe80:*
) are filtered out, unlike IPv4 address (e.g.10.0.4.3
is not filtered out).I don't have a Unique local address so I don't know if that's also being filtered out.
ice.Candidate
with IPv6 host are formatted similar tofe80::1:51820
, this only affects the log output, might be a good idea to submit a fix upstream later.Filtered log from testing:
Public keys are replaced with
<WG_PUBLIC_KEY_1>
<WG_PUBLIC_KEY_2>
IPv4 Addresses are replaced with
999.999.999.999
IPv6 Addresses are masked with
xxxx