Cuseeme-Nat

Cuseeme-Nat

[Kevin Smith]

 I was wondering how well the cuseeme-nat patch works in the field. Just
 looking for pros/cons  and gotchas.
 Also is there a Minimum kernel version you need to use these patches? mine
 is RH 7.2 2.4.7-10. I have been considering upgrading it since I am
probably
 in the Linux dark ages kernelwise. Since I never did one Im also looking
for some good newbie documentation on that.

ty Kev

cuseeme-nat

[Kevin Smith]

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

Greetings Listers, 

Im curious about any info, good or bad about this patch. Mostly how well it
works. 


Kev

[-- Attachment #2: winmail.dat --]
[-- Type: application/ms-tnef, Size: 1412 bytes --]

Re: cuseeme-nat

[Filip Sneppe (Cronos)]

On Tue, 2003-04-15 at 17:59, Kevin Smith wrote:
>
>Greetings Listers, 
>
>Im curious about any info, good or bad about this patch. Mostly how
>well it works. 
>
>

Hi Kevin,

You've already contacted me in private mail about this, and asked
this list the same question twice.

How about giving it a try for yourself and reporting back to the author
and the netfilter-devel list (or possibly this list) if things don't
work ? 

The patch is supposed to work on x86 architectures and I don't know
of anyone (including people who beta tested) experiencing problems.
There is an issue on some architectures - this is noted in the
patch desciption, but I haven't gotten around to looking at that
yet (and fixing it).

Regards,
Filip

Cuseeme-Nat

[Kevin Smith]

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

Listers, 


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: 
::
 gcc -D__KERNEL__ -I/usr/src/linux-2.4.20/include -Wall -Wstrict-prototypes
-
Wno-trigraphs -O2 -fno-strict-aliasing -fno-common -fomit-frame-pointer -pip
e -mpreferred-stack-boundary=2 -march=i586   -nostdinc -iwithprefix
include -DKBUILD_BASENAME=ip_nat_core  -c -o ip_nat_core.o ip_nat_core.c
gcc -D__KERNEL__ -I/usr/src/linux-2.4.20/include -Wall -Wstrict-prototypes -
Wno-trigraphs -O2 -fno-strict-aliasing -fno-common -fomit-frame-pointer -pip
e -mpreferred-stack-boundary=2 -march=i586   -nostdinc -iwithprefix
include -DKBUILD_BASENAME=ip_nat_helper  -c -o ip_nat_helper.o
ip_nat_helper.c
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 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. 

Thanks,

Kev

[-- Attachment #2: winmail.dat --]
[-- Type: application/ms-tnef, Size: 2232 bytes --]

Re: Cuseeme-Nat

[Filip Sneppe (Cronos)]

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

Cuseeme-nat

[Kevin Smith]

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

I as wondering is there were any PATH requirements for the cuseeme-nat
module?
I have patched it to the kernel but cant get it to compile. 
Kev

[-- Attachment #2: winmail.dat --]
[-- Type: application/ms-tnef, Size: 1456 bytes --]