I expect [netsend -u] to write responses from the server to its right outlet, but it isn't working. I've confirmed that 1. the messages are received by the server, and 2. the server responds correctly (other applications can receive and print responses). lsof -P | grep UDP | grep pd shows that pd is indeed listening for a response.

What would prevent the responses from being received, output, or printed by netsend?

@chvolow24 said:

What would prevent the responses from being received, output, or printed by netsend?

UDP is a dumb protocol: no handshaking, no confirmation of message receipt -- it's "I sent it out the port, then we just hope for the best."

Lack of handshaking means (AFAIK) UDP doesn't have a concept of sending back to the originating location. Because it's dumb, it's simpler: [netsend -u] only sends, [netreceive -u] only receives. The idea of passing a message into [netreceive] and it being sent somewhere doesn't make sense in UDP land.

In the helpfile, the "send back" functionality is demonstrated for TCP connections but not for UDP. I don't think this is a casual omission -- I think this actually reflects the functionality.

hjh

@chvolow24 On the client-side [netsend -u], are you connecting to both the send port and receive port?