Tor fallback nodes

[Red Emerald]

Are you using mapaddress?

I just added this to my torrc and made my bitcoin.conf match

mapaddress 192.0.2.2 p2hwc26zdsrqxiix.onion
mapaddress 192.0.2.3 sh4ep6zb6vnoa2h5.onion
mapaddress 192.0.2.4 iy6ni3wkqazp4ytu.onion
mapaddress 192.0.2.5 bxfna6fhddpzduck.onion

I'll let you know if it works.  Why does bitcoin not support using a remote DNS? I would think it should considering it has proxy support.

Oh wow.  I finally found this page https://en.bitcoin.it/wiki/Fallback_Nodes#Tor_network

Would sure be nice if https://en.bitcoin.it/wiki/Tor mentioned it...


EDIT: That did it theymos! Thanks!

Code:

$ bitcoind getinfo
{
    "version" : 50000,
    "balance" : 3.74654100,
    "blocks" : 159331,
    "connections" : 1,
    "proxy" : "127.0.0.1:9050",
    "generate" : false,
    "genproclimit" : -1,
    "difficulty" : 1159929.49722438,
    "hashespersec" : 0,
    "testnet" : false,
    "keypoololdest" : 1319583806,
    "keypoolsize" : 101,
    "paytxfee" : 0.00000000,
    "errors" : ""
}

I'll add something to the wiki to make this more clear for people

[1714801693]

1714801693

[1714801693]

1714801693

[1714801693]

1714801693

[theymos]

Ah, that's where I thought you would have seen the list of hidden services. They shouldn't be listed elsewhere, since they're useless without the instructions.

[Red Emerald]

Ah, that's where I thought you would have seen the list of hidden services. They shouldn't be listed elsewhere, since they're useless without the instructions.

I removed them from the other page, added a link and expanded the explanation of how to properly connect to the hidden services.

I still think that if I set my server running the tor hidden service to also proxy it's connections through tor, then it will reject incoming connections and not work properly.

[Red Emerald]

I've added all of the tor fallback nodes to my torrc with mapaddress and I only connect to 1.  I'm pretty sure that my hidden service is the only one still online.

[Gavin Andresen]

Disclaimer:  I'm a Tor newbie and networking stuff isn't my strong suit, you probably know more about it than I do.

But: I fixed a Tor-related bug for version 0.6 a few days ago.  In particular, I moved all of the "turn this on or turn this off if running over Tor" to one spot (in the init.cpp file) and reworked the code so that you can override all of those decisions via command-line or bitcoin.conf switches (e.g. specify -nolisten=0 to set nolisten to false so you DO listen even if running a port 9050 proxy).

[Red Emerald]

Disclaimer:  I'm a Tor newbie and networking stuff isn't my strong suit, you probably know more about it than I do.

But: I fixed a Tor-related bug for version 0.6 a few days ago.  In particular, I moved all of the "turn this on or turn this off if running over Tor" to one spot (in the init.cpp file) and reworked the code so that you can override all of those decisions via command-line or bitcoin.conf switches (e.g. specify -nolisten=0 to set nolisten to false so you DO listen even if running a port 9050 proxy).

Great.  I'll be sure to test 0.6 with a proxy set and a tor hidden service sometime soon.

[Red Emerald]

I got another hidden service up and running.

You can see a list of them on the wiki, although it appears that my 2 are the only ones online

https://en.bitcoin.it/wiki/Fallback_Nodes#Tor_nodes

[mila]

I got another hidden service up and running.

hooray! : )

You can see a list of them on the wiki, although it appears that my 2 are the only ones online

there was this issue with Tor that as soon as you run a stable node, it gets high traffic as the network routes more and more through that node. probably folks gave up turning theirs off and on again. either you shape available bandwidth or tune tor to only consume a fair share of resources and then it might be sustainable. I hope I'm wrong and running tor is not an issue anymore