Cause: The egressIPTracker had methods that lock eit.mutex and that call evm functions that lock evm.mutex. The problem with this was that evm.mutex had to write to the evm.updates channel which isn't buffered and becomes blocked until eit.setNodeOffline was run, and this function also locked eit.mutex. Consequence: When there was a vas amount of egressIPs there was a deadlock Fix: Removed the deadlock by making the updates channel buffered so that it's a mere notification system which doesn't contain the actual data. Result: There is no deadlock