1. 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
  2. 24 Apr, 2017 1 commit
  3. 26 Dec, 2016 1 commit
  4. 21 Sep, 2016 1 commit
  5. 09 Feb, 2016 4 commits
  6. 08 Feb, 2016 1 commit
  7. 04 Feb, 2016 1 commit
  8. 01 Feb, 2016 3 commits
  9. 08 Dec, 2015 1 commit
    • Ilya Kulakov's avatar
      Add the VMCI transport. · 68b13fbd
      Ilya Kulakov authored
      VMCI transport allows fast communication between the Host
      and a virtual machine, between virtual machines on the same host,
      and within a virtual machine (like IPC).
      
      It requires VMware to be installed on the host and Guest Additions
      to be installed on a guest.
      68b13fbd
  10. 23 Nov, 2015 1 commit
  11. 13 Nov, 2015 2 commits
  12. 08 Nov, 2015 1 commit
  13. 08 Oct, 2015 1 commit
  14. 13 Sep, 2015 1 commit
  15. 11 Sep, 2015 1 commit
  16. 06 Aug, 2015 1 commit
  17. 04 Aug, 2015 2 commits
  18. 08 Jul, 2015 2 commits
  19. 26 Jan, 2015 1 commit
    • Julien Ruffin's avatar
      Added socket option ZMQ_INVERT_MATCHING. · cf2238f8
      Julien Ruffin authored
      ZMQ_INVERT_MATCHING reverses the PUB/SUB prefix matching. The subscription
      list becomes a rejection list. The PUB socket sends messages to all
      connected (X)SUB sockets that do not have any matching subscription.
      
      Whenever the option is used on a PUB/XPUB socket, any connecting SUB
      sockets must also set it or they will reject everything the publisher
      sends them. XSUB sockets are unaffected because they do not filter out
      incoming messages.
      cf2238f8
  20. 09 Jan, 2015 1 commit
  21. 08 Nov, 2014 1 commit
  22. 12 Aug, 2014 1 commit
  23. 20 Jun, 2014 1 commit
  24. 12 May, 2014 1 commit
  25. 09 May, 2014 1 commit
  26. 01 Jan, 2014 2 commits
    • Pieter Hintjens's avatar
      Removed ZMQ_ZAP_IPC_CREDS option · 5bf96f64
      Pieter Hintjens authored
      - This seems redundant; is there a use case for NOT providing
        the IPC credentials to the ZAP authenticator?
      
      - More, why is IPC authentication done via libzmq instead of ZAP?
        Is it because we're missing the transport type on the ZAP request?
      5bf96f64
    • Pieter Hintjens's avatar
      Reordered socket options · adf5b45d
      Pieter Hintjens authored
      - put into alphabetical order
      - there was no consistency in previous ordering
      adf5b45d
  27. 06 Dec, 2013 1 commit
    • Brandon Carpenter's avatar
      Add support for extending ZAP request address with IPC peer credentials. · a018ef5e
      Brandon Carpenter authored
      Another take on LIBZMQ-568 to allow filtering IPC connections, this time
      using ZAP.  This change is backward compatible.  If the
      ZMQ_ZAP_IPC_CREDS option is set, the user, group, and process IDs of the
      peer process are appended to the address (separated by colons) of a ZAP
      request; otherwise, nothing changes.  See LIBZMQ-568 and zmq_setsockopt
      documentation for more information.
      a018ef5e
  28. 25 Nov, 2013 1 commit
  29. 09 Oct, 2013 1 commit
  30. 20 Sep, 2013 1 commit
    • Pieter Hintjens's avatar
      Renamed new socket options to be clearer · 5e609be3
      Pieter Hintjens authored
      * ZMQ_REQ_STRICT was negative option (default 1) which goes against
        the standard, where defaults are zero. I renamed this to
        ZMQ_REQ_RELAXED.
      
      * ZMQ_REQ_REQUEST_IDS felt clumsy and describes the technical solution
        rather than the problem/requirement. I changed to ZMQ_REQ_CORRELATE
        which seems more explicit.
      5e609be3
  31. 12 Sep, 2013 1 commit
    • Pieter Hintjens's avatar
      Fixed overwrite in zmq_getsockopt · 345bf146
      Pieter Hintjens authored
      On ZMQ_CURVE_xxxKEY fetches, would return 41 bytes into caller's 40-byte
      buffer. Now these fetches only return 41 bytes if the caller explicitly
      provides a 41-byte buffer (i.e. the option size is 41).
      345bf146