Hey,
I found out that the batman-exp daemon goes crazy when its internal life-time variable overflows. This will happen after 49 days, 17 hours, 2 minutes, and 48 seconds (which corresponds to 2^32 milliseconds). Unfortunately, its behavior afterwards can be anything between hanging around and doing nothing and an endless loop of sending packets. The problem is fixed with revision 972.
If you are running batman-exp I strongly suggest to update.
ciao, axel
Hi Axel On Thu, Jan 31, 2008 at 06:04:55PM +0100, Axel Neumann wrote:
I found out that the batman-exp daemon goes crazy when its internal life-time variable overflows. This will happen after 49 days, 17 hours, 2 minutes, and 48 seconds (which corresponds to 2^32 milliseconds). Unfortunately, its behavior afterwards can be anything between hanging around and doing nothing and an endless loop of sending packets.
or just work normally for another ~2 weeks, and then going crazy after some 60 days of uptime ;-)
The problem is fixed with revision 972.
If you are running batman-exp I strongly suggest to update.
if i find time on sunday, i'll give it a try
cheers
--Jan
b.a.t.m.a.n@lists.open-mesh.org
-
Axel Neumann -
Jan Hetges