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

Add my node to the list... #22

Open
username1565 opened this issue Aug 27, 2019 · 2 comments
Open

Add my node to the list... #22

username1565 opened this issue Aug 27, 2019 · 2 comments

Comments

@username1565
Copy link

username1565 commented Aug 27, 2019

I see here https://wiki.tox.chat/users/nodes#faq ,
for adding my node into the list of TOX-nodes,
I need send some email with some data to someone...
And my node cann't be added there, if I just open the port...
Hm...

Thelefore, you can make this node-list better.

  1. Just take list of IP-addresses for active peers.
  2. Check port 33445 (or declared domain_name:PORT, if DDNS or ONION-domain) - for them all.
  3. Add nodes to the list, if port is open.
  4. Ping them all regularry and sort this, by uptime.

Then you will got the nodes list, like the list on this service for monitoring the active torrent trackers: https://newtrackon.com/
This is open-source. Source code - here: https://github.com/CorralPeltzer/newTrackon


Also, maybe there is possible to create those lists for each node,
and check the status for all nodes regularry,
and return the list of active nodes, sorted by uptime - as JSON,
and as response to some packet at port 33445 for the current node.
For example, http://blah-blah:33445/nodes
can return something, like:
IP, PORT, KEY, UPTIME(milliseconds, or OFFLINE)


Also, this tests not working for TCP and UDP ports: https://nodes.tox.chat/test
for https://github.com/isotoxin/isotoxin/releases
even if ports has status opened,
and maybe this is a problem on your side,
because connection to the network is good for that isotoxin.
So, something need to fix.

Best Regards.

@alexbakker
Copy link
Member

Thelefore, you can make this node-list better.

Yes, there is definitely room for improvement. A similar idea is also discussed at the bottom of the wiki article you linked: https://wiki.tox.chat/users/nodes#is_there_anything_else_bootstrap_node_related_i_can_help_with_besides_running_a_bootstrap_node.

However, ToxStatus has been in maintenance mode for a while now. I ensure that it keeps working, but I don't do any active development on it anymore. Perhaps this is a project you would like to take on?

and return the list of active nodes, sorted by uptime - as JSON,

FYI: ToxStatus already provides a JSON-formatted list of nodes: https://nodes.tox.chat/json.

Also, this tests not working for TCP and UDP ports: https://nodes.tox.chat/test
for https://github.com/isotoxin/isotoxin/releases
even if ports has status opened,

Which error do you get when running the test? An open port is not enough. ToxStatus sends a TCP relay handshake packet and expects a response back.

@username1565
Copy link
Author

username1565 commented Aug 28, 2019

@alexbakker,

A similar idea is also discussed at the bottom of the wiki article you linked: https://wiki.tox.chat/users/nodes#is_there_anything_else_bootstrap_node_related_i_can_help_with_besides_running_a_bootstrap_node.

I see by your link the project https://toxstats.com and as I understand, there,
my node will be added automatically, if this node will working some time with opened port.
But this site not working for me and not opening.
Is there any source code?

FYI: ToxStatus already provides a JSON-formatted list of nodes: https://nodes.tox.chat/json.

This is nice, but I say about this answer from each node, like http://IP:PORT/nodes,
or as an answer to TCP/UDP packet at port 33445 (or decladed adress:PORT).
Maybe this can be programmed, of cource with saving the backward compatibility.

Which error do you get when running the test?

I enabled the TCP PORT 33445, in the settings of profile in Isotoxin.
And I see here https://ping.eu/port-chk/ this TCP PORT 33445 has status "open"

But this tests: https://nodes.tox.chat/test is not passed.
I see the following errors:

UDP PORT:

{
	"success": false,
	"latency": 0,
	"error": "request timed out"
}

TCP PORT:

{
	"success": false,
	"latency": 0,
	"error": "EOF"
}

An open port is not enough.
ToxStatus sends a TCP relay handshake packet and expects a response back.

So, maybe need to fix something in the Isotoxin.
isotoxin/isotoxin#25


Also, earlier, I just make the opened port, and just saw my node in that list, here: https://nodes.tox.chat/ without any another actions.
But now, I cann't, and something was been changed...

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