zishuo/always-online-stun
1
0
Fork 0
mirror of https://github.com/pradt2/always-online-stun.git synced 2026-04-22 15:57:20 +08:00
Code Issues Packages Projects Releases Wiki Activity

Added NAT testing lists

Browse Source
This commit is contained in:
pradt2
2024-06-26 14:55:52 +01:00
parent 2c51b0355e
commit a436b413cd
1 changed files with 14 additions and 6 deletions
Download Patch File Download Diff File Expand all files Collapse all files
README.md
+14 -6
View File
@@ -41,14 +41,22 @@ Feel free to open an issue and let's discuss your specific needs.
### How often are the lists refreshed? ### How often are the lists refreshed?
Hourly, you can see the timestamp of the last check in the commit message. Hourly, you can see the timestamp of the last check in the commit message.
### What RFC spec do the servers conform to? ### What RFC specs do the servers conform to?
As long as the server correctly responds to an RFC5389 `BINDING` request, it is judged as healthy.
This is enough to establish the NAT mapping of a given socket.
_Noteworthy_: the server does not need to respond with an alternate IP address to be judged as healthy. The `valid_nat_testing_*` lists contain servers that should be capable of both NAT detection and behaviour testing. These capabilities
This can be a problem if you need a server with full RFC5389/5780 NAT testing (endpoint mapping and filtering modes) capability. roughly correspond to RFC5780 (and, implicitly, to RFC5389).
If you need a list of servers that support RFC5389/5780 NAT testing, open an issue. To qualify for these lists, a server has to correctly respond to a RFC5389 `BINDING` request and provide the `OTHER-ADDRESS` attribute in the response.
The presence of the `OTHER-ADDRESS` attribute is the spec-compliant way to advertise that a STUN server can be used for NAT behaviour tests.
_At the moment, no actual verification of the NAT behaviour testing capabilities is carried out.
We rely on the STUN server maintainers to set the `OTHER-ADDRESS` attribute only if their server supports NAT behaviour testing.
If that's a problem for you (i.e. you need a stronger guarantee), please open an issue._
The other `valid_*` lists contain servers that are capable of NAT detection only. These are much bigger lists as only a small fraction
of servers is configured to provide the full NAT testing capabilities.
To qualify for these lists, a server has to correctly respond to a RFC5389 `BINDING` request.
### What IP versions and transport protocols are tested? ### What IP versions and transport protocols are tested?
IP versions 4 and 6. UDP and TCP. IP versions 4 and 6. UDP and TCP.