1. 08 May, 2019 1 commit
  2. 05 Apr, 2019 2 commits
  3. 15 Feb, 2019 1 commit
  4. 11 Feb, 2019 1 commit
  5. 23 Jan, 2019 1 commit
  6. 22 Jan, 2019 1 commit
  7. 14 Jan, 2019 1 commit
  8. 02 Jan, 2019 1 commit
  9. 27 Dec, 2018 2 commits
  10. 14 Dec, 2018 4 commits
  11. 21 Oct, 2018 2 commits
  12. 18 Jun, 2018 1 commit
  13. 06 Jun, 2018 1 commit
  14. 04 May, 2018 2 commits
  15. 28 Nov, 2017 1 commit
    • Youness Alaoui's avatar
      turn: Add support for ALTERNATE_SERVER in OC2007 Compatibility · 59fcf95d
      Youness Alaoui authored
      The MS Office TURN servers will always return the MS_ALTERNATE_SERVER in
      allocation responses, and if they are not handled, we end up using the
      main turn server to send allocation requests that then get sent to the
      alternate server which will return the XOR_MAPPED_ADDRESS containing
      the IP address of the turn server that proxied the message instead of
      our own actual external IP.
      59fcf95d
  16. 12 Sep, 2017 1 commit
  17. 21 Jun, 2017 1 commit
  18. 12 Jun, 2017 1 commit
    • Fabrice Bellet's avatar
      stun timer: make properties for stun timer tunables · 8bb210c5
      Fabrice Bellet authored
      Three STUN binding request properties should be customisable. RFC 5245
      describes the retransmission timer of the STUN transaction 'RTO', and
      RFC 5389 describes the number of retransmissions to send until a
      response is received 'Rc'. The third property is the 'RTO' when
      a reliable connection is used.
      
      RFC 5389 introduces a supplementary property 'Rm' as a multiplier used
      to compute the final timeout RTO * Rm. However, this property is not
      added in libnice, because this would require breaking the public API for
      STUN. Currently, our STUN implementation hardcodes a division by two for
      this final timeout.
      
      Differential Revision: https://phabricator.freedesktop.org/D1109
      8bb210c5
  19. 12 Apr, 2017 1 commit
    • Fabrice Bellet's avatar
      stun timer: fix timeout of the last retransmission · f6f704c5
      Fabrice Bellet authored
      According to RFC 5389, section 7.2.1, a special timeout is applied to
      the last retransmission (Rm * RTO), with Rm default value of 16, instead
      of (64 * RTO), 2^6 when the number of transmissions Rc is set to 7.
      
      As spotted by Olivier Crete, stun_timer_* is a public API, that cannot
      be changed, and the initial delay (RTO) is not preserved in the
      stun_timer_s struct. So we use a hack that implicitely guess Rm from the
      number of transmissions Rc, by generalizing the default value of the
      spec for Rm and Rc to other values of Rc passed in stun_timer_start(
      
      According to the spec, with the default value of Rc=7, the last delay
      should be (64 * RTO), and it is instead (16 * RTO). So the last delay
      can be computed by dividing the penultimate delay by two, instead of
      multiplying it by two.
      
      Differential Revision: https://phabricator.freedesktop.org/D1108
      f6f704c5
  20. 04 Apr, 2017 1 commit
  21. 03 Apr, 2017 5 commits
  22. 31 Mar, 2017 5 commits
  23. 28 Mar, 2017 1 commit
  24. 26 Oct, 2016 2 commits
    • Jakub Adam's avatar
      ms-ice: limit legacy connchecks as per [MS-ICE2] 3.1.4.8.2 · 2803a0b4
      Jakub Adam authored
      Client should stop sending connectivity checks with legacy FINGERPRINT
      when it receives a conncheck message containing IMPLEMENTATION-VERSION
      attribute.
      
      Differential Revision: https://phabricator.freedesktop.org/D1139
      2803a0b4
    • Jakub Adam's avatar
      ms-ice: legacy FINGERPRINT mode · 7e5ab23c
      Jakub Adam authored
      In order to preserve compatibility with clients which use custom CRC
      lookup table from [MS-ICE2], whenever a connectivity check request or
      reply is sent, an additional message is sent along. These two messages
      differ only in FINGERPRINT attribute - one uses regular CRC lookup table
      for calculation, the other uses the modified table.
      
      When a message is received and FINGERPRINT doesn't pass validation using
      regular CRC table, the receiver also tries to verify using the modified
      table.
      
      [MS-ICE2] 3.1.4.8.2 describes this procedure.
      
      The commit fixes compatibility with older MSOC and Lync clients.
      
      Differential Revision: https://phabricator.freedesktop.org/D1138
      7e5ab23c