1. 27 Dec, 2018 1 commit
  2. 18 Dec, 2018 2 commits
  3. 14 Dec, 2018 4 commits
  4. 31 Oct, 2018 1 commit
    • Jakub Adam's avatar
      udp-turn: handle multiple RFC4571 frames received in a TCP-TURN message · d79d1179
      Jakub Adam authored
      There might be multiple RFC4571-framed messages (or fragments thereof)
      within a single TCP-TURN message. Make sure each NiceInputMessage
      passed by the user into socket_recv_messages() gets exactly one RFC4571
      frame, or remains empty if there aren't any messages to receive.
      
      We should keep any data that doesn't fit into the user buffers for
      the next time socket_recv_messages() gets called with the socket.
      d79d1179
  5. 21 Oct, 2018 1 commit
  6. 06 Jun, 2018 1 commit
  7. 23 Mar, 2018 1 commit
  8. 28 Nov, 2017 1 commit
  9. 27 Nov, 2017 2 commits
  10. 12 Sep, 2017 2 commits
  11. 21 Jun, 2017 1 commit
  12. 12 Jun, 2017 1 commit
  13. 11 Apr, 2017 2 commits
  14. 05 Apr, 2017 1 commit
  15. 03 Apr, 2017 1 commit
  16. 23 Jun, 2016 1 commit
  17. 20 Jun, 2016 3 commits
  18. 03 Jun, 2016 4 commits
    • Olivier Crête's avatar
      pseudotcp: Set min RTO to 1 second · 1f532aeb
      Olivier Crête authored
      This is recommended by RFC 6298
      1f532aeb
    • Philip Withnall's avatar
      pseudotcp: Correct behaviour of buffer size methods when part-closed · 11d4bb97
      Philip Withnall authored and Olivier Crête's avatar Olivier Crête committed
      Correct the behaviour of pseudo_tcp_socket_get_available_bytes() and
      pseudo_tcp_get_available_send_space() when the socket is not in
      TCP_ESTABLISHED state. It’s still permissible to send and receive up
      until the local side calls pseudo_tcp_socket_close(), which means we
      may be in state TCP_ESTABLISHED *or TCP_CLOSE_WAIT*.
      11d4bb97
    • Philip Withnall's avatar
      pseudotcp: Fix pseudo_tcp_socket_recv() in state TCP_CLOSE_WAIT · a72a93e5
      Philip Withnall authored and Olivier Crête's avatar Olivier Crête committed
      Previously, pseudo_tcp_socket_recv() would start returning 0 (EOS) as
      soon as a FIN segment was received from the peer, even if there was
      unread data already in the receive buffer.
      
      Instead, the unread data should all be accessible before
      pseudo_tcp_socket_recv() starts returning 0.
      a72a93e5
    • Philip Withnall's avatar
      pseudotcp: Fix retransmission of segments before handling a FIN · 02699917
      Philip Withnall authored and Olivier Crête's avatar Olivier Crête committed
      Previously, if peer A transmitted one or more data segments (1),
      followed by a FIN segment (2) to peer B, and segments 1 were
      dropped, peer B would not request retransmission of them and would
      instead continue with the FIN handshake. This effectively meant
      segments 1 were lost without peer B realising.
      
      Fix this by only handling the FIN segment once its sequence number is
      acknowledged in the receive window.
      02699917
  19. 02 Jun, 2016 1 commit
  20. 01 Jun, 2016 1 commit
    • Jakub Adam's avatar
      test-icetcp: don't be sensitive to the signal order · 1a234765
      Jakub Adam authored and Olivier Crête's avatar Olivier Crête committed
      "new-selected-pair" may be emitted after "component-state-changed"
      to READY, by which time the main loop might have gotten quit in
      cb_component_state_changed(). Consequently, cb_new_selected_pair() could
      miss to register the selected pair, ultimately leading to an assertion
      failure in main().
      
      We should wait for both selected pair and state change events to occur
      before stopping the main loop.
      
      Differential Revision: https://phabricator.freedesktop.org/D1044
      1a234765
  21. 04 Apr, 2016 2 commits
  22. 01 Mar, 2016 2 commits
  23. 18 Oct, 2015 1 commit
  24. 01 Oct, 2015 3 commits