Closed simonvanderveldt closed 3 years ago
I've managed to "fix" this for now by disabling IPv6, so I guess it's caused by the application not actually listening to messages going to the IPv4 address. I'll do a search if I can find a bug for it or an option to pass to liblo to listen to both IPv4 and IPv6.
serialosc.maxpat
sends data toserialoscd
usinglocalhost
as the address, see https://github.com/monome/serialosc.maxpat/blob/master/serialosc.js#L32Unfortunately this doesn't work for me. I have to edit lines https://github.com/monome/serialosc.maxpat/blob/master/serialosc.js#L32-L33 and replace
localhost
with my computer's IP address to get it to work.I checked the application/patch part by running
oscdump 12002
and opening a patch, this results in the following outputSo the messages are correctly being sent and can be received by an application listening on UDP port
localhost:12002
.When running
serialoscd
netstat
shows thatserialoscd
is listening on0.0.0.0
So it seems like there's something going wrong within
serialoscd
which causes the messages not to be processed/picked up.Any suggestions/ideas how I can debug this/figure out what's causing this?
I'm using Linux btw, to be specific gentoo with both serialosc as well as libmonome built from current master.