From: Pablo Neira <pablo@eurodev.net>
To: Harald Welte <laforge@netfilter.org>
Cc: Netfilter Development <netfilter-devel@lists.netfilter.org>,
Abraham van der Merwe <abz@frogfoot.net>
Subject: Re: ULOG / netlink errors
Date: Thu, 16 Dec 2004 15:42:07 +0000 [thread overview]
Message-ID: <41C1ACCF.6040604@eurodev.net> (raw)
In-Reply-To: <20041216134127.GI10165@sunbeam.de.gnumonks.org>
Harald Welte wrote:
>On Sun, Nov 28, 2004 at 09:50:04PM +0100, Pablo Neira wrote:
>
>
>>Pablo Neira wrote:
>>
>>
>>
>>>this is ok, it's always a good idea to reduce the probability of an
>>>overflow. But I think that you'll have problems anyway with traffers
>>>rates bigger than ~20 Mbits/s.
>>>
>>>
>>well, this is true in ip_queue, don't know in ipt_ULOG, it depends on
>>three/four parameters.
>>
>>
>
>just to let you know: there are people doing ULOG based acounting on >=
>100MBit. So it's not as bad as you think it is ;)
>
I love netlink sockets, but loving someone/something implies knowing
their limitations as well :)
I think that it depends on the settings, let me see what happen with an
insane iptables rule like: iptables -I INPUT -j ULOG
>[no, I'm not advertising the use of ulog for accounting. That's not
>what it was menat for].
>
I do also use ULOG(tm) to log packets, Since I do my hamster pet looks
happier ;)
--
Pablo
prev parent reply other threads:[~2004-12-16 15:42 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-28 11:37 ULOG / netlink errors Abraham van der Merwe
2004-11-28 20:37 ` Pablo Neira
2004-11-28 20:50 ` Pablo Neira
2004-12-16 13:41 ` Harald Welte
2004-12-16 15:42 ` Pablo Neira [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=41C1ACCF.6040604@eurodev.net \
--to=pablo@eurodev.net \
--cc=abz@frogfoot.net \
--cc=laforge@netfilter.org \
--cc=netfilter-devel@lists.netfilter.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.