Setting beacon port does not set the broadcast port
posiczko opened this issue · comments
Hello,
It appears that setting beacon port via
require 'rbczmq'
beacon = ZMQ::Beacon.new(11111);
beacon.publish 'test'
has no effect what goes on the wire. Capturing the traffic on the wire when running the above multiple times shows that a port is always ephemeral:
23:56:53 pablo@galileo [~] > sudo tcpdump -i en0 -n 'broadcast or multicast'
Password:
tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
listening on en0, link-type EN10MB (Ethernet), capture size 65535 bytes
00:02:42.234151 IP 192.168.250.175.9508 > 255.255.255.255.9508: UDP, length 4
00:02:43.771552 IP 192.168.250.175.25892 > 255.255.255.255.25892: UDP, length 4
I'm not 100% sure if this is czmq issue or rbczmq yet, as I'm quite new to the zmq world. Or am I missing something basic?
I'm running rbczmq 1.7.5.
Thank you,
Pawel
Thanks for flagging :-)
Fixed in 1.7.6 ( a749e3f && http://rubygems.org/gems/rbczmq )
tcpdump confirmation:
10:33:09.887861 IP 192.168.1.2.11111 > 255.255.255.255.11111: UDP, length 4
10:33:10.888920 IP 192.168.1.2.11111 > 255.255.255.255.11111: UDP, length 4
10:33:11.888393 IP 192.168.1.2.11111 > 255.255.255.255.11111: UDP, length 4
10:33:12.889593 IP 192.168.1.2.11111 > 255.255.255.255.11111: UDP, length 4
10:33:13.890531 IP 192.168.1.2.11111 > 255.255.255.255.11111: UDP, length 4
10:33:14.891295 IP 192.168.1.2.11111 > 255.255.255.255.11111: UDP, length 4