From 1fd58bc867f336b3293d0e7ad6e1b90f1e90c987 Mon Sep 17 00:00:00 2001
From: wakgill <76528604+wakgill@users.noreply.github.com>
Date: Mon, 4 Jan 2021 22:45:01 -0600
Subject: [PATCH] Create 46.md

---
 docs/forum/bitcoin-forum/46.md | 31 +++++++++++++++++++++++++++++++
 1 file changed, 31 insertions(+)
 create mode 100644 docs/forum/bitcoin-forum/46.md

diff --git a/docs/forum/bitcoin-forum/46.md b/docs/forum/bitcoin-forum/46.md
new file mode 100644
index 0000000..4f3a079
--- /dev/null
+++ b/docs/forum/bitcoin-forum/46.md
@@ -0,0 +1,31 @@
+---
+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
+```