Simple to implement feature requests(connecting Bitcoin network through proxy IP)
2010 Feb 8
See all posts
Simple to implement feature requests(connecting Bitcoin network through proxy IP) @ Satoshi Nakamoto
- Author
-
Satoshi Nakamoto
- Email
-
satoshinakamotonetwork@proton.me
- Site
-
https://satoshinakamoto.network
BlueSky
Simple to implement feature requests
February 08, 2010, 09:00:02 AM
First request:
Optional connect to IP dialog.
Explanation:
BitCoin connects to the network(of peers) by getting one of a number of
IP's from IRC at present, once connected to a single peer other
connections can be made, so if only 1 IP on the list are available then
you can connect to the network & make connections to other IP's(this
is my assumption, please correct me if I am wrong).
This is somewhat similar to how Tor works, when you first start it up
it attempts to connect to a public list of IP's(public bridge nodes).
This list being public is accessible to organisations that want to
prevent the use of Tor(for example the Chinese or Iranian government).
And so as a consequence these IP's are blocked, and you cannot connect
from these countries.
However there is the option to connect to the ip of a bridge (if you
know one, a friend in a free country running Tor in bridge mode perhaps)
and so this circumvents regime blocking attempts and is very robust.
Adding this feature will allow Bitcoin to function despite regime
efforts to prevent it.
Satoshi Nakamoto
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
Simple to implement feature requests(connecting Bitcoin network through proxy IP)
2010 Feb 8 See all postsSatoshi Nakamoto
satoshinakamotonetwork@proton.me
https://satoshinakamoto.network
First request:
Optional connect to IP dialog.
Explanation:
BitCoin connects to the network(of peers) by getting one of a number of IP's from IRC at present, once connected to a single peer other connections can be made, so if only 1 IP on the list are available then you can connect to the network & make connections to other IP's(this is my assumption, please correct me if I am wrong).
This is somewhat similar to how Tor works, when you first start it up it attempts to connect to a public list of IP's(public bridge nodes). This list being public is accessible to organisations that want to prevent the use of Tor(for example the Chinese or Iranian government). And so as a consequence these IP's are blocked, and you cannot connect from these countries.
However there is the option to connect to the ip of a bridge (if you know one, a friend in a free country running Tor in bridge mode perhaps) and so this circumvents regime blocking attempts and is very robust.
Adding this feature will allow Bitcoin to function despite regime efforts to prevent it.
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