search

JoshuaKissoon / Kademlia

A Java implementation of Kademlia Routing Protocol and DHT
MIT License
193 stars 73 forks source link

Won't work inside NAT #13

Open mesudip opened 6 years ago

mesudip commented 6 years ago

The node connection setup protocol is as follows: --> Client sends it's local ip:port information --> Server reads that information and updates the DHT

Thus the connection ot that client will always fail if it's inside a subnet. The ip information that is kept is so bad that my local computer sends it's loopback address i.e. "127.0.0.1:port" to the server

JoshuaKissoon commented 6 years ago

Hey @mesudip, Did you do any code updates to solve this issue? If you did please send me a pull. If not let me know and I'll try to sort it out ASAP.

I've actually only used this DHT locally. I'd be happy to add this functionality.

sivanagarajumolabant commented 5 years ago

The node connection setup protocol is as follows: --> Client sends it's local ip:port information --> Server reads that information and updates the DHT

Thus the connection ot that client will always fail if it's inside a subnet. The ip information that is kept is so bad that my local computer sends it's loopback address i.e. "127.0.0.1:port" to the server

can you please tell me which file i have to run first iam intresting to work on this project

schneidersoft commented 4 years ago

google brought me here... why have peer 1 send its own contact information to peer2? peer2 will know what the ip of peer1 is as soon as peer1 connects... probably still won't help you with nat traversal, because if peer1 is behind a nat peer3 won't be able to get through even if it got working contact information from peer2...