Author

Topic: More info than just "bitcoind getconnectioncount" (Read 1047 times)

hero member
Activity: 742
Merit: 500
December 27, 2011, 01:31:57 PM
#5
I just want to see the IPs that bitcoin is talking to.

Look up the `netstat` command.  You can use a (platform-dependent) switch to see which connections are associated with which processes.
Good idea.  I'll play around with that.

I did get my tor relay working last night, though! It did have to do with bitcoin being to dumb to use the remote DNS.  I've updated the wiki to explain how to properly do it.
full member
Activity: 225
Merit: 101
I just want to see the IPs that bitcoin is talking to.

Look up the `netstat` command.  You can use a (platform-dependent) switch to see which connections are associated with which processes.
hero member
Activity: 742
Merit: 500
Wouldn't work without modifying the protocol and sourcecode.
What would have to change in the protocol? I just want to see the IPs that bitcoin is talking to.
legendary
Activity: 1232
Merit: 1076
Wouldn't work without modifying the protocol and sourcecode.
hero member
Activity: 742
Merit: 500
I am trying to setup a tor hidden service for bitcoin and am having a difficult time getting it to actually work.  It would be helpful if I could see the clients connected to me instead of just the number of clients connected to me. Is this possible?

I don't mind having to modify some code and rebuilding the client, but my C is rusty and some tips on where to start would be great if this is what I need to do.

Sadly, I'm pretty certain that bitcoin does not play nice as a tor hidden service since I'm pretty sure bitcoin wants IPs and tor doesn't give it any.  As laws stand now, there isn't really any reason to hide that you are running a node but now just I want to know why tor hidden services don't work properly.

If anyone runs bitcoin through a tor proxy and has the hidden services working, please let me know.
Jump to: