…. TCP stacks commonly use a randomized source port to provide this protection [ RFC6056 ]; UDP applications should follow the same technique. Middleboxes and end systems often make assumptions about the system ports or user ports; hence, it is recommended to use randomized ports …
…10.17487/RFC5928 , August 2010 , < https://www.rfc-editor.org/info/rfc5928 > . [RFC6056] Larsen, M. and F. Gont , "Recommendations for Transport-Protocol Port Randomization" , BCP 156 , RFC 6056 , DOI 10.17487/RFC6056 , January 2011 , < https://www.rfc-editor.org/info/rfc6056 > .…
…, 4 and 5 with port numbers from the range 49152-65535 as documented in [NetBSD-RFC6056]. Notes: The project implemented the RFC 6056 algorithms last year to obfuscate the ephemeral port numbers. [NetBSD-RFC6056] reference is: The NetBSD Project, "NetBSD Miscellaneous Information…
…, 4 and 5 with port numbers from the range 49152-65535 as documented in [NetBSD-RFC6056]. Notes: The project implemented the RFC 6056 algorithms last year to obfuscate the ephemeral port numbers. [NetBSD-RFC6056] reference is: The NetBSD Project, "NetBSD Miscellaneous Information…