2016-02-12 15:46:55 +01:00
|
|
|
/*
|
|
|
|
Copyright (c) 2007-2016 Contributors as noted in the AUTHORS file
|
|
|
|
|
|
|
|
This file is part of libzmq, the ZeroMQ core engine in C++.
|
|
|
|
|
|
|
|
libzmq is free software; you can redistribute it and/or modify it under
|
|
|
|
the terms of the GNU Lesser General Public License (LGPL) as published
|
|
|
|
by the Free Software Foundation; either version 3 of the License, or
|
|
|
|
(at your option) any later version.
|
|
|
|
|
|
|
|
As a special exception, the Contributors give you permission to link
|
|
|
|
this library with independent modules to produce an executable,
|
|
|
|
regardless of the license terms of these independent modules, and to
|
|
|
|
copy and distribute the resulting executable under terms of your choice,
|
|
|
|
provided that you also meet, for each linked independent module, the
|
|
|
|
terms and conditions of the license of that module. An independent
|
|
|
|
module is a module which is not derived from or based on this library.
|
|
|
|
If you modify this library, you must extend this exception to your
|
|
|
|
version of the library.
|
|
|
|
|
|
|
|
libzmq is distributed in the hope that it will be useful, but WITHOUT
|
|
|
|
ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or
|
|
|
|
FITNESS FOR A PARTICULAR PURPOSE. See the GNU Lesser General Public
|
|
|
|
License for more details.
|
|
|
|
|
|
|
|
You should have received a copy of the GNU Lesser General Public License
|
|
|
|
along with this program. If not, see <http://www.gnu.org/licenses/>.
|
|
|
|
*/
|
|
|
|
|
2015-11-13 10:41:00 +01:00
|
|
|
#include "testutil.hpp"
|
|
|
|
|
2016-02-09 10:51:51 +01:00
|
|
|
void test_setsockopt_tcp_recv_buffer (void)
|
2015-11-13 10:41:00 +01:00
|
|
|
{
|
|
|
|
int rc;
|
2016-02-09 10:51:51 +01:00
|
|
|
void *ctx = zmq_ctx_new ();
|
|
|
|
void *socket = zmq_socket (ctx, ZMQ_PUSH);
|
2015-11-13 10:41:00 +01:00
|
|
|
|
|
|
|
int val = 0;
|
2016-02-09 10:51:51 +01:00
|
|
|
size_t placeholder = sizeof (val);
|
2015-11-13 10:41:00 +01:00
|
|
|
|
2016-02-09 10:51:51 +01:00
|
|
|
rc = zmq_getsockopt (socket, ZMQ_RCVBUF, &val, &placeholder);
|
|
|
|
assert (rc == 0);
|
2016-05-03 18:46:34 +02:00
|
|
|
assert (val == -1);
|
2015-11-13 10:41:00 +01:00
|
|
|
|
|
|
|
val = 16384;
|
|
|
|
|
2016-02-09 10:51:51 +01:00
|
|
|
rc = zmq_setsockopt (socket, ZMQ_RCVBUF, &val, sizeof (val));
|
|
|
|
assert (rc == 0);
|
|
|
|
assert (val == 16384);
|
2015-11-13 10:41:00 +01:00
|
|
|
|
2016-02-09 10:51:51 +01:00
|
|
|
rc = zmq_getsockopt (socket, ZMQ_RCVBUF, &val, &placeholder);
|
|
|
|
assert (rc == 0);
|
|
|
|
assert (val == 16384);
|
2015-11-13 10:41:00 +01:00
|
|
|
|
2016-02-09 10:51:51 +01:00
|
|
|
zmq_close (socket);
|
|
|
|
zmq_ctx_term (ctx);
|
2015-11-13 10:41:00 +01:00
|
|
|
}
|
|
|
|
|
2016-02-09 10:51:51 +01:00
|
|
|
void test_setsockopt_tcp_send_buffer (void)
|
2015-11-13 10:41:00 +01:00
|
|
|
{
|
|
|
|
int rc;
|
2016-02-09 10:51:51 +01:00
|
|
|
void *ctx = zmq_ctx_new ();
|
|
|
|
void *socket = zmq_socket (ctx, ZMQ_PUSH);
|
2015-11-13 10:41:00 +01:00
|
|
|
|
|
|
|
int val = 0;
|
2016-02-09 10:51:51 +01:00
|
|
|
size_t placeholder = sizeof (val);
|
2015-11-13 10:41:00 +01:00
|
|
|
|
2016-02-09 10:51:51 +01:00
|
|
|
rc = zmq_getsockopt (socket, ZMQ_SNDBUF, &val, &placeholder);
|
|
|
|
assert (rc == 0);
|
2016-05-03 18:46:34 +02:00
|
|
|
assert (val == -1);
|
2015-11-13 10:41:00 +01:00
|
|
|
|
|
|
|
val = 16384;
|
|
|
|
|
2016-02-09 10:51:51 +01:00
|
|
|
rc = zmq_setsockopt (socket, ZMQ_SNDBUF, &val, sizeof (val));
|
|
|
|
assert (rc == 0);
|
|
|
|
assert (val == 16384);
|
2015-11-13 10:41:00 +01:00
|
|
|
|
2016-02-09 10:51:51 +01:00
|
|
|
rc = zmq_getsockopt (socket, ZMQ_SNDBUF, &val, &placeholder);
|
|
|
|
assert (rc == 0);
|
|
|
|
assert (val == 16384);
|
2015-11-13 10:41:00 +01:00
|
|
|
|
2016-02-09 10:51:51 +01:00
|
|
|
zmq_close (socket);
|
|
|
|
zmq_ctx_term (ctx);
|
2015-11-13 10:41:00 +01:00
|
|
|
}
|
|
|
|
|
2016-02-09 10:51:51 +01:00
|
|
|
void test_setsockopt_use_fd ()
|
2016-02-01 13:00:45 +01:00
|
|
|
{
|
|
|
|
int rc;
|
2016-02-09 10:51:51 +01:00
|
|
|
void *ctx = zmq_ctx_new ();
|
|
|
|
void *socket = zmq_socket (ctx, ZMQ_PUSH);
|
2016-02-01 13:00:45 +01:00
|
|
|
|
|
|
|
int val = 0;
|
2016-02-09 10:51:51 +01:00
|
|
|
size_t placeholder = sizeof (val);
|
2016-02-01 13:00:45 +01:00
|
|
|
|
2016-02-09 10:51:51 +01:00
|
|
|
rc = zmq_getsockopt (socket, ZMQ_USE_FD, &val, &placeholder);
|
2018-02-01 11:46:09 +01:00
|
|
|
assert (rc == 0);
|
|
|
|
assert (val == -1);
|
2016-02-01 13:00:45 +01:00
|
|
|
|
|
|
|
val = 3;
|
|
|
|
|
2018-02-01 11:46:09 +01:00
|
|
|
rc = zmq_setsockopt (socket, ZMQ_USE_FD, &val, sizeof (val));
|
|
|
|
assert (rc == 0);
|
|
|
|
assert (val == 3);
|
2016-02-01 13:00:45 +01:00
|
|
|
|
2016-02-09 10:51:51 +01:00
|
|
|
rc = zmq_getsockopt (socket, ZMQ_USE_FD, &val, &placeholder);
|
2018-02-01 11:46:09 +01:00
|
|
|
assert (rc == 0);
|
|
|
|
assert (val == 3);
|
2016-02-01 13:00:45 +01:00
|
|
|
|
2016-02-09 10:51:51 +01:00
|
|
|
zmq_close (socket);
|
|
|
|
zmq_ctx_term (ctx);
|
2016-02-01 13:00:45 +01:00
|
|
|
}
|
|
|
|
|
Add socket option BINDTODEVICE
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.
2017-07-28 15:35:09 +02:00
|
|
|
#define BOUNDDEVBUFSZ 16
|
|
|
|
void test_setsockopt_bindtodevice ()
|
|
|
|
{
|
|
|
|
void *ctx = zmq_ctx_new ();
|
|
|
|
void *socket = zmq_socket (ctx, ZMQ_PUSH);
|
|
|
|
|
2017-07-31 17:01:13 +02:00
|
|
|
#ifdef ZMQ_BINDTODEVICE
|
|
|
|
int rc;
|
Add socket option BINDTODEVICE
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.
2017-07-28 15:35:09 +02:00
|
|
|
char devname[BOUNDDEVBUFSZ];
|
|
|
|
size_t buflen = BOUNDDEVBUFSZ;
|
|
|
|
|
|
|
|
rc = zmq_getsockopt (socket, ZMQ_BINDTODEVICE, devname, &buflen);
|
2018-02-01 11:46:09 +01:00
|
|
|
assert (rc == 0);
|
|
|
|
assert (devname[0] == '\0');
|
|
|
|
assert (buflen == 1);
|
Add socket option BINDTODEVICE
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.
2017-07-28 15:35:09 +02:00
|
|
|
|
2018-02-01 11:46:09 +01:00
|
|
|
sprintf (devname, "testdev");
|
|
|
|
buflen = strlen (devname);
|
Add socket option BINDTODEVICE
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.
2017-07-28 15:35:09 +02:00
|
|
|
|
|
|
|
rc = zmq_setsockopt (socket, ZMQ_BINDTODEVICE, devname, buflen);
|
2018-02-01 11:46:09 +01:00
|
|
|
assert (rc == 0);
|
Add socket option BINDTODEVICE
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.
2017-07-28 15:35:09 +02:00
|
|
|
|
|
|
|
buflen = BOUNDDEVBUFSZ;
|
2018-02-01 11:46:09 +01:00
|
|
|
memset (devname, 0, buflen);
|
Add socket option BINDTODEVICE
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.
2017-07-28 15:35:09 +02:00
|
|
|
|
|
|
|
rc = zmq_getsockopt (socket, ZMQ_BINDTODEVICE, devname, &buflen);
|
2018-02-01 11:46:09 +01:00
|
|
|
assert (rc == 0);
|
|
|
|
assert (!strncmp ("testdev", devname, buflen));
|
2017-07-31 17:01:13 +02:00
|
|
|
#endif
|
Add socket option BINDTODEVICE
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.
2017-07-28 15:35:09 +02:00
|
|
|
|
|
|
|
zmq_close (socket);
|
|
|
|
zmq_ctx_term (ctx);
|
|
|
|
}
|
|
|
|
|
2016-02-09 10:51:51 +01:00
|
|
|
int main (void)
|
2015-11-13 10:41:00 +01:00
|
|
|
{
|
2016-02-09 10:51:51 +01:00
|
|
|
test_setsockopt_tcp_recv_buffer ();
|
|
|
|
test_setsockopt_tcp_send_buffer ();
|
|
|
|
test_setsockopt_use_fd ();
|
Add socket option BINDTODEVICE
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.
2017-07-28 15:35:09 +02:00
|
|
|
test_setsockopt_bindtodevice ();
|
2015-11-13 10:41:00 +01:00
|
|
|
}
|