Hello, David! Am I right you have a subscriber up and running?
Otherwise tshark cannot observe anything since there is no established TCP session and your process is just awaiting for an incoming TCP connection and you can probably prove it with the help of netstat. "Publisher" implies information is emitted to the air though TCP works differently. 06.09.10, 20:53, "david starkweather" <[email protected]>: > hello, > > I have a simple test case here that mirrors what i am doing in my main > project. I need to publish messages from several worker threads, so I > have a socket to connect to an ipc pipe from each thread and then a > forwarder device to forward from the backend socket to the main > publisher socket in the main thread. The problem is that when I monitor > the port, no messages are forthcoming. > > I monitor the port with the line: tshark -f "tcp port 4000" -i eth1 > > (and with -i lo) -- Best regards, Ilja Golshtein. _______________________________________________ zeromq-dev mailing list [email protected] http://lists.zeromq.org/mailman/listinfo/zeromq-dev
