… | |
… | |
160 | =item trace <node> |
160 | =item trace <node> |
161 | |
161 | |
162 | Asks the given node for all currently connected nodes, then asks those |
162 | Asks the given node for all currently connected nodes, then asks those |
163 | nodes for the same, thus tracing all node connections. |
163 | nodes for the same, thus tracing all node connections. |
164 | |
164 | |
165 | =cut |
165 | =back |
166 | |
166 | |
167 | =head2 CONFIGURATION/NODE ID/SECRET/CERTIFICATE |
167 | =head2 CONFIGURATION/NODE ID/SECRET/CERTIFICATE |
168 | |
168 | |
169 | These commands deal with rather basic settings, the node ID, the shared |
169 | These commands deal with rather basic settings, the node ID, the shared |
170 | secret and the TLS certificate. |
170 | secret and the TLS certificate. |
… | |
… | |
220 | |
220 | |
221 | To discover the network you have to specify some seed addresses, which are |
221 | To discover the network you have to specify some seed addresses, which are |
222 | basically C<host:port> pairs where you expect some long-running nodes. It |
222 | basically C<host:port> pairs where you expect some long-running nodes. It |
223 | does no harm to have a node as its own seed (they will eventually be |
223 | does no harm to have a node as its own seed (they will eventually be |
224 | ignored). |
224 | ignored). |
|
|
225 | |
|
|
226 | =over 4 |
225 | |
227 | |
226 | =item setseeds <host:port>,... |
228 | =item setseeds <host:port>,... |
227 | |
229 | |
228 | Sets or replaces the list of seeds, which must be specified as a |
230 | Sets or replaces the list of seeds, which must be specified as a |
229 | comma-separated list of C<host:port> pairs. The C<host> can be a hostname, |
231 | comma-separated list of C<host:port> pairs. The C<host> can be a hostname, |