Re: How (and why) to use the Relay Network

[norgan]

I've downloaded the exe client and am running it with "D:\Temp\relay\relaynetworkclient.exe public.au.relay.mattcorallo.com 127.0.0.1 8333" but I just get the following:

Closing bitcoind socket, failed to connect() (10049: Unknown error)
Closing relay socket, failed to connect() (10049: Unknown error)
Closing bitcoind socket, failed to connect() (10049: Unknown error)
Closing relay socket, failed to connect() (10049: Unknown error)
Closing bitcoind socket, failed to connect() (10049: Unknown error)
Closing relay socket, failed to connect() (10049: Unknown error)
Closing bitcoind socket, failed to connect() (10049: Unknown error)
Closing relay socket, failed to connect() (10049: Unknown error)
Closing bitcoind socket, failed to connect() (10049: Unknown error)
Closing relay socket, failed to connect() (10049: Unknown error)
Closing bitcoind socket, failed to connect() (10049: Unknown error)
Closing relay socket, failed to connect() (10049: Unknown error)
Closing bitcoind socket, failed to connect() (10049: Unknown error)

What am I doing wrong?

I'm getting this too with the windows exe client on Win7.  It eventually killed my TCP/IP stack, all programs were getting TCP/IP errors until I killed the relay client.

Going back to the python version here.

M

It was a broken build, have you tried the latest? Also try disabling ipv6

[mdude77]

I've downloaded the exe client and am running it with "D:\Temp\relay\relaynetworkclient.exe public.au.relay.mattcorallo.com 127.0.0.1 8333" but I just get the following:

Closing bitcoind socket, failed to connect() (10049: Unknown error)
Closing relay socket, failed to connect() (10049: Unknown error)
Closing bitcoind socket, failed to connect() (10049: Unknown error)
Closing relay socket, failed to connect() (10049: Unknown error)
Closing bitcoind socket, failed to connect() (10049: Unknown error)
Closing relay socket, failed to connect() (10049: Unknown error)
Closing bitcoind socket, failed to connect() (10049: Unknown error)
Closing relay socket, failed to connect() (10049: Unknown error)
Closing bitcoind socket, failed to connect() (10049: Unknown error)
Closing relay socket, failed to connect() (10049: Unknown error)
Closing bitcoind socket, failed to connect() (10049: Unknown error)
Closing relay socket, failed to connect() (10049: Unknown error)
Closing bitcoind socket, failed to connect() (10049: Unknown error)

What am I doing wrong?

I'm getting this too with the windows exe client on Win7.  It eventually killed my TCP/IP stack, all programs were getting TCP/IP errors until I killed the relay client.

Going back to the python version here.

M

It was a broken build, have you tried the latest? Also try disabling ipv6

I got it from github, I assume it's the latest.

M

[mdude77]

Nevermind.  I forgot my bitcoin port isn't default, so it was pounding 8333 and there wasn't anything there to respond.



M

[simdude]

I love this concept. I start running the windows version on my windows based p2pool. If you get around to building a exe for relay enabled p2pool i would love to test it out.

[-ck]

Having issues with the c++ client receiving anything in the last day connecting to us-west without any other changes. Tried restarting and getting repeated

Code:

Closing relay socket, failed to read message header (104: Connection reset by peer)

[IYFTech]

Having issues with the c++ client receiving anything in the last day connecting to us-west without any other changes. Tried restarting and getting repeated

Code:

Closing relay socket, failed to read message header (104: Connection reset by peer)

The eu server is working well - have you tried that one? 

[Matt Corallo]

Having issues with the c++ client receiving anything in the last day connecting to us-west without any other changes. Tried restarting and getting repeated

Code:

Closing relay socket, failed to read message header (104: Connection reset by peer)

Hmm, I dont see anything in my logs...Is it working now and/or can you pm me the IP you're connecting from?

[-ck]

Having issues with the c++ client receiving anything in the last day connecting to us-west without any other changes. Tried restarting and getting repeated

Code:

Closing relay socket, failed to read message header (104: Connection reset by peer)

Hmm, I dont see anything in my logs...Is it working now and/or can you pm me the IP you're connecting from?

It's still there. I've PMed you where from.

EDIT: It just started working again. Beats me 

[Matt Corallo]

EDIT: It just started working again. Beats me 

I was fuxing with it.

[simdude]

I am still getting the Closing relay socket, failed to read message header (10054: Unknown error)

[Matt Corallo]

I am still getting the Closing relay socket, failed to read message header (10054: Unknown error)

What node are you connecting to? All nodes seem to be working from here. If you are connect multiple times from the same external IP, this is expected behavior as having multiple connections will decrease your relay time by a huge margin because, in my tests, the most important thing is packet loss requiring extra RTTs for TCP retransmits (if you're behind ISP level NAT I think I can just flip the switch on IPv6 for most of the nodes, just need to actually test the clients to make sure they wont flip).

[simdude]

Hello,

     public.us-east

[amaclin]

public.us-east

us-east and us-west work right now as I see
(us-west had some troubles in the past)

[Matt Corallo]

public.us-east

I dont see any issues there, can you PM me the IP you're connecting from?

[norgan]

Seeing issues on the sg node again. Had to change to west-us

[amaclin]

Seeing issues on the sg node again. Had to change to west-us

us-west does not work from my side right now
I use us-east

[Matt Corallo]

Ugh, yes, there appear to have been some issues that went unnoticed over the past week or so, should be all good now and I'm monitoring for further hiccups until I can go in and debug a bit more.

[norgan]

Ugh, yes, there appear to have been some issues that went unnoticed over the past week or so, should be all good now and I'm monitoring for further hiccups until I can go in and debug a bit more.

au/sg working now.

Would there be any negative impact of running two relays to two different relay servers? so if one went down the other would still relay blocks...

[Matt Corallo]

Ugh, yes, there appear to have been some issues that went unnoticed over the past week or so, should be all good now and I'm monitoring for further hiccups until I can go in and debug a bit more.

au/sg working now.

Would there be any negative impact of running two relays to two different relay servers? so if one went down the other would still relay blocks...

Seems several servers were all hit with the same bug at nearly the same time. Still need to look into it, but for this case, it appears that would not have helped. Still, no, that would probably not be a negative.

[spin]

Under the C++ folder I see a make script for 5 components (including a windows client).  I am happy with how the client is used and managed to get it going.

Can you perhaps share how the other components could be used to build a relay network? I am not really proficient at reading c++.

My guesses:
relaynetworkproxy -> Connects two relay nodes (both on port 8336).
relaynetworkterminator -> Seems to provide the 8334 and 8335 tx and block only feeds?
relaynetworkoutbound -> Connects a bitcoind and a something on port 8334?
relaynetworkserver -> connects to a trusted bitcoind? Also serves clients?  Also connects to something local on port 8334? I kept getting connection refused to the local bitcoind when I ran it.


Happy to assist with a readme on your github if needs be.