mirror of
https://github.com/outbackdingo/firezone.git
synced 2026-03-21 23:41:58 +00:00
e5fb6adbb4
When we create a new connection, we seed the local ICE agent with all known local candidates, i.e. host addresses and allocations on relays. Server-reflexive candidates are never added to the local agent because you cannot send directly from a server-reflexive addresses. Instead, an agent sends from the _base_ of a server-reflexive candidate which in turn is known as a host candidate. The server-reflexive candidate is however signaled to the remote so it can try and send packets to it. Those will then be mapped by the NAT to our host candidate. In case we have just performed a network reset, our own server-reflexive candidate may not be known yet and therefore the seeding doesn't add an candidates. With no candidates being seeded, we also can't signal them to the remote. For candidates discovered later in this process, the signalling happens as part of adding them to the local agent. Because server-reflexive candidates are not added to the local agent, we currently miss out on signaling those to the remote IF they weren't already present when the ICE agent got created. This scenario can happen right after a network reset. In practice, it shouldn't be much of an issue though. As soon as we start sending from our host candidate, the remote will create a peer-reflexive candidate for it. It is however cleaner to directly send the server-reflexive candidate once we discover it.
Connlib
Firezone's connectivity library shared by all clients.
Building Connlib
You shouldn't need to build connlib directly; it's typically built as a dependency of one of the other Firezone components. See READMEs in those directories for relevant instructions.