1. 16 Jul, 2019 2 commits
  2. 07 Feb, 2019 1 commit
  3. 05 Feb, 2019 2 commits
  4. 02 Feb, 2019 5 commits
  5. 01 Feb, 2019 2 commits
  6. 08 Dec, 2018 1 commit
  7. 27 May, 2018 2 commits
  8. 23 May, 2018 2 commits
  9. 18 May, 2018 1 commit
  10. 19 Apr, 2018 1 commit
  11. 12 Mar, 2018 1 commit
    • Sergey Kachanovskiy's avatar
      Partial fix for issue 2963, removed invalid casts from fd_t to int (#2984) · 9c748f1b
      Sergey Kachanovskiy authored
      * Fixes issue 2963, ref stream_engine.cpp:981
      
      * Fixes issue 2963, ref socks_connecter.cpp:158
      
      * Fixes issue 2963, ref tcp_listener.cpp:144
      
      * Fixes issue 2963, ref tcp_connecter.cpp:423
      
      * Fixes issue 2963, ref socks_connecter.cpp:436
      
      * Fixes issue 2963, ref tcp_listener.cpp:179
      
      * Fixes issue 2963, ref tcp_listener.cpp:268
      
      * Fixes issue 2963, ref tcp_connecter.cpp:160
      9c748f1b
  12. 10 Mar, 2018 1 commit
    • Manuel Segura's avatar
      Pull request to merge porting to WindRiver VxWorks 6.x (#2966) · 4726f726
      Manuel Segura authored
      * Problem: Still need to port over more files to VxWorks 6.x
      
      Solution: Port more files to VxWorks 6.x
      
      * Problem: Need to port over remaining files to VxWorks 6.x. Also remove POSIX thread dependency for VxWorks (because of priority inversion problem in POSIX mutexes with VxWorks 6.x processes)
      
      Solution: Port over remaining files to VxWorks 6.x. Also removed POSIX thread dependency for VxWorks
      
      * Problem: Needed to modify TCP, UDP, TIPC classes with #ifdefs to be compatible with VxWorks 6.x.
      
      Solution:  Modify TCP, UDP, TIPC classes with #ifdefs to be compatible with VxWorks 6.x
      4726f726
  13. 09 Feb, 2018 1 commit
  14. 08 Feb, 2018 1 commit
  15. 02 Feb, 2018 1 commit
  16. 18 Nov, 2017 1 commit
  17. 31 Jul, 2017 1 commit
    • Brian Russell's avatar
      Add socket option BINDTODEVICE · b963542e
      Brian Russell authored
      Linux now supports Virtual Routing and Forwarding (VRF) as per:
      
      https://www.kernel.org/doc/Documentation/networking/vrf.txt
      
      In order for an application to bind or connect to a socket with an
      address in a VRF, they need to first bind the socket to the VRF device:
      
          setsockopt(sd, SOL_SOCKET, SO_BINDTODEVICE, dev, strlen(dev)+1);
      
      Note "dev" is the VRF device, eg. VRF "blue", rather than an interface
      enslaved to the VRF.
      
      Add a new socket option, ZMQ_BINDTODEVICE, to bind a socket to a device.
      In general, if a socket is bound to a device, eg. an interface, only
      packets received from that particular device are processed by the socket.
      
      If device is a VRF device, then subsequent binds/connects to that socket
      use addresses in the VRF routing table.
      b963542e
  18. 04 Apr, 2017 2 commits
    • Jake Cobb's avatar
      Prevent DOS by asserts in TCP tuning (#2492) · 5d5263ed
      Jake Cobb authored
      * Prevent DOS by asserts in TCP tuning
      
      -Propagates socket option errors from the
      tuning functions to the callers.
      -Asserts a subset of error conditions during tuning,
      excluding external network causes.
      -Checks tuning results in 3 call sites and treats
      them like failures to connect, accept, etc.
      
      * Fix variable name
      
      * Remove lambda requiring C++11
      5d5263ed
    • bbdb68's avatar
      Problem: no windows UWP support · 1d58a009
      bbdb68 authored
      * add define for windows/UWP
      
      * prevent issue with COM references
      
      * gettickcount not available on uwp
      
      * add compiler definitions
      
      * add convenitnece cmake file
      
      * brute force uwp compilation
      
      * fix compiler version
      
      * cosmetics
      1d58a009
  19. 04 Jan, 2017 1 commit
    • Luca Boccassi's avatar
      Problem: peer can close connection before SO_NOSIGPIPE is set · 31a3a068
      Luca Boccassi authored
      Solution: setsockopt returns EINVAL if the connection was closed by
      the peer after the accept returned a valid socket. This is a valid
      network error and should not cause an assert.
      To handle this we have to extract the setsockopt from the stream
      engine, as there's no clean way to return an error from the
      constructor. Instead, try to set this option before creating the
      engine in the callers, and return immediately as if the accept
      had failed to avoid churn. Do the same for the connect calls by
      setting the option in open_socket, so that the option for that
      case is set even before connecting, so there's no possible race
      condition.
      Since this has to be done in 4 places (tcp/ipc listener, socks
      connecter and open_socket) add an utility function in ip.cpp.
      Fixes #1442
      31a3a068
  20. 17 Sep, 2016 1 commit
  21. 30 Jul, 2016 1 commit
  22. 01 Jun, 2016 1 commit
  23. 14 May, 2016 1 commit
  24. 08 May, 2016 1 commit
  25. 04 May, 2016 1 commit
  26. 01 May, 2016 1 commit
  27. 07 Apr, 2016 2 commits
  28. 21 Feb, 2016 2 commits