-
Notifications
You must be signed in to change notification settings - Fork 1.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[WIP] Update pion/ice to v0.5.x (new TURN client) #740
Conversation
Hmm...
@Sean-Der Any idea? I wonder why this happens at webrtc level. Actually, control message is no longer used in pion/turn. I may have to clearn that up, but I'd like to know exactly what this means. |
Aggh... ok. I am going to completely remove ipnet folder:
|
Upgraded pion/transport to v0.8.6 Relates to pion/webrtc#740
Upgraded pion/transport to v0.8.6 Relates to pion/webrtc#740
Upgraded pion/transport to v0.8.6 Relates to pion/webrtc#740
Also update pion/transport to v0.8.6 Relates to pion/webrtc#740
TURN client's loc conn was not closed when agent.Close() was called Relates to pion/webrtc#740
Also update pion/transport to v0.8.6 Relates to pion/webrtc#740
TURN client's loc conn was not closed when agent.Close() was called Relates to pion/webrtc#740
c7ba240
to
071d004
Compare
Codecov Report
@@ Coverage Diff @@
## master #740 +/- ##
==========================================
- Coverage 76.71% 76.66% -0.05%
==========================================
Files 58 59 +1
Lines 4041 4050 +9
==========================================
+ Hits 3100 3105 +5
- Misses 686 690 +4
Partials 255 255
Continue to review full report at Codecov.
|
Relates to pion/turn#74
071d004
to
d9334b9
Compare
Thanks! Let me tag it as v2.0.24. |
Relates to pion/turn#74
This updates pion/ice to v0.5.1, which include a refactoring of CandidateRelay and a TURN client overhaul which resolves the connectivity issue with relay-prflx (symmetric NAT) pair.