Skip to content

agent: stay in aggressive mode after conncheck has started

When remote tcp candidates are received late after the conncheck has started, RFC 6554 suggests that we switch the nomination mode back from aggressive to regular. The problem is that some stun requests may already be inflight with the use-candidate stun flag set, and reverting to regular mode in that case is too late, because these inflight requests may nominate a pair on the remote agent, and not on the local agent. We prefer to just ignore remote tcp candidates that are received after the component state has reached state CONNECTING.

Merge request reports