-
Notifications
You must be signed in to change notification settings - Fork 74
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
Comments
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.... |
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. |
I have some spare time, I'd be happy to write a web app!
On Thu, Jun 15, 2017 at 9:38 PM Finn ***@***.***> wrote:
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.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#24 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AHMJ5qs2FcL2UHEkzv-IVTE5iOZE9s_4ks5sEgbEgaJpZM4GpsMq>
.
--
From Kyler Chin
|
Okay, go for it. This ticket represents the need to have it done in CI. Maybe start there? |
Alright.... How do I insert the peer into /etc/cjdroute.conf ??? |
We have to determine if the peer is IPV6 or IPv4 and then slot it into the correct place, do |
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. |
Some files have multiple IPs. Should I seperate the peers? what should I do? |
Yeah, test each peer individually |
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
The text was updated successfully, but these errors were encountered: