-
Notifications
You must be signed in to change notification settings - Fork 180
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
added multicast scouting ttl option #1032
Conversation
@@ -637,6 +647,7 @@ impl Runtime { | |||
// Must set to nonblocking according to the doc of tokio | |||
// https://docs.rs/tokio/latest/tokio/net/struct.UdpSocket.html#notes | |||
socket.set_nonblocking(true)?; | |||
socket.set_multicast_ttl_v4(multicast_ttl)?; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Here we don't join any multicast group. Isn't this a no-op?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
If I understand multicast properly, only listening for multicast packets requires joining a multicast group, but sending packets only requires sending to the correct IP address, and this is the function used in the scout function here to create the socket that send out multicast packets, so if the TTL is not set on this socket, then all the scouting messages sent will still have a TTL of 1. I tried taking this line out and saw that packet TTL was still 1.
@jeremiah-wooten Thank you for the contribution :) Welcome to Eclipse Zenoh! |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM.
adds the ability to change the ttl on the multicast scouting socket from the default of 1