Differences
This shows you the differences between two versions of the page.
Both sides previous revision Previous revision | Next revision Both sides next revision | ||
developers:client_examples:echo_bot [2017/08/17 16:26] nurupo Updated nurupo's node domain name |
developers:client_examples:echo_bot [2020/03/22 20:56] nurupo [Table] Update DHT bootstrap nodes as the current ones are offline |
||
---|---|---|---|
Line 68: | Line 68: | ||
Now we know that to be online in the context of Tox it means to connect to the DHT, so let's do that. First we need to know IP and port of a DHT node, as well as its public key, to be able to protect the communication. In Tox, every peer who has UDP connections enabled is a DHT node, even our Echo Bot. This means that it is possible for someone to connect to the DHT (i.e. to bootstrap) through our bot. However, in contrast to regular Tox peers, users using Tox to communicate with their friends, DHT nodes can be dedicated, i.e. have a more permanent IP address and be online most of the time, which means that knowing IP, port and public key of just few nodes is generally enough to be able to always connect to the DHT network. Because using dedicated DHT nodes to connect to the DHT is more reliable, since they are more likely to be online when we want to bootstrap into the DHT, that's what we will be using. Tox's wiki contains [[https:// | Now we know that to be online in the context of Tox it means to connect to the DHT, so let's do that. First we need to know IP and port of a DHT node, as well as its public key, to be able to protect the communication. In Tox, every peer who has UDP connections enabled is a DHT node, even our Echo Bot. This means that it is possible for someone to connect to the DHT (i.e. to bootstrap) through our bot. However, in contrast to regular Tox peers, users using Tox to communicate with their friends, DHT nodes can be dedicated, i.e. have a more permanent IP address and be online most of the time, which means that knowing IP, port and public key of just few nodes is generally enough to be able to always connect to the DHT network. Because using dedicated DHT nodes to connect to the DHT is more reliable, since they are more likely to be online when we want to bootstrap into the DHT, that's what we will be using. Tox's wiki contains [[https:// | ||
- | ^ IP ^ Port ^ Public Key ^ | + | ^ IP ^ Port |
- | | 178.62.250.138 | 33445 | '' | + | | 85.143.221.42 | 33445 | '' |
- | | 2a03:b0c0:2:d0::16:1 | 33445 | '' | + | | 2a04:ac00:1:9f00:5054:ff:fe01: |
- | | tox.zodiaclabs.org | 33445 | '' | + | | 78.46.73.141 |
- | | 163.172.136.118 | + | | 2a01: |
- | | 2001: | + | | tox.initramfs.io |
- | | 128.199.199.197 | + | | tox2.abilinski.com |
- | | 2400: | + | | 205.185.115.131 |
- | | node.tox.biribiri.org | 33445 | '' | + | | tox.kurnevsky.net | 33445 | '' |
We will use '' | We will use '' |