Hi jan,
just sitting here with lui and discussing your problem... batman usually terminates itself when it finds a firewall blocking its own packets. Seems like your firewall starts to drop packets beause the maximum number of possible connection tracking has been exceeded. You can find more information about that (and also how to increase the limit) here: http://www.fli4l.de/fileadmin/doc/deutsch/html/fli4l-3.1.3/node9.html
to see the currently tracked connection look at cat /proc/net/ip_conntrack
ciao, lui, axel
On Donnerstag 06 Dezember 2007, Jan Hetges wrote:
Hi All after two weeks uptime bmxd_rv804 just died! and not only that one, but on a neighbouring node (~5 days uptime) as well. So i restarted them, and about 26hrs later, they are both dead again. So i enabled Lui's watchout4batman, maybe i see at least, which one dies first. Only unnormal in the log: user.warn kernel: nf_conntrack: table full, dropping packet. any ideas?
cheers
--Jan
p.s. both boxes run kamikaze 7.07 i386