1. 17 Sep, 2020 1 commit
    • Johan Sternerup's avatar
      agent: Enable both UDP and TCP to the same TURN server · 303f0179
      Johan Sternerup authored
      Previously if we enabled both UDP and TCP to the same TURN server, the
      TCP connection would not work. What happened was that when traffic was
      targeted at the TCP connection we would fail to route the traffic to
      the right socket due to a too early jump out of the loop searching for
      the socket. The search would stop when finding a TURN server matching
      the address of the incoming message source. Thus, a UDP TURN server
      with the same address as the TCP TURN server would effectively mean
      that traffic got routed to a different stun agent that would complain
      about receiving responses without matching requests.
      303f0179
  2. 20 Aug, 2020 1 commit
  3. 18 Aug, 2020 2 commits
  4. 13 Aug, 2020 1 commit
  5. 10 Aug, 2020 2 commits
  6. 04 Aug, 2020 4 commits
  7. 22 Jul, 2020 3 commits
  8. 09 Jul, 2020 5 commits
  9. 26 Jun, 2020 1 commit
  10. 25 Jun, 2020 1 commit
    • Nirbheek Chauhan's avatar
      stund: Use lowercase winsock2.h · aa055b36
      Nirbheek Chauhan authored
      Windows ships with `WinSock2.h` but mingw ships with `winsock2.h`.
      This is fine on Windows because files are case-insensitive, but on
      Linux it causes the compiler to not find the header.
      
      All other #includes are lowercase, so just use that.
      aa055b36
  11. 15 Jun, 2020 2 commits
  12. 22 May, 2020 16 commits
  13. 19 May, 2020 1 commit
    • Fabrice Bellet's avatar
      conncheck: do not always remove pair in triggered check list · 4c53dc2f
      Fabrice Bellet authored
      This patch reenables an interesting side effect that existed before
      commit 263c0903, when the state of a pair state in the triggered check
      list was changed to in-progress. Such "triggered" pairs with this state
      were selectively pruned from the conncheck list according to their
      priority in priv_prune_pending_checks(), meaning that pairs with a high
      priority were conserved, and quickly rechecked.
      
      Retrospectively, I suspect that this side effect was the initial
      motivation for changing the state of a "triggered" pair.
      
      Commit 263c0903 disabled that behaviour, for the sake of clarity, but it
      seems important to restore it, because these "triggered" pairs are often
      retriggered for a good reason, and frequently lead to a nominated pair.
      And loosing the opportunity to nominate a pair may be critical in
      controlled role when the peer agent is in aggressive nomination mode.
      4c53dc2f