Hacker Newsnew | past | comments | ask | show | jobs | submit | clearint's commentslogin

This article should clarify at the start whether TCP or UDP is under consideration. NAT idle timeouts for both are typically very different. RFC 5382 [0] specifies no less than 2 hours and 4 minutes for TCP. RFC 4787 [1] specifies no less than 2 minutes for UDP. Towards the end of the article it becomes clear that it's UDP.

The example diagrams also incorrectly show port numbers exceeding 65535. The port fields in TCP and UDP headers are 16 bits [2].

[0]: https://www.rfc-editor.org/rfc/rfc5382 [1]: https://www.rfc-editor.org/rfc/rfc4787 [2]: https://textbook.cs161.org/network/transport.html


That's interesting. Do NATs in the wild tend to be spec-compliant with their timeouts?


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: