OpenWrt Forum Archive

Topic: Value of the nlbufsiz parameter of the ipt_ULOG module

The content of this topic has been archived on 8 Apr 2018. There are no obvious gaps in this topic, but there may still be some posts missing at the end.

Would some kind soul tell me how to determine this?

I'd like to run ulogd on White Russion/RC5, and I'm getting these errors when I do:

ipulog_read == -1! ipulog_errno == 7, errno = 132

From /usr/src/linux-2.6.12/include/asm-mips/errno.h:

#define ENOBUFS         132     /* No buffer space available */

I realize the OpenWrt firmware runs 2.4.30 and not 2.6.12, but I guessed that these numbers remained the same.

And I found this with google:

https://lists.gnumonks.org/pipermail/ul … 00308.html

which seems to address my problem too (though the errno is different, the ENOBUFS is the same)

So rather than just going with the defaults from ulogd.conf, I thought I would adjust them to fit the OpenWrt firmware (in case it's different than a stock kernel) or at least figure out what these numbers are for the OpenWrt firmware before adjusting /proc/sys/net/core/rmem_*

Thanks for any replies.

John

For anyone else who might be interested in this issue (and tho this might have been the hard way to answer the question) I checked out the sources for whiterussion with svn and built the firmware myself, thus getting a copy of the kernel sources.  From there, I checked ipt_ULOG.c and found the answer to be 4096.

Sorry for asking half a year later: 4096 was the answer, but did it solve the problem? If I set rmem=4096 in ulogd.conf, I get a TON of these errno=132 messages, a lot more than with the standard settings. My router hangs after a few minutes or hours an I can only unplug the power cable.

The discussion might have continued from here.