Open cliff101532 opened 2 years ago
Hi, yeah this seems like a better spot for your questions instead of the SMCRoute issue tracker, in a closed issue no less.
Just a quick observation. What do you mean by "not reachable"? When pinging a multicast address there is nobody there to respond (no ICMP reply). For an end-device to receive the multicast it has to join the group.
Also, I've not tested this project, and fail to remember what I did three years ago with SMCRoute to fix it, but if there's any routing involved you need to ensure you set the TTL value in your call to ping. In my version of ping (iputils) the command line I often use is ping -I eth0 -t 255
-- interface name and TTL value is up to you to fill in.
I got some problems. When I try to ping the group address of 239.0.0.1 from h2(172.16.0.100) it is not reachable. I used wireshark to observe h1-eth0 interface and I can't receive any package. I'm trying to do is that I want to ping a multicast group address and I wish the group member like h1 can get the multicast package. ex:h3 is a source. Sending package to a multicast group like 239.0.0.1. I'm wondering is it available to realised.