Sheriff recognizing Deputy on same Network, but sending commands doesn't work.

[junwoo091400]

Setup

1. Host

• Built Procman and LCM from source.
• Connected to local network via ethernet.
• Open "procman-sheriff" to monitor deputies.

2. Secondary device

• Built Procman and LCM from source.
• Connected to local network via WiFi.

Situation / Problem
First of all, opening on secondary devices, "procman-deputy -u udpm://239.255.76.67:7667?ttl=1" works to a point where the deputy gets recognized by the host's sheriff. And "Last update" time interval stays at 0.2 seconds, so data is getting through for sure.

But, if I set "?ttl=1" part to "?ttl=0" (which is a default LCM connection url, i.e. without '-u' option), host sheriff doesn't even recognize the deputy. Why would this behaviour arise?

Second of all, all the 'commands' related stuff doesn't work at the moment.

=> As seen here, the secondary device ('lilani') doesn't recognize nor receive (No command related output when the deputy is executed with '-v' flag, verbose output) the commands. Even though it does get recognized by the sheriff on the right panel.

3. Question
Why would this happen? It seems odd that deputy can send message to sheriff, but in reverse, it can't.
It also seems odd that with LCM's simple receiver / transmitter tutorial, even if I setup the secondary device's TX with 'udpm://239.255.76.67:7667?ttl=1' url when instantiating LCM, and RX on local with no url passed to the LCM object, the message doesn't get received (But the Deputy could send message to Sheriff in the situation above, hmm!).
Seems like I'm missing something (most likely on the network side), but not sure how to solve this problem.

[junwoo091400]

@ashuang Is this a known issue? Would really appreciate your feedback on this.

[ashuang]

Hi @junwoo091400 . Unfortunately I am unable to provide support. I wish you the best of luck resolving this issue, and if you're able to resolve it would appreciate if you're able to post your findings here as well.