There is another tool that seems quite complete : punch-check.The only other tool I know of is Xbox networking app. Run the network tests, it'll show you the correct results.
https://github.com/delthas/punch-check
It gives hairpinning support and port assignment informations, something that NatType tester do not gives.RFC 4787 defines several NAT properties and which are needed for hole-punching support. Those properties which are checked by this tool are:
port mapping: either endpoint-independent, address-dependent, or address and port-dependent
filtering: either endpoint-independent, address-dependent, or address and port-dependent
hairpinning: supported or unsupported
port assignment: may be contiguous, preserving, and parity-preserving
The RFC 4787 reading probably gives a clear view of the quite complex UDP NAT subject.
https://datatracker.ietf.org/doc/html/rfc4787
Definitely those older terms are not precise enough :
And some other interesting readings about the subject :STUN [RFC3489] used the terms "Full Cone", "Restricted Cone", "Port
Restricted Cone", and "Symmetric" to refer to different variations of
NATs applicable to UDP only. Unfortunately, this terminology has
been the source of much confusion, as it has proven inadequate at
describing real-life NAT behavior. This specification therefore
refers to specific individual NAT behaviors instead of using the
Cone/Symmetric terminology.
https://bford.info/pub/net/p2pnat/
https://datatracker.ietf.org/doc/html/d ... results-01
Statistics: Posted by FIPTech — Sat Feb 24, 2024 10:43 pm