You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
maoyuanpeng opened this issue
Nov 7, 2022
· 1 comment
Labels
enhancementNew feature requests or performance improvement.wontfixA potentially valid point has been made, but a decision has made not to address this issue.
After my tests, I found that it seems that only udp can be used to punch holes. If tcponly is set, the network traffic will be transferred through the host with the public IP.
I kown udp holes punching is better than tcp. But in my area, udp will be restricted and qos.
The text was updated successfully, but these errors were encountered:
Unfortunately, only UDP hole punching is supported. TCP hole punching is working differently is much harder to do, and while perhaps not impossible, this is not something that I plan to support.
gsliepen
added
enhancement
New feature requests or performance improvement.
wontfix
A potentially valid point has been made, but a decision has made not to address this issue.
labels
Nov 8, 2022
enhancementNew feature requests or performance improvement.wontfixA potentially valid point has been made, but a decision has made not to address this issue.
After my tests, I found that it seems that only udp can be used to punch holes. If tcponly is set, the network traffic will be transferred through the host with the public IP.
I kown udp holes punching is better than tcp. But in my area, udp will be restricted and qos.
The text was updated successfully, but these errors were encountered: