UDP replies on port 53535

[Keith Kiyohara]

I'm trying to debug why I don't see any replies when I send UDP commands on port 53535. I'm using netcat to send a command:

$ nc -uv 127.0.0.1 53535

Connection to 127.0.0.1 port 53535 [udp/*] succeeded!

/workspaces

I can see that qlab receives the command and tries to reply in the workspace status logs tab:

2021-02-02 10:41:17 (47786.084): unknown client sent OSC message: /workspaces

2021-02-02 10:41:17 (47786.085): unknown client getting OSC reply: /reply/workspaces "{"status":"ok","address":"\/workspaces","data":[{"version":"4.6.9","displayName":"explore_qlab","uniqueID":"11A57A93-5C3C-43A2-8163-31A4F70189B3","hasPasscode":false}]}"

But I never see a reply message. Using Wireshark shows that nothing appears be sent via UDP from qlab.

[Sam Kusnetz]

Hello Keith

QLab does not reply to UDP commands sent on port 53535. The Workspace Status window shows you what the reply *would* be, but this is as a convenience or debugging tool.

If you need replies from QLab, you need to send OSC messages to port 53000 via either TCP or UDP.

Best
Sam

––
Sam Kusnetz [he/him/his] (what is this?)
Figure 53
https://qlab.app | https://figure53.com

--
Contact support anytime: sup...@figure53.com
Follow QLab on Twitter: https://twitter.com/QLabApp
User Group Code of Conduct: https://qlab.app/code-of-conduct/
---
You received this message because you are subscribed to the Google Groups "QLab" group.
To unsubscribe from this group and stop receiving emails from it, send an email to qlab+uns...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/qlab/5770aef8-609e-44f5-827a-60e76d2a1b06n%40googlegroups.com.

[Keith Kiyohara]

Ok, thanks! Perhaps you could add this to the documentation to help other avoid this in the future.

[Taylor Glad]

Like this?  =P

But perhaps it could be slightly reworded for a small clarification, since it does respond to other ports as well.