Hi, all!
I observed a, at least for me, strange behaviour of amuled concerning kad.
I use amuled/amuleweb/amulcmd on Debian Sarge w/o any gui. All three magic ports are forwarded to the PC and I have a high id.
After starting amuled I can see the usual lines in the log file. The first tells me, that 0 (sometimes more) kad contacts have been read (don't know the exact phrasing in English, as I'm using German version). Some minutes later I am connected to kad, but firewalled. Another few minutes later kad is OK. So far, so good.
But, after some time, again the message in the log file, that I am connected to kad (firewalled) and after a few minutes, that kad is OK. No message that kad was disconnected.
I get those disconnect messages, too, once in a while, so I know, that they do exist.
After some time, I get to the point that the web server tells me "Kad: off". If I take a look in the log file, the last line with the string "kad" in it, says "connected to Kad(firewalled)" and is 16 hours old. No mention of "disconnected" before or after.
Even if I manually do a "connect kad" in amulecmd (which is answered with "successfull"), nothing changes. Kad is still off and stays that way, until I restart amuled. Then the connection is OK again for some hours.
I can, of course, see the same with amulegui under WinXP. It makes no difference at all. Only mentioning this for the sake of completeness.
Any ideas about that? What about the settings concerning the learning of new servers from other clients? Do these have an effect on Kademlia?