Skip to content

Conversation

@cohosh
Copy link
Owner

@cohosh cohosh commented Jun 10, 2020

Snowflake clients will now attempt NAT discovery using the provided STUN
servers and report their NAT type to the Snowflake broker for matching.
The three possibilities for NAT types are:

  • unknown (the client was unable to determine their NAT type),
  • restricted (the client has a restrictive NAT and can only be paired
    with unrestricted NATs)
  • unrestricted (the client can be paired with any other NAT).

cohosh added 5 commits June 10, 2020 17:57
Snowflake clients will now attempt NAT discovery using the provided STUN
servers and report their NAT type to the Snowflake broker for matching.
The three possibilities for NAT types are:
- unknown (the client was unable to determine their NAT type),
- restricted (the client has a restrictive NAT and can only be paired
with unrestricted NATs)
- unrestricted (the client can be paired with any other NAT).
Now when proxies poll, they provide their NAT type to the broker. This
introduces a new snowflake heap of just restricted snowflakes that the
broker can pull from if the client has a known, unrestricted NAT. All
other clients will pull from a heap of snowflakes with unrestricted or
unknown NAT topologies.
These unittests need to be updated for the new Version 1.2 messaging
specification.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants