Skip to content
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

Test Connecting Multiple Host Implementation #10

Open
araskachoi opened this issue Sep 30, 2019 · 4 comments
Open

Test Connecting Multiple Host Implementation #10

araskachoi opened this issue Sep 30, 2019 · 4 comments

Comments

@araskachoi
Copy link
Contributor

araskachoi commented Sep 30, 2019

Will need to verify that two host clients will be able to communicate with one another

  • spin two clients up
  • add the client to the static peers file (IP)
  • establish a handshake (if applicable)
  • verify that packets can be sent from one client to another
  • output to stdout and pipe to a file
@araskachoi
Copy link
Contributor Author

@adam-hanna
Do you think you can describe the process briefly (with the exact commands) so that i can easily deploy this on my own?

@adam-hanna
Copy link

@araskachoi yup! The easiest way to do this is via the subnet command: $ go run ./cmd/subnet/main.go

The default will connect 10 hosts together using the whiteblocks peering topology. Make any necessary changes to configs/subnet/config.json

See the readme for how to manually connect hosts.

@araskachoi
Copy link
Contributor Author

araskachoi commented Oct 2, 2019

@adam-hanna so the issue with using subnet would be that it would all be done on one container. We will need to generate multiple containers that are logically separated with their own designated IP.

I was more interested in the command that is required to connect two clients that have been spun up.

I believe we are using unique node identifiers using the multiaddr format provided by lilbp2p. is there a way to simplify this to just the IP address?

@adam-hanna
Copy link

adam-hanna commented Oct 2, 2019

yeah, I was building subnet for myself.

You can connect a host to another by passing it the cli flag -p or via the config file. Just give it a comma separated list. This won't work for hosts that are already running, obviously.

I'll add a command to the rpc channel (and implement it on the client) to be able to tell it to connect to another host. In this way, we'll be able to connect, after spinning up.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants