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

tests should actually try to connect to the peer #24

Open
thefinn93 opened this issue Nov 26, 2015 · 9 comments
Open

tests should actually try to connect to the peer #24

thefinn93 opened this issue Nov 26, 2015 · 9 comments

Comments

@thefinn93
Copy link
Contributor

Right now we don't do much beyond validate the JSON structure. Tests should actually run cjdns, insert the peer, then verify that the connection succeeded via peerStats. It could also attempt to reach known nodes on Hyperboria to verify that the peer is connected to Hyperboria

@kylerchin
Copy link
Contributor

Can we have Travic-CI build CJDNS, then putting in the node via a npm manager? (cjdmaid hates me.) If we do that, some nodes may go off-line at anytime. If someone shuts down the server forgetting that CJDNS is running, what happens? That is hyperboria for you....
If we really wanted to... We could have an online status that checks if a particular peer is up by pinging it.

@thefinn93
Copy link
Contributor Author

Yes, we can and someone should go and write the scripting around that. You may have issues binding to the tun device, but you should be able to get cjdns to just check if the peering came up without that.

@kylerchin
Copy link
Contributor

kylerchin commented Jun 16, 2017 via email

@thefinn93
Copy link
Contributor Author

Okay, go for it. This ticket represents the need to have it done in CI. Maybe start there?

@kylerchin
Copy link
Contributor

Alright.... How do I insert the peer into /etc/cjdroute.conf ???

@kylerchin
Copy link
Contributor

We have to determine if the peer is IPV6 or IPv4 and then slot it into the correct place, do systemctl restart cjdns then test the connection, wipe the /etc/cjdroute.conf and repeat.

@thefinn93
Copy link
Contributor Author

That's one way. I would suggest starting a cjdns instance with no peers and no tun device configured, then adding the peer via the RPC interface, then use the RPC interface to check if it's connected.

@kylerchin
Copy link
Contributor

Some files have multiple IPs. Should I seperate the peers? what should I do?

@thefinn93
Copy link
Contributor Author

Yeah, test each peer individually

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

No branches or pull requests

2 participants