From: Filip Sneppe <filip.sneppe@uptime.be>
To: Krishna Prasanth P <krishnap@teneoris.com>
Cc: netfilter@lists.netfilter.org
Subject: Re: compilation problem with cuseeme patch.
Date: 15 Feb 2004 14:41:38 +0100 [thread overview]
Message-ID: <1076852498.12832.2.camel@exile> (raw)
In-Reply-To: <1076587638.1004.49.camel@krishnap>
On Thu, 2004-02-12 at 13:06, Krishna Prasanth P wrote:
> Hi!!
> I'm trying to use cuseeme patch with netfilter and downloaded the patch
> from the cvs repository.
> While building the kernel with the new patch, i'm not able to do
> linking. The reason is the cuseeme(ip_nat_cuseeme.c) is using function
> ip_nat_mangle_udp_packet() function which is not defined.
>
> Please let me know, if i'm missing some other things while adding the
> patch.
>
Hi Krishna,
You will need at least kernel version 2.4.20 + the "03_2.4.21.patch"
from patch-o-matic/submitted/ for this to compile and work correctly.
ip_nat_mangle_udp_packet entered the kernel somewhere between 2.4.20
and 2.4.21 and is needed by the cuseeme nat module.
regards,
Filip
next prev parent reply other threads:[~2004-02-15 13:41 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-12 12:06 compilation problem with cuseeme patch Krishna Prasanth P
2004-02-15 13:41 ` Filip Sneppe [this message]
2004-02-15 15:28 ` Harald Welte
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=1076852498.12832.2.camel@exile \
--to=filip.sneppe@uptime.be \
--cc=krishnap@teneoris.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox