subject:"\[zeromq\-dev\] No UDP broadcast message received using CZMQ zbeacon on RaspberryPi3"

Re: [zeromq-dev] No UDP broadcast message received using CZMQ zbeacon on RaspberryPi3

2016-12-14 Thread Johan Philips

Here the issues on our Odroids and RPis are solved as well! Many thanks to Luca 
for spotting the zmq bug and patching it!

Johan

On 13 Dec 2016, at 19:47, Rodrigo Madruga 
mailto:rodrigo.madr...@nexxtorage.com>> wrote:

Updated to latest libzmq master and got the zbeacon class working now.

Tested with direct compilation on RPi3 and cross-compiled via 
czmq/builds/rpi/build.sh.

Issue resolved.

Thank you Luca and zmq community!

Rodrigo Madruga.

[https://docs.google.com/uc?export=download&id=0Bw1T0J_CDTOXcGoydVkyQnF2ajQ]
Rodrigo Cheminn Madruga

Engenheiro de Desenvolvimento
Nexxtorage Cargo Technology
Fone/Fax +55 48 3341-4028
rodrigo.madr...@nexxtorage.com


2016-12-11 13:20 GMT-02:00 Luca Boccassi 
mailto:luca.bocca...@gmail.com>>:
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 
> mailto: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
> >
>  *:*
> udp0  0 *:bootpc*:*
> udp0  0 raspberrypi-001:ntp *:*
> udp0  0 raspberrypi:ntp *:*
> udp0  0 localhost:ntp   *:*
> udp0  0 *:ntp   *:*
> udp0  0 *:mdns  *:*
> udp0  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
> udp0  0 
> 255.255.255.255:5670
> 
> >*:*
> udp0  0 *:bootpc*:*
> udp0  0 raspberrypi-001:ntp *:*
> udp0  0 raspberrypi:ntp *:*
> udp0  0 localhost:ntp   *:*
> udp0  0 *:ntp

Re: [zeromq-dev] No UDP broadcast message received using CZMQ zbeacon on RaspberryPi3

2016-12-13 Thread Rodrigo Madruga

Updated to latest libzmq master and got the zbeacon class working now.

Tested with direct compilation on RPi3 and cross-compiled via
czmq/builds/rpi/build.sh.

Issue resolved.

Thank you Luca and zmq community!

Rodrigo Madruga.

  *Rodrigo Cheminn Madruga*

Engenheiro de Desenvolvimento
Nexxtorage Cargo Technology
Fone/Fax +55 48 3341-4028
rodrigo.madr...@nexxtorage.com

2016-12-11 13:20 GMT-02:00 Luca Boccassi :

> 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 :
> >
> >
> > 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
> > 
> >  *:*
> > udp0  0 *:bootpc*:*
> > udp0  0 raspberrypi-001:ntp *:*
> > udp0  0 raspberrypi:ntp *:*
> > udp0  0 localhost:ntp   *:*
> > udp0  0 *:ntp   *:*
> > udp0  0 *:mdns  *:*
> > udp0  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
> > udp0  0 255.255.255.255:5670
> > *:*
> > udp0  0 *:bootpc*:*
> > udp0  0 raspberrypi-001:ntp *:*
> > udp0  0 raspberrypi:ntp *:*
> > udp0  0 localhost:ntp   *:*
> > udp0  0 *:ntp   *:*
> > udp0  0 *:mdns  *:*
> > udp0  0 *:38304 *:*
> > udp6   0  0 [::]:ntp[::]:*
> > udp6   0  0 [::]:mdns   [::]:*
> >

Re: [zeromq-dev] No UDP broadcast message received using CZMQ zbeacon on RaspberryPi3

2016-12-11 Thread Gangadhara Rao Baggu

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 
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 :
> >
> >
> > 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
> > 
> >  *:*
> > udp0  0 *:bootpc*:*
> > udp0  0 raspberrypi-001:ntp *:*
> > udp0  0 raspberrypi:ntp *:*
> > udp0  0 localhost:ntp   *:*
> > udp0  0 *:ntp   *:*
> > udp0  0 *:mdns  *:*
> > udp0  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
> > udp0  0 255.255.255.255:5670
> > *:*
> > udp0  0 *:bootpc*:*
> > udp0  0 raspberrypi-001:ntp *:*
> > udp0  0 raspberrypi:ntp *:*
> > udp0  0 localhost:ntp   *:*
> > udp0  0 *:ntp   *:*
> > udp0  0 *:mdns  *:*
> > udp0  0 *:38304 *:*
> > udp6   0  0 [::]:ntp[::]:*
> > udp6   0  0 [::]:mdns   [::]:*
> > udp6   0

Re: [zeromq-dev] No UDP broadcast message received using CZMQ zbeacon on RaspberryPi3

2016-12-11 Thread Luca Boccassi

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 :
> 
> 
> 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
> 
>  *:*
> udp0  0 *:bootpc*:*
> udp0  0 raspberrypi-001:ntp *:*
> udp0  0 raspberrypi:ntp *:*
> udp0  0 localhost:ntp   *:*
> udp0  0 *:ntp   *:*
> udp0  0 *:mdns  *:*
> udp0  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
> udp0  0 255.255.255.255:5670
> *:*
> udp0  0 *:bootpc*:*
> udp0  0 raspberrypi-001:ntp *:*
> udp0  0 raspberrypi:ntp *:*
> udp0  0 localhost:ntp   *:*
> udp0  0 *:ntp   *:*
> udp0  0 *:mdns  *:*
> udp0  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 exactl

Re: [zeromq-dev] No UDP broadcast message received using CZMQ zbeacon on RaspberryPi3

2016-12-05 Thread Rodrigo Madruga

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 :

>
>
> 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 
>>  *:*
>> udp0  0 *:bootpc*:*
>> udp0  0 raspberrypi-001:ntp *:*
>> udp0  0 raspberrypi:ntp *:*
>> udp0  0 localhost:ntp   *:*
>> udp0  0 *:ntp   *:*
>> udp0  0 *:mdns  *:*
>> udp0  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
>> udp0  0 255.255.255.255:5670
>> *:*
>> udp0  0 *:bootpc*:*
>> udp0  0 raspberrypi-001:ntp *:*
>> udp0  0 raspberrypi:ntp *:*
>> udp0  0 localhost:ntp   *:*
>> udp0  0 *:ntp   *:*
>> udp0  0 *:mdns  *:*
>> udp0  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 > >:
>>
>> 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
>> > 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 
>>
>>
>> ___
>> zeromq-dev mailing list
>> zeromq-dev@lists.zeromq.org 
>> http://lists.zeromq.org/mailman/listinfo/zeromq-dev
>> 
>>
>>
>>
>>
>> _

Re: [zeromq-dev] No UDP broadcast message received using CZMQ zbeacon on RaspberryPi3

2016-12-02 Thread Luca Boccassi

On Fri, 2016-12-02 at 15:51 +0100, Johan Philips wrote:
> 
> 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 
> >  *:*
> > udp0  0 *:bootpc*:*
> > udp0  0 raspberrypi-001:ntp *:*
> > udp0  0 raspberrypi:ntp *:*
> > udp0  0 localhost:ntp   *:*
> > udp0  0 *:ntp   *:*
> > udp0  0 *:mdns  *:*
> > udp0  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
> > udp0  0 255.255.255.255:5670
> > *:*
> > udp0  0 *:bootpc*:*
> > udp0  0 raspberrypi-001:ntp *:*
> > udp0  0 raspberrypi:ntp *:*
> > udp0  0 localhost:ntp   *:*
> > udp0  0 *:ntp   *:*
> > udp0  0 *:mdns  *:*
> > udp0  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

I would recommend to open an issue on Github:

https://github.com/zeromq/zyre/issues

And paste/upload to gist all logs and minimal code/test case to
reproduce the problem, details about the build and runtime environments
to reproduce, etc.

Kind regards,
Luca Boccassi


signature.asc
Description: This is a digitally signed message part
___
zeromq-dev mailing list
zeromq-dev@lists.zeromq.org
http://lists.zeromq.org/mailman/listinfo/zeromq-dev

Re: [zeromq-dev] No UDP broadcast message received using CZMQ zbeacon on RaspberryPi3

2016-12-02 Thread Johan Philips




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 
 *:*
udp0  0 *:bootpc*:*
udp0  0 raspberrypi-001:ntp *:*
udp0  0 raspberrypi:ntp *:*
udp0  0 localhost:ntp   *:*
udp0  0 *:ntp   *:*
udp0  0 *:mdns  *:*
udp0  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
udp0  0 255.255.255.255:5670
*:*
udp0  0 *:bootpc*:*
udp0  0 raspberrypi-001:ntp *:*
udp0  0 raspberrypi:ntp *:*
udp0  0 localhost:ntp   *:*
udp0  0 *:ntp   *:*
udp0  0 *:mdns  *:*
udp0  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 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 
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 


___
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

Re: [zeromq-dev] No UDP broadcast message received using CZMQ zbeacon on RaspberryPi3

2016-11-28 Thread Rodrigo Madruga

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 *:*
udp0  0 *:bootpc*:*
udp0  0 raspberrypi-001:ntp *:*
udp0  0 raspberrypi:ntp *:*
udp0  0 localhost:ntp   *:*
udp0  0 *:ntp   *:*
udp0  0 *:mdns  *:*
udp0  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
udp0  0 255.255.255.255:5670*:*
udp0  0 *:bootpc*:*
udp0  0 raspberrypi-001:ntp *:*
udp0  0 raspberrypi:ntp *:*
udp0  0 localhost:ntp   *:*
udp0  0 *:ntp   *:*
udp0  0 *:mdns  *:*
udp0  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.

Any tips are welcome...

Thanks!

Rodrigo Madruga.

2016-11-28 13:19 GMT-02:00 Wes Young :

> 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> 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
>
>
> ___
> 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

Re: [zeromq-dev] No UDP broadcast message received using CZMQ zbeacon on RaspberryPi3

2016-11-28 Thread Wes Young

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  
> 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



signature.asc
Description: Message signed with OpenPGP using GPGMail
___
zeromq-dev mailing list
zeromq-dev@lists.zeromq.org
http://lists.zeromq.org/mailman/listinfo/zeromq-dev

Re: [zeromq-dev] No UDP broadcast message received using CZMQ zbeacon on RaspberryPi3

2016-11-28 Thread Kevin Sapper

I successfully used it through zyre on 20 raspberry pi1.

Am 28.11.2016 3:50 nachm. schrieb "Luca Boccassi" :

> Hi,
>
> There is a CZMQ 4.0.x series now, loads of changes have gone in since
> 3.0.2. I would recommend trying it as the first thing.
>
> https://github.com/zeromq/czmq/releases
>
> On Mon, 2016-11-28 at 12:42 -0200, Rodrigo Madruga wrote:
> > Hello all,
> >
> > I am developing a system that uses CZMQ's zbeacon (broadcast on UDP) for
> > app discovery. Beacon sender is Windows box and receiver is RaspberryPi3.
> >
> > As the subject says, no message is reaching the zbeacon actor.
> >
> > Using czmq3.0.2 and zmq4.1.6 built directly on pi to rule out
> > cross-compiling issues.
> >
> > Calling just zbeacon_test() returns "OK" without assertions errors.
> >
> > 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
> >
> > The code used to test is based on zbeacon_test function:
> >
> > zactor_t *listener = zactor_new (zbeacon, NULL);
> > assert (listener);
> > zsock_send (listener, "si", "CONFIGURE", 5670);
> > hostname = zstr_recv (listener);
> > assert (*hostname);
> > free (hostname);
> >
> > zsock_send (listener, "sb", "SUBSCRIBE", "", 0);
> >
> > zpoller_t *poller = zpoller_new (listener, NULL);
> > assert (poller);
> > int64_t stop_at = zclock_mono () + 1; // wait 10 seconds
> > while (zclock_mono () < stop_at) {
> > long timeout = (long) (stop_at - zclock_mono ());
> > if (timeout < 0)
> > timeout = 0;
> > void *which = zpoller_wait (poller, timeout * ZMQ_POLL_MSEC);
> > if (which) {
> > char *ipaddress, *received;
> > zstr_recvx (which, &ipaddress, &received, NULL);
> > printf("From address %s:%s\n", ipaddress, received);
> > zstr_free (&ipaddress);
> > zstr_free (&received);
> > }
> > }
> > zpoller_destroy (&poller);
> >
> > //  Stop listening
> > zstr_sendx (listener, "UNSUBSCRIBE", NULL);
> >
> > //  Destroy the test nodes
> > zactor_destroy (&listener);
> >
> > I cross-compiled a simple Qt app with a QUdpSocket (below) and the
> messages
> > were received without issues:
> >
> > #include 
> >
> > TestUDP::TestUDP(QObject *parent) :
> > QObject(parent)
> > {
> > qDebug() << "Binding UDP Socket";
> > socket = new QUdpSocket(this);
> > socket->bind(QHostAddress::Any, 5670);
> > connect(socket, &QUdpSocket::readyRead,this,
> &TestUDP::readyRead);
> > qDebug() << "Ready Read signal connected0, waiting for
> broadcasts";
> > }
> >
> > void TestUDP::readyRead(){
> > QByteArray buffer;
> > buffer.resize(socket->pendingDatagramSize());
> > //var to store headers from udp
> > QHostAddress sender;
> > quint16 sender_port;
> > socket->readDatagram(buffer.data(),buffer.size(), &sender,
> > &sender_port);
> > qDebug() << "Message from " << sender << " port " << sender_port;
> > qDebug() << "Msg: " << buffer;
> > }
> >
> > Maybe the problem is at the way zbeacon is dealing with the UDP socket...
> >
> > Has anyone successfully used a zbeacon on RPI3?
> >
> > Thanks in advance!
> >
> > Rodrigo Madruga.
> > ___
> > 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

Re: [zeromq-dev] No UDP broadcast message received using CZMQ zbeacon on RaspberryPi3

2016-11-28 Thread Luca Boccassi

Hi,

There is a CZMQ 4.0.x series now, loads of changes have gone in since
3.0.2. I would recommend trying it as the first thing.

https://github.com/zeromq/czmq/releases

On Mon, 2016-11-28 at 12:42 -0200, Rodrigo Madruga wrote:
> Hello all,
> 
> I am developing a system that uses CZMQ's zbeacon (broadcast on UDP) for
> app discovery. Beacon sender is Windows box and receiver is RaspberryPi3.
> 
> As the subject says, no message is reaching the zbeacon actor.
> 
> Using czmq3.0.2 and zmq4.1.6 built directly on pi to rule out
> cross-compiling issues.
> 
> Calling just zbeacon_test() returns "OK" without assertions errors.
> 
> 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
> 
> The code used to test is based on zbeacon_test function:
> 
> zactor_t *listener = zactor_new (zbeacon, NULL);
> assert (listener);
> zsock_send (listener, "si", "CONFIGURE", 5670);
> hostname = zstr_recv (listener);
> assert (*hostname);
> free (hostname);
> 
> zsock_send (listener, "sb", "SUBSCRIBE", "", 0);
> 
> zpoller_t *poller = zpoller_new (listener, NULL);
> assert (poller);
> int64_t stop_at = zclock_mono () + 1; // wait 10 seconds
> while (zclock_mono () < stop_at) {
> long timeout = (long) (stop_at - zclock_mono ());
> if (timeout < 0)
> timeout = 0;
> void *which = zpoller_wait (poller, timeout * ZMQ_POLL_MSEC);
> if (which) {
> char *ipaddress, *received;
> zstr_recvx (which, &ipaddress, &received, NULL);
> printf("From address %s:%s\n", ipaddress, received);
> zstr_free (&ipaddress);
> zstr_free (&received);
> }
> }
> zpoller_destroy (&poller);
> 
> //  Stop listening
> zstr_sendx (listener, "UNSUBSCRIBE", NULL);
> 
> //  Destroy the test nodes
> zactor_destroy (&listener);
> 
> I cross-compiled a simple Qt app with a QUdpSocket (below) and the messages
> were received without issues:
> 
> #include 
> 
> TestUDP::TestUDP(QObject *parent) :
> QObject(parent)
> {
> qDebug() << "Binding UDP Socket";
> socket = new QUdpSocket(this);
> socket->bind(QHostAddress::Any, 5670);
> connect(socket, &QUdpSocket::readyRead,this, &TestUDP::readyRead);
> qDebug() << "Ready Read signal connected0, waiting for broadcasts";
> }
> 
> void TestUDP::readyRead(){
> QByteArray buffer;
> buffer.resize(socket->pendingDatagramSize());
> //var to store headers from udp
> QHostAddress sender;
> quint16 sender_port;
> socket->readDatagram(buffer.data(),buffer.size(), &sender,
> &sender_port);
> qDebug() << "Message from " << sender << " port " << sender_port;
> qDebug() << "Msg: " << buffer;
> }
> 
> Maybe the problem is at the way zbeacon is dealing with the UDP socket...
> 
> Has anyone successfully used a zbeacon on RPI3?
> 
> Thanks in advance!
> 
> Rodrigo Madruga.
> ___
> zeromq-dev mailing list
> zeromq-dev@lists.zeromq.org
> http://lists.zeromq.org/mailman/listinfo/zeromq-dev




signature.asc
Description: This is a digitally signed message part
___
zeromq-dev mailing list
zeromq-dev@lists.zeromq.org
http://lists.zeromq.org/mailman/listinfo/zeromq-dev

[zeromq-dev] No UDP broadcast message received using CZMQ zbeacon on RaspberryPi3

2016-11-28 Thread Rodrigo Madruga

Hello all,

I am developing a system that uses CZMQ's zbeacon (broadcast on UDP) for
app discovery. Beacon sender is Windows box and receiver is RaspberryPi3.

As the subject says, no message is reaching the zbeacon actor.

Using czmq3.0.2 and zmq4.1.6 built directly on pi to rule out
cross-compiling issues.

Calling just zbeacon_test() returns "OK" without assertions errors.

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

The code used to test is based on zbeacon_test function:

zactor_t *listener = zactor_new (zbeacon, NULL);
assert (listener);
zsock_send (listener, "si", "CONFIGURE", 5670);
hostname = zstr_recv (listener);
assert (*hostname);
free (hostname);

zsock_send (listener, "sb", "SUBSCRIBE", "", 0);

zpoller_t *poller = zpoller_new (listener, NULL);
assert (poller);
int64_t stop_at = zclock_mono () + 1; // wait 10 seconds
while (zclock_mono () < stop_at) {
long timeout = (long) (stop_at - zclock_mono ());
if (timeout < 0)
timeout = 0;
void *which = zpoller_wait (poller, timeout * ZMQ_POLL_MSEC);
if (which) {
char *ipaddress, *received;
zstr_recvx (which, &ipaddress, &received, NULL);
printf("From address %s:%s\n", ipaddress, received);
zstr_free (&ipaddress);
zstr_free (&received);
}
}
zpoller_destroy (&poller);

//  Stop listening
zstr_sendx (listener, "UNSUBSCRIBE", NULL);

//  Destroy the test nodes
zactor_destroy (&listener);

I cross-compiled a simple Qt app with a QUdpSocket (below) and the messages
were received without issues:

#include 

TestUDP::TestUDP(QObject *parent) :
QObject(parent)
{
qDebug() << "Binding UDP Socket";
socket = new QUdpSocket(this);
socket->bind(QHostAddress::Any, 5670);
connect(socket, &QUdpSocket::readyRead,this, &TestUDP::readyRead);
qDebug() << "Ready Read signal connected0, waiting for broadcasts";
}

void TestUDP::readyRead(){
QByteArray buffer;
buffer.resize(socket->pendingDatagramSize());
//var to store headers from udp
QHostAddress sender;
quint16 sender_port;
socket->readDatagram(buffer.data(),buffer.size(), &sender,
&sender_port);
qDebug() << "Message from " << sender << " port " << sender_port;
qDebug() << "Msg: " << buffer;
}

Maybe the problem is at the way zbeacon is dealing with the UDP socket...

Has anyone successfully used a zbeacon on RPI3?

Thanks in advance!

Rodrigo Madruga.
___
zeromq-dev mailing list
zeromq-dev@lists.zeromq.org
http://lists.zeromq.org/mailman/listinfo/zeromq-dev

Re: [zeromq-dev] No UDP broadcast message received using CZMQ zbeacon on RaspberryPi3

Re: [zeromq-dev] No UDP broadcast message received using CZMQ zbeacon on RaspberryPi3

Re: [zeromq-dev] No UDP broadcast message received using CZMQ zbeacon on RaspberryPi3

Re: [zeromq-dev] No UDP broadcast message received using CZMQ zbeacon on RaspberryPi3

Re: [zeromq-dev] No UDP broadcast message received using CZMQ zbeacon on RaspberryPi3

Re: [zeromq-dev] No UDP broadcast message received using CZMQ zbeacon on RaspberryPi3

Re: [zeromq-dev] No UDP broadcast message received using CZMQ zbeacon on RaspberryPi3

Re: [zeromq-dev] No UDP broadcast message received using CZMQ zbeacon on RaspberryPi3

Re: [zeromq-dev] No UDP broadcast message received using CZMQ zbeacon on RaspberryPi3

Re: [zeromq-dev] No UDP broadcast message received using CZMQ zbeacon on RaspberryPi3

Re: [zeromq-dev] No UDP broadcast message received using CZMQ zbeacon on RaspberryPi3

[zeromq-dev] No UDP broadcast message received using CZMQ zbeacon on RaspberryPi3

12 matches

Site Navigation

Mail list logo

Footer information