Linux Netfilter discussions
 help / color / mirror / Atom feed
From: Martin Josefsson <gandalf@wlug.westbo.se>
To: Roy Sigurd Karlsbakk <roy@karlsbakk.net>
Cc: Netfilter mailinglist <netfilter@lists.netfilter.org>
Subject: Re: PPTP+NAT+MASQ anyone?
Date: 09 Dec 2002 15:42:25 +0100	[thread overview]
Message-ID: <1039444945.28074.43.camel@tux> (raw)
In-Reply-To: <200212091512.10109.roy@karlsbakk.net>

On Mon, 2002-12-09 at 15:12, Roy Sigurd Karlsbakk wrote:

> > And patch-o-matic from cvs works with at least 2.4.19 (2.4.18 and .20
> > should work aswell)
> 
> then what's this?
> 
> In file included from 
> /usr/src/linux/include/linux/netfilter_ipv4/ip_conntrack.h:64,
>                  from extensions/libipt_conntrack.c:12:
> /usr/src/linux/include/linux/netfilter_ipv4/ip_conntrack_talk.h:6:2: #error 
> Only in kernel.
> In file included from 
> /usr/src/linux/include/linux/netfilter_ipv4/ip_conntrack.h:65,
>                  from extensions/libipt_conntrack.c:12:
> /usr/src/linux/include/linux/netfilter_ipv4/ip_conntrack_rsh.h:16:2: #error 
> Only in kernel.
> make: *** [extensions/libipt_conntrack_sh.o] Error 1

You said "the only one I've managed to patch-o-matic" which means the
only one you've managed to patch. What you are saying now is that you
indeed did manage to patch your kernel. Please use more accurate wording
in reports like these.

And you are NOT using patch-o-matic from cvs, I know this because these
problems were fixed some time ago (and doublechecking the files I see
that they were indeed fixed). The error you are seeing is _impossible_
with patch-o-matic from cvs (the #error lines doesn't even exist)

-- 
/Martin

Never argue with an idiot. They drag you down to their level, then beat
you with experience.


  reply	other threads:[~2002-12-09 14:42 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-12-09 11:26 PPTP+NAT+MASQ anyone? Roy Sigurd Karlsbakk
2002-12-09 12:25 ` Martin Josefsson
2002-12-09 14:12   ` Roy Sigurd Karlsbakk
2002-12-09 14:42     ` Martin Josefsson [this message]
2002-12-09 14:58       ` Roy Sigurd Karlsbakk
2002-12-09 15:17         ` Martin Josefsson
2002-12-11 11:49           ` Roy Sigurd Karlsbakk
2002-12-11 13:29             ` Rob Sterenborg
2002-12-11 14:03             ` Martin Josefsson
2002-12-11 14:14               ` Roy Sigurd Karlsbakk
2002-12-11 14:26                 ` Martin Josefsson
2002-12-11 14:31                   ` Roy Sigurd Karlsbakk
2002-12-11 15:35                   ` Roy Sigurd Karlsbakk
2002-12-11 15:40                     ` Martin Josefsson
2002-12-11 15:56                       ` Roy Sigurd Karlsbakk
2002-12-11 16:01                       ` Roy Sigurd Karlsbakk
2002-12-11 16:41                         ` Martin Josefsson
2002-12-11 16:54                           ` Roy Sigurd Karlsbakk
2002-12-23 13:15                             ` [REPOST] " Roy Sigurd Karlsbakk
2002-12-23 17:02                               ` Ilguiz Latypov
2002-12-26 23:09                               ` Diego Sarasua
2002-12-26 23:10                               ` [REPOST] PPTP+NAT+MASQ anyone? (!!!!!!!!!!!!!!!!!! SORRY BAD LINK !!!!!!!!!!!!!!!!!) Diego Sarasua
2002-12-11 16:09                       ` PPTP+NAT+MASQ anyone? Roy Sigurd Karlsbakk
  -- strict thread matches above, loose matches on Subject: below --
2002-12-09 11:57 Rob Sterenborg

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=1039444945.28074.43.camel@tux \
    --to=gandalf@wlug.westbo.se \
    --cc=netfilter@lists.netfilter.org \
    --cc=roy@karlsbakk.net \
    /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