1. 12 Jun, 2018 1 commit
  2. 30 May, 2018 1 commit
  3. 27 May, 2018 1 commit
  4. 26 May, 2018 1 commit
  5. 23 May, 2018 1 commit
  6. 22 May, 2018 1 commit
  7. 18 May, 2018 1 commit
  8. 16 May, 2018 1 commit
  9. 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
  10. 10 Mar, 2018 2 commits
    • Luca Boccassi's avatar
      Problem: formatting issues in the CI · 8d544ef1
      Luca Boccassi authored
      Solution: commit clang-format-diff
      8d544ef1
    • 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
  11. 05 Mar, 2018 1 commit
  12. 09 Feb, 2018 1 commit
  13. 08 Feb, 2018 2 commits
  14. 02 Feb, 2018 1 commit
  15. 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
  16. 04 Apr, 2017 1 commit
    • 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
  17. 23 Oct, 2016 1 commit
  18. 01 Jun, 2016 1 commit
  19. 14 May, 2016 1 commit
  20. 08 May, 2016 1 commit
  21. 04 May, 2016 1 commit
  22. 01 May, 2016 1 commit
  23. 07 Apr, 2016 1 commit
  24. 21 Feb, 2016 3 commits
  25. 18 Feb, 2016 1 commit
  26. 09 Feb, 2016 1 commit
  27. 28 Jan, 2016 1 commit
  28. 02 Nov, 2015 1 commit
    • William Swanson's avatar
      Do not crash on unusual connection-failure cases · b2010432
      William Swanson authored
      Only assert on errors we know are our fault,
      instead of trying to whitelist every possible network-related failure.
      This makes ZeroMQ more portable to other platforms
      where the possible errors are different.
      
      In particular, the previous code would often die under iOS.
      b2010432
  29. 17 Sep, 2015 1 commit
  30. 06 Sep, 2015 1 commit
  31. 21 Aug, 2015 1 commit
  32. 16 Aug, 2015 1 commit
  33. 14 Aug, 2015 2 commits
  34. 06 Aug, 2015 1 commit
  35. 04 Aug, 2015 1 commit