From <http://www.tldp.org/HOWTO/Multicast-HOWTO-2.html>
"The TTL (Time To Live) field in the IP header has a double significance in multicast. As always, it controls the live time of the datagram to avoid it being looped forever due to routing errors. Routers decrement the TTL of every datagram as it traverses from one network to another and when its value reaches 0 the packet is dropped."
We are having some problems configuring our routers to allow dynamic peer discovery, one of the problems is that mantaray sets the IP TTL to 1 which according to the above paper means that there is a maximum of 1 hop between peers.
For our needs I changed the MutlicastGroupManager.sendMessageToGroup() to set the TTL to 3 but this probably should be user configured.
Best regards,
Luis Neves
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hello all,
From <http://www.tldp.org/HOWTO/Multicast-HOWTO-2.html>
"The TTL (Time To Live) field in the IP header has a double significance in multicast. As always, it controls the live time of the datagram to avoid it being looped forever due to routing errors. Routers decrement the TTL of every datagram as it traverses from one network to another and when its value reaches 0 the packet is dropped."
We are having some problems configuring our routers to allow dynamic peer discovery, one of the problems is that mantaray sets the IP TTL to 1 which according to the above paper means that there is a maximum of 1 hop between peers.
For our needs I changed the MutlicastGroupManager.sendMessageToGroup() to set the TTL to 3 but this probably should be user configured.
Best regards,
Luis Neves
Luis,
Your idea has merit to it.
I will make sure MantaRay's next release would contain this functionality.
P.S We are always looking for contributors...don't hesitate to drop me an email (yuval@coridan.com) if you'd like to join our contributors.
Best regards,
Yuval Lubowich
Chief Architect
MantaRay Team