This repository has been archived by the owner on Jun 8, 2024. It is now read-only.
forked from alanmcgovern/Mono.Nat
-
Notifications
You must be signed in to change notification settings - Fork 99
Known Issues
Matt edited this page Jun 19, 2020
·
2 revisions
NAT devices' mapping table is a scarce resource and that means we cannot have an infinite number of mappings. These tables have a limit, some have 10, 16, 32 and even more entries and then, the question is: how should the NAT response once the its limit is reached? Well, that's the problem, the specs do not say anything about this so, some NATs just accept the addNewPortMapping request and response with status 200 OK and for that reason the clients, like Open.NAT, have no cheap way to know about that fact.
Workaround:
Clients can verify that the new requested port mappings have been append to the mapping table by requesting the full list of port mappings and check those ports are listed.