Linux Netfilter discussions
 help / color / mirror / Atom feed
From: "Filip Sneppe (Cronos)" <filip.sneppe@cronos.be>
To: Kevin Smith <ksmith@perfht.com>
Cc: netfilter@lists.netfilter.org
Subject: Re: Cuseeme-Nat
Date: 18 Apr 2003 02:15:45 +0200	[thread overview]
Message-ID: <1050624945.1900.10.camel@exile> (raw)
In-Reply-To: <NGBBLGFEALDADHNDAAFFMEHJDJAA.ksmith@perfht.com>

Hi Kevin,

On Thu, 2003-04-17 at 15:20, Kevin Smith wrote:

>Well I upgraded my Kernel to 2.4.20 and patched cuseeme-nat and the
>other required file to it (Patch-o-matic says verifies this). But I
>still get the same problem with some reflectors, where they read the
>machine IP and refuse to let me in. 
>
>I did however get curious error while compiling: 
...
>ip_nat_helper.c: In function `ip_nat_resize_packet':
>ip_nat_helper.c:87: warning: unused variable `data' <-------- This one
>
>
>Might this cause the patch to malfunction? If so, since Im new to all

No, this warning is not really an issue. I think there's already
a small patch in patch-o-matic to fix this compile warning.

>this patching/compiling stuff, can someone point me in the right
>direction to correct this? Ive been compiling for about a week now so
>Id liekto NOT have to do that again, but If I must. 
>
Can you recompile the CuSeeMe module with debugging enabled ?
there's no need for a full kernel recompile.

Just edit net/ipv4/netfilter/ip_nat_cuseeme.c in the kernel tree
and change the lines:

#if 0
#define DEBUGP printk
#else
#define DEBUGP(format, args...)
#endif

into this (it's really just a one-line change):

#if 1
#define DEBUGP printk
#else
#define DEBUGP(format, args...)
#endif

then do (from your kernel source tree):

rm net/ipv4/netfilter/ip_nat_cuseeme.o
make SUBDIRS=net/ipv4/netfilter modules
make modules_install

then you can do 'rmmod ip_nat_cuseeme' and 'modprobe ip_nat_cuseeme'
again.

Debugging messages should be logged depending on your
syslog configuration. Most likely they will show
up in /var/log/messages. Can you copy-paste the
debugging messages ?

Thanks in advance,
Filip



  reply	other threads:[~2003-04-18  0:15 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-04-17 13:20 Cuseeme-Nat Kevin Smith
2003-04-18  0:15 ` Filip Sneppe (Cronos) [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-04-25 13:08 Cuseeme-nat Kevin Smith
2003-04-15 15:59 cuseeme-nat Kevin Smith
2003-04-15 20:46 ` cuseeme-nat Filip Sneppe (Cronos)
2003-04-09  3:43 Cuseeme-Nat Kevin Smith

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=1050624945.1900.10.camel@exile \
    --to=filip.sneppe@cronos.be \
    --cc=ksmith@perfht.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