-
Notifications
You must be signed in to change notification settings - Fork 23
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 enable mDNS and Rendezvous config settings #376
Labels
Comments
bgins
added
enhancement
New feature or request
networking
Features, functionality involving networking
labels
Oct 11, 2023
bgins
added a commit
that referenced
this issue
Oct 12, 2023
# Description This PR implements the following features: - [x] Add `enable_mdns` config - [x] Add `enable_rendezvous` config These configs determine whether we toggle mDNS and Rendezvous on or off. In addition, we check the toggle states in event handlers where we might use mDNS or Rendezvous. ## Link to issue Closes #376 ## Type of change - [x] New feature (non-breaking change that adds functionality) - [x] Refactor (non-breaking change that updates existing functionality) ## Test plan (required) All existing tests should pass. In particular, we are interested in the multi-node tests that rely on known peers and mDNS.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
Summary
Problem
We run libp2p mDNS and Rendezvous by default as a best effort mechanism to connect peers, but there are some circumstances where we don't want them all running.
Impact
Testing can be challenging when we want to check that one behavior or another is responsible for discovery or establishing a peer connection.
Some binary users may want to shut off these behaviors. For example, mDNS may not be useful to a Homestar node not running on a LAN.
Solution
Add configs to turn mDNS and Rendezvous behaviors on or off.
The text was updated successfully, but these errors were encountered: