thanks for the quick response, I will with latest libzmq package (4.2.0) without changing any other package and get back to you.
I am using the following version pyzmq: 14.6.0 czmq: 3.0.2 libsodium: 1.0.6 Cython: 0.19-3 python: 2.7.5 please let me know any version is not compatible with the latest zmq. with regards Gangadhar On Sun, Dec 11, 2016 at 10:20 AM, Luca Boccassi <luca.bocca...@gmail.com> wrote: > Could you all please try with the very latest head of the libzmq master > branch? > > I could reproduce the problem, but it's fixed now, see my comment: > > https://github.com/zeromq/zyre/issues/496#issuecomment-266287690 > > On Mon, 2016-12-05 at 09:58 -0200, Rodrigo Madruga wrote: > > Hello Johan, > > > > > > We got the same behaviour here: > > > > > > - RPI3 running a zbeacon-publish loop being discovered correctly by a > > Linux machine > > - RPI3 running a zbeacon-subscribe loop do not discover anything at > > all > > > > > > As a temp workaround, we ended up replacing the zbeacon stuff with a > > working Qt class. > > > > > > I tried to change to czmq zsys_udp_new() in zsys.c to use the same > > options as Qt use to open the socket, but got no change in behaviour. > > > > > > > > > > > > > > > > > > Rodrigo > > > > 2016-12-02 12:51 GMT-02:00 Johan Philips <johan.phil...@kuleuven.be>: > > > > > > On 2016-11-28 19:03, Rodrigo Madruga wrote: > > A few more tests and information about the issue: > > > > pi@raspberrypi:~ $ uname -a > > Linux raspberrypi 4.4.26-v7+ #915 SMP Thu Oct 20 > > 17:08:44 BST 2016 > > armv7l GNU/Linux > > > > Now testing with zmq and czmq from master compiled on > > RPI with default > > options: > > > > *CZMQ version: 40002* > > *ZMQ version: 40201* > > > > Tried setting ZSYS_INTERFACE with "*", "wlan0", "eth0" > > and also not set > > at all (""). > > > > Using VERBOSE with zbeacon always indicate the correct > > interface being used: > > > > - Without setting or "eth0": > > > > I: 16-11-28 15:30:09 zbeacon: interface=eth0 > > address=192.168.25.214 > > broadcast=192.168.25.255 > > > > I: 16-11-28 15:30:09 zbeacon: configured, > > hostname=192.168.25.214 > > > > > > - Setting as "*" > > > > I: 16-11-28 15:25:18 zbeacon: configured, > > hostname=* > > > > > > Running sudo netstat -uac while executing tests had > > the following results: > > > > - No setting ("") - *notice that Recv-Q builds up with > > time!*: > > > > Active Internet connections (servers and > > established) > > Proto Recv-Q Send-Q Local Address > > Foreign Address > > State > > udp 9408 0 192.168.25.255:5670 > > <http://192.168.25.255:5670> > > *:* > > udp 0 0 *:bootpc *:* > > udp 0 0 raspberrypi-001:ntp *:* > > udp 0 0 raspberrypi:ntp *:* > > udp 0 0 localhost:ntp *:* > > udp 0 0 *:ntp *:* > > udp 0 0 *:mdns *:* > > udp 0 0 *:38304 *:* > > udp6 0 0 [::]:ntp [::]:* > > udp6 0 0 [::]:mdns [::]:* > > udp6 0 0 [::]:43395 [::]:* > > > > - ZSYS_INTERFACE = "*": > > > > Active Internet connections (servers and > > established) > > Proto Recv-Q Send-Q Local Address > > Foreign Address > > State > > udp 0 0 255.255.255.255:5670 > > <http://255.255.255.255:5670> *:* > > udp 0 0 *:bootpc *:* > > udp 0 0 raspberrypi-001:ntp *:* > > udp 0 0 raspberrypi:ntp *:* > > udp 0 0 localhost:ntp *:* > > udp 0 0 *:ntp *:* > > udp 0 0 *:mdns *:* > > udp 0 0 *:38304 *:* > > udp6 0 0 [::]:ntp [::]:* > > udp6 0 0 [::]:mdns [::]:* > > udp6 0 0 [::]:43395 [::]:* > > > > > > The only difference from the netstat output for the > > QtUdpSocket version > > is that the Recv-Q is always zero. > > > > > > We are experiencing exactly the same with our Odroids, only > > strange thing is they are still being discovered by our linux > > laptop but do not discover each other. Recv-Q on Odroids also > > builds up > > > > > > Any tips are welcome... > > > > Did you manage to solve your problem? > > > > > > Thanks! > > > > Rodrigo Madruga. > > > > Johan > > > > > > 2016-11-28 13:19 GMT-02:00 Wes Young > > <w...@barely3am.com > > <mailto:w...@barely3am.com>>: > > > > but is that what interface your app is listening > > (err telling > > zbeacon to listen on) for beacons on? > > > > (in addition in making sure you’re using the > > latest ver), follow the > > ZSYS_INTERFACE var a bit (it may or may not be set > > and be > > associating the beacon listener with the correct > > interface…) > > > > > On Nov 28, 2016, at 9:42 AM, Rodrigo Madruga > > <rodrigo.madr...@nexxtorage.com > > <mailto:rodrigo.madr...@nexxtorage.com>> wrote: > > > > > > Broadcast messages are indeed reaching the pi, > > as shown by tcpdump: > > > > > > pi@raspberrypi:~ $ sudo tcpdump udp port > > 5670 > > > tcpdump: verbose output suppressed, use -v > > or -vv for full protocol decode > > > listening on wlan0, link-type EN10MB > > (Ethernet), capture size 262144 bytes > > > 13:33:56.203230 IP [REDACTED].5670 > > > 192.168.1.255.5670: UDP, length 22 > > > 13:34:01.072476 IP [REDACTED].5670 > > > 192.168.1.255.5670: UDP, length 22 > > > > -- > > wes > > wesyoung.me <http://wesyoung.me> > > > > > > _______________________________________________ > > zeromq-dev mailing list > > zeromq-dev@lists.zeromq.org > > <mailto:zeromq-dev@lists.zeromq.org> > > > > http://lists.zeromq.org/mailman/listinfo/zeromq-dev > > > > <http://lists.zeromq.org/mailman/listinfo/zeromq-dev> > > > > > > > > > > _______________________________________________ > > zeromq-dev mailing list > > zeromq-dev@lists.zeromq.org > > http://lists.zeromq.org/mailman/listinfo/zeromq-dev > > > > _______________________________________________ > > zeromq-dev mailing list > > zeromq-dev@lists.zeromq.org > > http://lists.zeromq.org/mailman/listinfo/zeromq-dev > > > > > > _______________________________________________ > > zeromq-dev mailing list > > zeromq-dev@lists.zeromq.org > > http://lists.zeromq.org/mailman/listinfo/zeromq-dev > > > _______________________________________________ > zeromq-dev mailing list > zeromq-dev@lists.zeromq.org > https://lists.zeromq.org/mailman/listinfo/zeromq-dev >
_______________________________________________ zeromq-dev mailing list zeromq-dev@lists.zeromq.org https://lists.zeromq.org/mailman/listinfo/zeromq-dev
