[zeromq-dev] ZMQ monitor and zero's for remote ip's?

[Marc Norton]

Ok, but 9091 is the PUB socket port we use, not the clients SUB port that
connects to it.  We already know that.  Whats the clients SUB socket
 IP:PORT info look like ? is it available....

marc

On Fri, Nov 21, 2014 at 9:47 AM, Greg Rogers <grogers at clicksecurity.com>
wrote:

> Hooked up the monitor to an xpub socket per the zmq_socket_monitor man
> page but I am only getting zero's for the the ip, but getting correct
> initial port.
>
> click-admin at grogers-ubuntu:~/Ingest-Dev$ obj/broker -s tcp://*:9053 -i
> 60 -q 1000
> starting monitor...
> listening socket descriptor 14
> listening socket address tcp://0.0.0.0:9091
> accepted socket descriptor 15
> accepted socket address tcp://0.0.0.0:9091
> disconnected socket descriptor 15
> disconnected socket address tcp://0.0.0.0:9091
> accepted socket descriptor 15
> accepted socket address tcp://0.0.0.0:9091
> disconnected socket descriptor 15
> disconnected socket address tcp://0.0.0.0:9091
> accepted socket descriptor 15
> accepted socket address tcp://0.0.0.0:9091
> disconnected socket descriptor 15
> disconnected socket address tcp://0.0.0.0:9091
>
> These connections were local and remote hosts.
>
> Using 4.0.5 and 4.0.4
>
> Looks like in tcp_listener_t endpoint is used for all events instead of
> stream_engine_t::peer_address which is collected from socket info.
>
>
> _______________________________________________
> zeromq-dev mailing list
> zeromq-dev at lists.zeromq.org
> http://lists.zeromq.org/mailman/listinfo/zeromq-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.zeromq.org/pipermail/zeromq-dev/attachments/20141121/861c0720/attachment.htm>