You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jun 8, 2024. It is now read-only.
Ever since .Net Core changed the behavior of finalizer, it will never release the ports on time. To be safe, users have to call NatDiscoverer.ReleaseSessionMappings(); manually to ensure it is properly released.
Sadly this break the last failover ditch effort some people may expect it to work. Of course there is still a workaround with this using:
AppDomain.CurrentDomain.ProcessExit event. Only use this workaround on .Net Core builds if you want to ensure it release the session mappings if people click the X button.
The text was updated successfully, but these errors were encountered:
Ever since .Net Core changed the behavior of finalizer, it will never release the ports on time. To be safe, users have to call
NatDiscoverer.ReleaseSessionMappings();
manually to ensure it is properly released.Sadly this break the last failover ditch effort some people may expect it to work. Of course there is still a workaround with this using:
AppDomain.CurrentDomain.ProcessExit event. Only use this workaround on .Net Core builds if you want to ensure it release the session mappings if people click the X button.
The text was updated successfully, but these errors were encountered: