From: Pascal Hambourg <pascal.mail@plouf.fr.eu.org>
To: netfilter <netfilter@lists.netfilter.org>
Subject: Re: Patch o matic
Date: Thu, 05 Oct 2006 19:11:10 +0200 [thread overview]
Message-ID: <45253CAE.8080600@plouf.fr.eu.org> (raw)
In-Reply-To: <4523FAF7.1070503@gabrix.ath.cx>
Hello,
gabrix a écrit :
> I have a debian sarge kernel 2.6 i got the patch-o-matic-ng , a kernel
> and iptables source ...
>
>> root@argo:~# ls /usr/src/
>> iptables-1.3.6 kernel-image-2.6.8_custom.1.0_i386.deb
>> kernel-source-2.6.8 patch-o-matic-ng-20040621
Aw. This is a very old and broken patch-o-matic-ng that you have.
There have ben a lot of changes since then. You may want to look at more
recent patch-o-matic-ng snapshots. Not too recent though, as some
patches have been removed from more or less recent patch-o-matic-ng
snapshots over time (some have been merged into recent kernels, some
have just been removed).
> I have placed all in the /usr/src/ dir as you can see , compiled the new
> kernel , installed by dpkg -i the new kernel,rebooted,no kernel panic
> and i can't find the new ipt modules.Some got built like NOTRACK and TTL
> but no TARPIT or psd ...
>
>> root@argo:~# lsmod | grep ipt
>> ipt_ttl 2176 0
>> ipt_NOTRACK 2304 0
>> ipt_recent 10252 2
[...]
Well, AFAIK all the listed modules, including ipt_NOTRACK, are already
included in the standard 2.6.8 kernel. I don't see ipt_TTL (TTL target)
but only ipt_ttl (TTL match). Did you apply the patch-o-matic patches to
the kernel source before compiling ? Are you running the new kernel ?
prev parent reply other threads:[~2006-10-05 17:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-04 18:18 Patch o matic gabrix
2006-10-05 7:55 ` Rob Sterenborg
2006-10-05 17:11 ` Pascal Hambourg [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=45253CAE.8080600@plouf.fr.eu.org \
--to=pascal.mail@plouf.fr.eu.org \
--cc=netfilter@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.