From: Valdis.Kletnieks@vt.edu
To: Harald Welte <laforge@gnumonks.org>
Cc: 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 12:50:30 -0500 [thread overview]
Message-ID: <200311141750.hAEHoUI2023152@turing-police.cc.vt.edu> (raw)
In-Reply-To: Your message of "Fri, 14 Nov 2003 16:10:04 +0100." <20031114151004.GE2395@obroa-skai.de.gnumonks.org>
[-- Attachment #1: Type: text/plain, Size: 1015 bytes --]
On Fri, 14 Nov 2003 16:10:04 +0100, Harald Welte said:
> > "ipt_hook: happy cracking."
>
> I guess it was Rusty. The idea message is a funny way of telling you
> that you are sending incomplete ip headers. Something that is not
> likely to occur unless you are trying to send corrupt packets via raw ip
> sockets...
Actually, once I found the message, and saw the context, it was actually
clear and self-explanatory. It was actually the ipfilter code's fault
that it got generated in any context other than "trying to send an intentionall
busticated packet"...
> There are people who do actually have fun developing linux code. And
> Rusty has a peculiar sense of humor... for further reference see the
> comments like 'furniture shopping' throughout the netfilter/iptables
> source code. I sometimes wish I had the same humor like he has.
find arch/sparc* -name '*.[ch]'| xargs grep -i penguin
and then read through the files that finds (trap.c is particularly fun).
Somebody was having fun porting. ;)
[-- Attachment #2: Type: application/pgp-signature, Size: 226 bytes --]
next prev parent reply other threads:[~2003-11-14 17:51 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 [this message]
2003-11-14 19:08 ` Maciej Soltysiak
2003-11-14 20:01 ` Matthias Andree
2003-11-14 20:37 ` Harald Welte
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=200311141750.hAEHoUI2023152@turing-police.cc.vt.edu \
--to=valdis.kletnieks@vt.edu \
--cc=laforge@gnumonks.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®