Linux Netfilter discussions
 help / color / mirror / Atom feed
From: Harald Welte <laforge@netfilter.org>
To: Krishna Prasanth P <krishnap@teneoris.com>
Cc: netfilter@lists.netfilter.org
Subject: Re: compilation problem with cuseeme patch.
Date: Sun, 15 Feb 2004 16:28:32 +0100	[thread overview]
Message-ID: <20040215152832.GM15567@sunbeam.de.gnumonks.org> (raw)
In-Reply-To: <1076587638.1004.49.camel@krishnap>

[-- Attachment #1: Type: text/plain, Size: 1021 bytes --]

On Thu, Feb 12, 2004 at 05:36:50PM +0530, Krishna Prasanth P wrote:
> Hi!!
>  I'm trying to use cuseeme patch with netfilter and downloaded the patch
> from the cvs repository.

a) Which kernel version are you using
b) did you correctly use the 'runme' program or did you apply the patch
   manually?

> 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.

net/ipv4/netfilter/ip_nat_helper.c includes this function, at least in
all kernels released for at least one year.

> -prasanth

-- 
- Harald Welte <laforge@netfilter.org>             http://www.netfilter.org/
============================================================================
  "Fragmentation is like classful addressing -- an interesting early
   architectural error that shows how much experimentation was going
   on while IP was being designed."                    -- Paul Vixie

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

      parent reply	other threads:[~2004-02-15 15:28 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
2004-02-15 15:28 ` Harald Welte [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=20040215152832.GM15567@sunbeam.de.gnumonks.org \
    --to=laforge@netfilter.org \
    --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