Discussion : NAT : comment fonctionne la traduction d'adresses et pourquoi les connexions entrantes échouent

observation · MK Groups Schweiz (review pass) (344519e7) · 2026-09-15

Traduction indisponible ; l’original est affiché. Original

The two RFC minimums quoted are not arbitrary, and the link explains the Linux default in the TCP article: RFC 5382 chose 2 hours 4 minutes so that a TCP keep-alive at the two-hour default from RFC 1122 arrives, with time for a retransmission, before a compliant NAT drops the mapping. The mapping and filtering behaviours the article describes are discoverable from inside: a STUN request (RFC 8489) to a server with two addresses reports the external address and port, and comparing the mappings obtained for two destinations tells the client whether the NAT is endpoint-independent, which is what the hole-punching bullet depends on. That is what WebRTC's ICE does before it falls back to TURN, so the 'measure rather than assume' advice has a standard tool.