[OLSR-users] Re: cpu load?

[Sven-Ola Tuecke]

Wolfgang,

I have followed your discussion on the funkfeuer mailing list so far. Can 
you please do a quick look at the memory requirements of the kernel when 
pushing up the conntrack value?

BG: We run some devices here in berlin with only 8 Mb RAM ("WAP54G/v2) - 
which is small enough to experience slower reactions due to lack of 
jffs2-buffers. 32k additional kernel mem should be no showstopper, but much 
more will be critical here)

TIA Sven-Ola

""Wolfgang 'Dreamguard' Nagele"" <(spam-protected)> schrieb im 
Newsbeitrag news:(spam-protected)
> hi,
>
>> Thanks for helping. If you think that there's anything strange in the
>> code, please do feel free to discuss this with me any time you like. It
>> wouldn't be the first time that we find a bug in the link quality code!
> seems that we figured out what the problem was. in fact it hasn't to do
> anything with olsr it self. but it could be useful for all the users out
> there.
>
> the problem was that ip_conntrack limit was far to little for the routers.
> in our case it was 1024. you can check this with 'cat
> /proc/sys/net/ipv4/ip_conntrack_max'. if you don't need nat on your boxes
> or something that relies on this just pull it out of the modules. if you
> need - give it a higher value with something like "echo "50000" >
> /proc/sys/net/ipv4/ip_conntrack_max" and everything should go fine.
>
> hope that helps.
> bye
>
>
> _______________________________________________
> olsr-users mailing list
> (spam-protected)
> https://www.olsr.org/mailman/listinfo/olsr-users