1. 12 Dec, 2011 1 commit
  2. 30 Nov, 2011 1 commit
  3. 28 Nov, 2011 1 commit
  4. 04 Nov, 2011 1 commit
  5. 13 Oct, 2011 3 commits
  6. 08 Sep, 2011 3 commits
  7. 30 Aug, 2011 1 commit
  8. 15 Aug, 2011 1 commit
  9. 07 Jul, 2011 1 commit
  10. 23 Jun, 2011 1 commit
  11. 24 May, 2011 2 commits
  12. 20 May, 2011 1 commit
  13. 20 Apr, 2011 1 commit
  14. 19 Apr, 2011 1 commit
  15. 31 Mar, 2011 5 commits
  16. 24 Mar, 2011 7 commits
  17. 08 Mar, 2011 2 commits
  18. 10 Feb, 2011 4 commits
  19. 31 Jan, 2011 1 commit
  20. 28 Jan, 2011 2 commits
    • Sjoerd Simons's avatar
      Remove some dead code · 5cc9cddf
      Sjoerd Simons authored
      5cc9cddf
    • Sjoerd Simons's avatar
      Reset the connectivity check timer when we get triggered checks · 9953608d
      Sjoerd Simons authored
      Current nice has a race where if the remote site only punches their side
      of the NAT after we have done the maximum number of retransmissions,
      we'll never send a new connectivity check (which would be successful).
      Causing the connectiviy check to fail eventually, even though it
      shouldn't have.
      
      By resetting the conncheck timer nice will always send new stun packets
      for connectivity checks afterwards, but also sent connectivity checks
      quicker so we can establish the connection quicker.
      9953608d