-
Notifications
You must be signed in to change notification settings - Fork 177
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
Add gossip_target configuration option #1678
Conversation
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.
I tested this with 1 router and 10 peers.
With scouting/gossip/target:["router"]
on the peers:
$ tshark -r out.pcap -d tcp.port==60000-70000,zenoh -Y 'tcp.port != 7447' | grep -c 'OAM'
0
Without scouting/gossip/target:["router"]
on the peers (i.e. the ["router", "peer"]
default):
$ tshark -r out.pcap -d tcp.port==60000-70000,zenoh -Y 'tcp.port != 7447' | grep -c 'OAM'
139
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.
Added some comments regarding default config
Add gossip_target configuration option.
This options allows to restrain the type of zenoh instances (router, peer) the configured instance sends gossip messages to.
This may typically be used in rmw_zenoh to make peers do gossip with the router but not between each other saving a lot of traffic and computation.