can't join network

[GoogleCodeExporter]

What steps will reproduce the problem?
1. using as reference the kaddemo wiki, create the first node(bootstrap 
node)
2. add a normal node to the network using random port. After connecting 
close the node
3. add again a normal node with random port like in step 2. This node can't 
connect the network

What is the expected output? What do you see instead?

this is the output for the node can't connect to the network

1035 --- Sending rpc Bootstrap to 81.202.191.212:5100 connection_id = 
652471297
-- rpc_id = 438081405
(1035) message for id 652471297 arrived
1035 --- Response arrived for KademliaService::Bootstrap -- 438081405 -- 
RTT: 88.217 ms, duration: 5609 ms
(1035) Accepted connections: 0. Msgs Sent: 1. Msgs Recv 1

What version of the product are you using? On what operating system?
using revision 416 
windows xp sp2

Please provide any additional information below.

Original issue reported on code.google.com by vt.o...@gmail.com on 19 May 2010 at 5:17

[GoogleCodeExporter]

Hi there,

Thanks for the report. We'll have a look tomorrow morning and update you on the 
matter.

Dan

Original comment by dan.schm...@gmail.com on 19 May 2010 at 7:00

• Changed state: Accepted

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

Hi again,

I've spent some time today trying to reproduce the fault in several platforms 
and it
doesn't appear. Let me tell you what I did exactly on Windows Xp to see if you 
can
see anything different from your process.

1. Opened two cmd windows
2. Compiled Debug version of kaddemo_static.
3. From build\Win_MinGW\Debug ran the following command (with my ip details):
   bin\kaddemo_static_d.exe -p 5000 --externalip 192.168.1.121 --externalport 5000
--noconsole --nodeinfopath .
4. In the other window, I typed: mkdir KnodeInfo5001. Then, copy .kadconfig
KnodeInfo5001. And finally, bin\kaddemo_static_d.exe -p 5001 -k 
KnodeInfo5001/.kadconfig
5. From this last terminal I did a ping to the other node: pingnode ##### (with 
the
id printed on the other terminal).
6. Ping came back ok.
7. Typed exit to terminate successfully the second node.
8. Did again bin\kaddemo_static_d.exe -p 5001 -k KnodeInfo5001/.kadconfig
9. Pinged the other node successfully again.

From the out put of the node that you send, it doesn't seem like the node is not
bootstrapping. You would instead see something like this:

(5001) UDT connect to 192.168.1.121:5000 -- Connection setup failure: 
connection time out
(5001) UDT connect to 192.168.1.121:5000 -- Connection setup failure: 
connection time out
(5001) UDT connect to 192.168.1.121:5000 -- Connection setup failure: 
connection time out
(5001) UDT connect to 192.168.1.121:5000 -- Connection setup failure: 
connection time out
(5001) Transport::ConnectToSend failed to connect to remote port 5000
5001 --- Failed to connect to send rpc Bootstrap to 192.168.1.121:5000 with id 
232877979
5001Request 232877979 times out.  Connection ID: 0
Node failed to join the network.
(5001) Accepted connections: 0. Msgs Sent: 0. Msgs Recv 0

So, some questions. Are you using the mingw version as well? Are you sure the
.kadconfig is in the right place and has the correct information? Are you sure 
the BS
node is running?

Let's see if we can figure this one out ;)

Original comment by dan.schm...@gmail.com on 20 May 2010 at 2:36

[GoogleCodeExporter]

Hi dan,

you have to use random port or use different ports

first do this
bin\kaddemo_static_d.exe -p 5001 -k KnodeInfo5001/.kadconfig
connect and close the application and
bin\kaddemo_static_d.exe -p 5002 -k KnodeInfo5001/.kadconfig

the trick is using different ports

Original comment by vt.o...@gmail.com on 20 May 2010 at 3:16

[GoogleCodeExporter]

Right. I see what you see now. The problem is in our NAT detection service. The
bootstrap node thinks that the other node is still up, and it's trying to 
contact it
to do the second stage of the NAT detection... This might require some 
re-factoring.
I'll keep you posted.

Good pick-up, man. Thanks for reporting it. 

Original comment by dan.schm...@gmail.com on 20 May 2010 at 3:26

[GoogleCodeExporter]

So good luck with this one :) 

Original comment by vt.o...@gmail.com on 20 May 2010 at 4:16

[GoogleCodeExporter]

Hey guys!

Long time no write. Been a bit busy with other projects. However, I think the 
issue's finally fixed. The problem reported for bootstrapping should be fixed.

If you have some time, give it a go. It's gone on the svn just now, revision 
456. There's a test in testknode.cc that verifies the behaviour.

Dan

Original comment by dan.schm...@gmail.com on 23 Jun 2010 at 6:47

• Changed state: Fixed