Cecylia Bocovich bf924445e3 Implement NAT discovery (RFC 5780) at the client ... 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).		2020-07-06 13:16:03 -04:00
..
interfaces.go	Remove SnowflakeDataChannel interface.	2020-04-27 18:48:00 -06:00
lib_test.go	Eliminate separate WebRTCPeer.Connect method.	2020-04-27 18:47:59 -06:00
peers.go	Remove Snowflake interface, use *WebRTCPeer directly.	2020-04-27 17:51:21 -06:00
rendezvous.go	Implement NAT discovery (RFC 5780) at the client	2020-07-06 13:16:03 -04:00
snowflake.go	Reduce SnowflakeTimeout to 20 seconds	2020-05-07 09:42:09 -04:00
turbotunnel.go	Turbo Tunnel client and server.	2020-04-23 16:02:56 -06:00
util.go	Simplify BytesSyncLogger.	2020-04-23 21:38:44 -06:00
webrtc.go	Format the establishDataChannel error log message like other log messages.	2020-05-01 10:30:04 -06:00