1. 24 Apr, 2015 2 commits
  2. 23 Apr, 2015 6 commits
  3. 22 Apr, 2015 1 commit
  4. 20 Apr, 2015 11 commits
  5. 14 Apr, 2015 3 commits
  6. 28 Mar, 2015 2 commits
  7. 27 Mar, 2015 3 commits
  8. 10 Mar, 2015 3 commits
  9. 11 Feb, 2015 5 commits
  10. 30 Jan, 2015 1 commit
    • Youness Alaoui's avatar
      Remove duplicate ips from nice_interfaces · 925649e8
      Youness Alaoui authored
      OpenVPN creates a tun interface having the same IP assigned twice like:
      
      9: tun0: <POINTOPOINT,MULTICAST,NOARP,UP,LOWER_UP> mtu 1500 qdisc ...100
          link/none
          inet 10.222.111.10 peer 10.222.111.9/32 brd 10.222.111.10 scope global tun0
             valid_lft forever preferred_lft forever
          inet 10.222.111.10/32 brd 10.222.111.10 scope global tun0
             valid_lft forever preferred_lft forever
      
      This interface would generate two identical host candidates with the same value
      of foundation.
      925649e8
  11. 29 Jan, 2015 3 commits
    • Olivier Crête's avatar
      Version 0.1.10.1 · b7a36c0c
      Olivier Crête authored
      b7a36c0c
    • Olivier Crête's avatar
      Version 0.1.10 · 2a9ce549
      Olivier Crête authored
      2a9ce549
    • Jakub Adam's avatar
      nicesink: unblock pending write on component change · 21dd3d15
      Jakub Adam authored
      When a nicesink switches to a different component, we should unblock any
      pending write waiting in gst_nice_sink_render() for writable_cond being
      signalled because if the new transport already is writable, we'll never
      get notified about the condition and thus nicesink will wait forever.
      
      That way, either the pending data are immediately sent or the nicesink
      blocks again until the transport becomes writable.
      21dd3d15