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
Fix new TTL based NAT hole punching for mobile #1788
Conversation
1a5b237
to
0a60adb
Compare
0a60adb
to
3c41758
Compare
@@ -35,6 +34,8 @@ import ( | |||
"github.com/rs/zerolog/log" | |||
) | |||
|
|||
const natPunchingMaxTTL = 10 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I suggest to change it to more clear name like natPunchingPortsLen
etc. In this context TTL is a bit confusing with IP packets TTL.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The number of ports is needed to test all TTL values up to the natPunchingMaxTTL
.
3c41758
to
348fbde
Compare
Codecov Report
@@ Coverage Diff @@
## master #1788 +/- ##
==========================================
+ Coverage 46.81% 46.82% +<.01%
==========================================
Files 281 281
Lines 11565 11574 +9
==========================================
+ Hits 5414 5419 +5
- Misses 5726 5731 +5
+ Partials 425 424 -1
Continue to review full report at Codecov.
|
No description provided.