Skip to content

    ← All posts

    Source ports exhausted: EADDRNOTAVAIL, TIME_WAIT and NAT Gateway

    · updated on

    One hundred connections go through, the next one fails with EADDRNOTAVAIL. Why TIME_WAIT holds ports for 60 s, what keep-alive and tcp_tw_reuse change, and the same limit on the AWS NAT Gateway (figures from the AWS docs, nothing was created).

    Spotted an error, something to add?

    Tell me: I read every message and correct the article when needed.

    Your name only appears below the article with this consent, and only if the remark is used. Your address is never published.