From: Jonas Berlin <xkr47@outerspace.dyndns.org>
To: Quinton Hoole <quinton@hoole.biz>
Cc: netfilter-devel@lists.netfilter.org
Subject: Re: Mangling IP Options fields
Date: Sat, 04 Jun 2005 09:23:53 +0000 [thread overview]
Message-ID: <42A17329.3050501@outerspace.dyndns.org> (raw)
In-Reply-To: <428C8D66.3030908@hoole.biz>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Quoting Quinton Hoole on 2005-05-19 12:58 UTC:
> Hi Jonas
Hello!
> Thanks for your kind offer of help! I assume you meant it ;-) If so,
> here goes...
Sorry for late reply..
> Now I try to use patch-o-matic to apply the IPV4OPTSSTRIP patch, but get
Do you possibly mean patch-o-matic-ng (ng = next generation :) ?
If not, you should fetch the latest snapshot from:
http://ftp.netfilter.org/pub/patch-o-matic-ng/snapshot/
> the following error:
> ===================
> Do you want to apply this patch [N/y/t/f/a/r/b/w/q/?] y
> Testing patch base/IPV4OPTSSTRIP.patch...
> Warning - no help text file could be found in either
> /usr/src/linux/net/ipv4/netfilter/Config.help
> or /usr/src/linux/Documentation/Configure.help
> fgrep: /usr/src/linux/net/ipv4/netfilter/Config.in: No such file or
> directory
> Could not find place to slot in Config.in line
> TEST FAILED: patch NOT applied.
> ===================
At least it worked for me with vanilla 2.6.11.
> I installed the kernel source RPM according to the instructions in the
> FC3 (http://fedora.redhat.com/docs/release-notes/fc3/x86/), which
> places the kernel source in
The error message makes me think you have the old patch-o-matic or an
outdated patch-o-matic-ng..
> Then by executing the following I got the error above:
> [root@quinton-lap1 patch-o-matic]# KERNEL_DIR=/usr/src/linux ./runme base
FYI: You can also use
./runme IPV4OPTSSTRIP
if you want just some specific patch.
> What am I doing wrong? Should I be using a standard kernel from
> kernel.org, rather than my FC3 kernel?
I think it should work fine on both.
- --
- - xkr47
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (GNU/Linux)
iD8DBQFCoXMoxyF48ZTvn+4RAnxqAJ9SHLZMzz6tB8NLiS0i10Fk28BLAACfdyHW
3Vl5s1bLsWtkOAIAO89u0+w=
=1cBw
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2005-06-04 9:23 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-16 12:38 Mangling IP Options fields Quinton Hoole
2005-05-16 18:43 ` Jonas Berlin
2005-05-19 12:58 ` Quinton Hoole
2005-05-20 11:17 ` Amin Azez
2005-05-20 13:47 ` Quinton Hoole
2005-06-04 9:23 ` Jonas Berlin [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-05-16 12:22 Quinton Hoole
2005-05-16 12:38 ` Tobias DiPasquale
2005-05-16 12:58 ` Quinton Hoole
2005-05-16 15:58 ` Frank Abel
2005-05-16 13:18 ` Quinton Hoole
2005-05-16 13:35 ` Tobias DiPasquale
2005-05-16 14:38 ` Quinton Hoole
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=42A17329.3050501@outerspace.dyndns.org \
--to=xkr47@outerspace.dyndns.org \
--cc=netfilter-devel@lists.netfilter.org \
--cc=quinton@hoole.biz \
/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.