Skip to content

conncheck: do not create a pair from peer-reflexive local candidate

The usual case when forming the initial conncheck list from local and remote candidates is to discard server-reflexive local candidates, since the agent can not send requests directly from these candidates. But it also may happen, when the remote candidates are received late after the beginning of the conncheck, that we also have discovered peer-reflexive local candidates, that must be discarded as well. See RFC 8445, section 6.1.2.4 "Pruning the Pairs".

This bug has been triggered with a same test scenario than with !93 (merged)

Merge request reports