-
Can you add missing RFCs?
There are for STUN:
- RFC 3489 - "classic" STUN
- RFC 5389 - base "new" STUN specs
- RFC 5769 - test vectors for STUN protocol testing
- RFC 5780 - NAT behavior discov…
-
When I check the wireshark code for stun, I see some more RFC's
This is more a feature request.
* Please refer to the following specs for protocol detail:
* - RFC 3489 (Addition of deprecated at…
-
After untaking research it seems that the best route is to implement this spec and then refactor into RFC 5389
-
sir,why a test used 20 seconds?can it be faster?
NAT Type: Port restricted NAT
External IP Family: 1
External IP: 121.7.13.88
External Port: 10065
Time taken: 22.4233083
-
-
-
http://lshsblog.blogspot.kr/2011/04/hole-punching_18.html
위 문서를 보면 홀펀칭 기법에 대한 설명에 대해 나와있음
본문에 나와있지만 글쓴이가 해석을 하였어도 원문과 함께보길 권장함
믿에 참고할 만한 싸이트가 있다면 추가로 알려주세요
-
For example google ones:
> stun.l.google.com:19302
> stun1.l.google.com:19302
> stun2.l.google.com:19302
> stun3.l.google.com:19302
> stun4.l.google.com:19302
Test1 fails with "No changed address." …
-
## 问题发现
因为一直都是在路由器上用 natmap 打洞, 通过打洞出来的 tcp/udp 端口连回家里或访问开放的服务
最近一次远程回家, 要测试点东西. 就把 homeproxy 的 `Bypass CN traffic` 给关了. 结果远程连接直接就断了, 其他的服务也都挂了
## 初步检查
回家后检查是 keep-alive 服务器命中了 Direct 规则, (natma…
muink updated
4 months ago
-
While testing STUN over UDP, TCP & TLS over TCP, we found there is way to test it for both UDP & TLS over TCP. But we were not able to configure RTCPeerConnection to use STUN over TCP. Could you pleas…