You've already forked nakamoto-archive
32 lines
1.0 KiB
Markdown
32 lines
1.0 KiB
Markdown
|
|
---
|
||
|
|
layout: forum
|
||
|
|
title: 'Re: Simple to implement feature requests'
|
||
|
|
grand_parent: Forum Posts
|
||
|
|
parent: Bitcoin Forum
|
||
|
|
nav_order: 46
|
||
|
|
date: 2010-02-08 16:37:24 UTC
|
||
|
|
original: https://bitcointalk.org/index.php?topic=46.msg284#msg284
|
||
|
|
---
|
||
|
|
|
||
|
|
# Re: Simple to implement feature requests
|
||
|
|
---
|
||
|
|
|
||
|
|
```
|
||
|
|
Re: Simple to implement feature requests
|
||
|
|
February 08, 2010, 04:37:24 PM
|
||
|
|
|
||
|
|
There are command line options:
|
||
|
|
|
||
|
|
bitcoin -addnode=1.2.3.4 to tell bitcoin about a node to connect to
|
||
|
|
bitcoin -connect=1.2.3.4 connect only to the specified node(s)
|
||
|
|
|
||
|
|
You can use more than one of these, for instance
|
||
|
|
bitcoin -connect=(first to try) -connect=(next to try) ...
|
||
|
|
|
||
|
|
You can specify non-routable IPs with -connect like 192.168.x.x, so if you had a server farm and you wanted one server to connect to the world and the rest to connect to the one server, you could do that.
|
||
|
|
|
||
|
|
In particular, -addnode is needed if you're always going to connect through TOR, since the IRC server blocks all the TOR exit nodes. To connect through TOR, you could use:
|
||
|
|
|
||
|
|
bitcoin -proxy=127.0.0.1:9050 -addnode=212.159.72.216
|
||
|
|
```
|