Arnaud Loonstra

probably related: #4342

Just after https://github.com/zeromq/libzmq/blob/875c2b15c30af70010c6681539b2195ba391069f/src/socket_base.cpp#L738 in socket_base.cpp the second udp socket is created ``` udp 0 0 0.0.0.0:1511 0.0.0.0:* 162018/czmqtests udp 0 0 0.0.0.0:6200 0.0.0.0:* 162018/czmqtests ``` However a few steps further...

I > Maybe `libzmq` can use the official `Findsodium.cmake` file, provided by libsodium? It does support linking statically. > > https://github.com/jedisct1/libsodium/blob/stable/contrib/Findsodium.cmake If this is a working fix can someone create...

Still tracing this. After creation of the second socket (second bind) I can see a socket is being created. (fd=10, first bind fd=9). However after creation I also see term...

I'm receiving an `attach` command for the second bind here (level 10 in stacktrace): https://github.com/zeromq/libzmq/blob/acfdf6712737380e0d0a83710e01f73975a241d1/src/io_thread.cpp#L91 Which results in reading a 'delimiter' on the pipe which triggers the destruction (level 2):...

I've reopened it but as long as nobody comes up with a PR it is to no avail?

As a reference when I change to TCP using a sub socket I get only the following commands: ``` plug own plug own ``` Then it runs just fine

Ok, it's a feature as the destroy is initiated here: https://github.com/zeromq/libzmq/blob/ce6d48c578a08770fb171486750300fd534d0254/src/dgram.cpp#L60-L66 Which clearly says: ``` ZMQ_DGRAM socket can only be connected to a single peer. The socket rejects any further...

Same for me, created a PR #13 I had to run as root as well. To succesfully compile on Debian trixie: `CFLAGS=-I/usr/include/libusb-1.0/ make`

To set permissions so you don't need to run as root: Create a udev rule: `/etc/udev/rules.d/11-rb3.rules` ``` SUBSYSTEMS=="usb", ATTRS{product}=="Harmonix RB3 Keyboard for Nintendo Wii", GROUP="users" ``` Now unplug and re-plug....