Avoid lots and lots of announced addresses in the presence of symmetric NAT #4519
Labels
enhancement
New features or improvements of some kind, as opposed to a problem (bug)
frozen-due-to-age
Issues closed and untouched for a long time, together with being locked for discussion
Milestone
When behind symmetric NAT we will get a new port mapping for every STUN lookup, which is (worst case) every 24 seconds. Worst case this means we accumulate up to 150 useless KCP addresses (one hour's worth) on the discovery server.
We should probably just not announce any KCP addresses to the global discovery system when we are behind an unfriendly NAT type.
Relates to #4459
The text was updated successfully, but these errors were encountered: