On Tue, Jun 06, 2006 at 09:40:28PM +0300, <Constantine Kousoulos>:
~> 'mydesktop$ host mynotebook' yields a wrong ip.
~> 'mynotebook$ host mydesktop' yields a wrong ip.
Yea, but I wanted to know what the wrong ip is, f.e. if the right ip is
1.2.3.4 but you get 4.3.2.1, then it is an endianness bug.
There is another possibility: previously registered hostnames have been
saved in the andna_cache but the RSA keys have been lost, thus when you try to
register the new one you are put in the queue and you have to wait three days
before you go on top of the queue (it isn't necessary that the daemons are up
for the three days).
In other words:
- mydesktop registered its hname
- mynotebook registered its hname
- you closed the daemons and the andna caches were saved
- for some reasons the keyrings have been lost
- you restart the daemons which load the andna caches
- when mydesktop try to register the hname with the _new_ RSA key, it gets
queued
- the same happens for mynotebook
- when you resolve 'mydesktop' you get the old IP, which was associated
previously
- the same happens for mynotebook
If it is this case then
{
you have to just try to rm /usr/share/netsukuku/*
and restart the daemons.
If this fails, then
{
I don't know what it might be and we need more debug, thus
you can proceed to try the CVS version.
If it doesn't happen for the CVS version, then
{
it is a bug of the 0.0.7b
}
else
{
it is a generic bug.
This is the best case, because we can track it down
better.
}
}
}
Regards
--
:wq!
"I don't know nothing" The One Who reached the Thinking Matter '.'
[ Alpt --- Freaknet Medialab ]
[ GPG Key ID 441CF0EE ]
[ Key fingerprint = 8B02 26E8 831A 7BB9 81A9 5277 BFF8 037E 441C F0EE ]
_______________________________________________
Netsukuku mailing list
[email protected]
http://lists.dyne.org/mailman/listinfo/netsukuku
