Kademlia running, but no kad peers / no kad boot peers

[arny]

Hello all,

I think my problem are missing kad boot peers. Any suggestion how to solve this?

Thanks in advance
Arny

Details:
MLDonkey version 2.8.7.

Kademlia seems to run, port 6749 is not firewalled, the sysinfo page says:
Donkey 6749 kademlia_port UDP

The Kad statistics page says
Kademlia is enabled Kademlia Connectivity: NOT enough online peers
and indeed there are no boot peers.

So I guess the boot peers are missing. When I input the command
kad_load contact.dat
the answer is
0 overnet peers loaded

BTW, in mlnet.log there is the line
2007/06/06 15:45:10 [OV] contact.dat loaded from http://download.overnet.org/contact.dat, added 500 peers

[spiralvoice]

overnet/contact.dat is unrelated to Kad.
Here Kad works for me:

[arny]

[arny]

Using mlnet 3.0.1 and a previously working *.ini config files, I don't get kad boot peers any longer. I still do get overnet boot peers.

The only change on my side: as mlnet had warned that it had been compiled for some different shared lib version, I recompiled it (libc-2.9.x.so ==> libc-2.10.2.so).

Donkey servers are enabled. Bittorrent and Edonkey seem to function.

I checked my masquerading router's iptable settings and used tcpdump to find out what is going on on the kad udp port.

When explicitly kad_load-ing the file http://www.nodes-dat.com/dl.php?load=nodes&trace=35090211.6111, tcpdump on my router shows that packets are sent via the ppp interface to many different hosts from the kad port. But there is no single reply.

Also I run tcpdump on another machine on the internet and specified this machine's adress in a kad_boot command. tcpdump showed that Kad packets really arrive.

Then I used hping2 on this other machine, and yes, udp packets arrived at my router on the kad port.

What the heck is going on?

- Has there been a change in the Kad protokoll and other peers don't respond any longer?

- Does my provider (O2 Germany) use deep packet inspection and block incoming kad packets?

Any ideas?

[arny]

I made some further investigations. mlnet aquires kad boot peers now. But I don't know why this didn't work in the beginning.

What I did:
- Setup another server on the internet as router (masquerading/forwarding with iptabes)
- Started an openvpn tunnel from my mlnet machine to this other server. So all internet traffic got routed via the server, which is connected to another provider.

Then mlnet started to find kad boot peers.
Good, I thought. Or rather bad. My home provider obviously blocks kad traffic.

But wrong! After terminating the openvpn tunnel, mlnet continued to find kad peers.

Strange!