Dear Siva,
To provide additionnal context:
I used sudo ip addr add <239.192.22.10> dev eth0 autojoin to join automatically the multicast address on which the radar is supposed to broadcast information. (maddr add and ip route add don’t seem to work for some reason, see: Joining Multicast IP group).
I’ve been able to test that with a laptop and a script that writes to the same address and port as the radar is supposed to use and I was seeing packets using tcpdum.
The configuration was: windows laptop (ethernet) → E3579 dongle → Front pannel HSD 1|2.
I’ve recorded an acquisition with the radar (.pcap file) on an Orin NX in the configuration: radar → E3579 dongle → RJ45 port (ethernet). I can confirm from the headers of the messages that the addresses and ports I’m using are the correct ones.
(from pcap: src=192.168.3.33 dst=239.192.22.10 |<UDP sport=31122 dport=31122 ).
I’m wondering why I can confirm that i can listen through eth0 to the multicast group when using my PC but not the radar. And that from the other side, I can confirm that the radar writes to the proper addresses and is working.
** Important to note ** The radar capture and the laptop communication on the multicast group are both dependant on the usage of the E3579 dongle. No solution tried worked without this piece of equipment in the way. And the objective is to make it work by directly connecting the ARS430RDI_v2 → HSD port and communicate via BR automotive ethernet.
What’s happening inside the dongle, and why is it working acting like a “magic black box” in our tests?
Thank you