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
Describe the bug
The pfconnector server uses a cache for the currently active dynamic reverses. When a reverse is closed due to inactivity (or any other reason), the cache entry stays. There is a check that tries to bind the port in the cache and if it fails to bind that port, it believes the reverse is still alive. On occasion, that inactively closed port can be reused by another process and the pfconnector will think the tunnel is still active while it isn't (the existing bind is for another process)
The solution is to cycle through all the active dynamic reverses when one closes to purge it from the cache
The text was updated successfully, but these errors were encountered:
Describe the bug
The pfconnector server uses a cache for the currently active dynamic reverses. When a reverse is closed due to inactivity (or any other reason), the cache entry stays. There is a check that tries to bind the port in the cache and if it fails to bind that port, it believes the reverse is still alive. On occasion, that inactively closed port can be reused by another process and the pfconnector will think the tunnel is still active while it isn't (the existing bind is for another process)
The solution is to cycle through all the active dynamic reverses when one closes to purge it from the cache
The text was updated successfully, but these errors were encountered: