Quote from: linuxforyou on August 24, 2014, 03:20:07 AM

Yes, RelayNodeClient.jar is nice.

Add node option can be checked with=>

Code:

host public.us-east.relay.mattcorallo.com

which gives IP=>
public.us-east.relay.mattcorallo.com has address 162.243.69.180

then,

Code:

netstat -lant | grep 162.243.69.180

Should give established connection between local IP and 162.243.69.180

To check actual traffic between local node and 162.243.69.180 tcpdump can be used.

Code:

tcpdump -neivv -i MyNetworkInterface host 162.243.69.180

Change MyNetworkInterface respectively with your network interface.

0 packet captured means something is wrong, else should be fine.

Cheers,

Thanks for that info. The reason I didn't think a direct connection from bitcoind to the Relay Network worked for me is because after I did the "addnode" I checked bitcoind with the "getaddednodeinfo" command. I got the following output:

Code:

[
{
"addednode" : "public.us-east.relay.mattcorallo.com",
"connected" : false,
"addresses" : [
{
"address" : "162.243.69.180:8335",
"connected" : "false"
}
]
}
]

Also, the number of bitcoin peers from "getinfo" stayed the same. Thus I concluded that something was wrong and I went down the RelayNodeClient path. I would prefer to connect bitcoind directly to the Relay Network and save the RAM that RelayNodeClient uses, but its not a big deal (30 MB of RAM, I believe) either way. Has anyone else had success connecting bitcoind to the Relay Network without RelayNodeClient?