From: Harald Welte <laforge@netfilter.org>
To: Linux-Kernel mailing list <linux-kernel@vger.kernel.org>,
Netfilter Development Mailinglist
<netfilter-devel@lists.netfilter.org>
Subject: Re: [2.6] Nonsense-messages from iptables + co.
Date: Fri, 14 Nov 2003 21:37:37 +0100 [thread overview]
Message-ID: <20031114203737.GI6937@obroa-skai.de.gnumonks.org> (raw)
In-Reply-To: <20031114200119.GA27789@merlin.emma.line.org>
[-- Attachment #1: Type: text/plain, Size: 1068 bytes --]
On Fri, Nov 14, 2003 at 09:01:19PM +0100, Matthias Andree wrote:
> > I guess it was Rusty. The idea message is a funny way of telling you
> > that you are sending incomplete ip headers.
>
> Am I? what's with the *_limit() function called before the printk?
it's a generic network rate limiting function. It prevents the same
message from being logged and logged again (and thus flooding your
syslog).
> > Something that is not likely to occur unless you are trying to send
> > corrupt packets via raw ip sockets...
>
> Not at the times when these occurred.
there seemed to be a bug that I was unaware of, and according to other
mails in this thread it has been fixed.
--
- Harald Welte <laforge@netfilter.org> http://www.netfilter.org/
============================================================================
"Fragmentation is like classful addressing -- an interesting early
architectural error that shows how much experimentation was going
on while IP was being designed." -- Paul Vixie
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2003-11-14 20:42 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-14 13:20 Matthias Andree
2003-11-14 14:17 ` Patrick McHardy
2003-11-14 15:10 ` Harald Welte
2003-11-14 17:50 ` Valdis.Kletnieks
2003-11-14 19:08 ` Maciej Soltysiak
2003-11-14 20:01 ` Matthias Andree
2003-11-14 20:37 ` Harald Welte [this message]
2003-11-14 17:50 ` Tomas Szepe
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=20031114203737.GI6937@obroa-skai.de.gnumonks.org \
--to=laforge@netfilter.org \
--cc=linux-kernel@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®