-
Notifications
You must be signed in to change notification settings - Fork 86
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
[Feature] lan discovery (broadcast/multicast?) #115
Comments
I believe this is the documentation site. this is provides a friendly wrapper around/is based on @hyperswarm/dht "In the Hyperswarm DHT, peers are identified by a public key, not by an IP address. If you know someone's public key, you can connect to them regardless of where they're located". The underlying p2p mechanism is described in https://pdos.csail.mit.edu/~petar/papers/maymounkov-kademlia-lncs.pdf. I don't believe you can do that without replacing @hyperswarm/dht -- probably out of scope for this project. What I am wondering is, how do the dht nodes traffic their information? I havent actually read that PDF yet :P -- but I dont expect that the server related aspect of it is covered there. |
Connecting to different peers with specific IPs in a P2P network using Hyperswarm is not the typical way to use the library, as Hyperswarm is designed to handle peer discovery and connection management for you, using a Distributed Hash Table (DHT) for peer discovery based on a specific "topic." However, if you need to establish connections with specific IPs, you might need to use a direct connection solution using the Example of Direct Connection with Node.js
|
My scenario was developing a p2p application. |
In alternative is there a way to connect directly to a peer by ip:port?
The text was updated successfully, but these errors were encountered: