Mailing List Archive: NTop: Misc

PF_RING

Index | Next | Previous | View Threaded

neil-johnson at uiowa

Sep 19, 2005, 2:16 PM

Post #1 of 9 (2949 views)
Permalink

PF_RING

Can someone explain to me how to patch PF_RING into the FC4 (2.6.12)
kernel?

The instructions are not clear to me and when I run mkpatch.sh I either
get an empty patch file or one that the patch program won't let me use.

Thanks.

--
Neil Johnson
Network Communications Engineer
Information Technology Services
University of Iowa
(319) 384-0938 Phone
(319) 335-2951 Fax

_______________________________________________
Ntop-misc mailing list
Ntop-misc [at] listgateway
http://listgateway.unipi.it/mailman/listinfo/ntop-misc

bdoctor at ps-ax

Jan 12, 2006, 8:26 AM

Post #2 of 9 (2706 views)
Permalink

Re: PF_RING [In reply to]

PF_RING is a kernel patch and you are required to patch the kernel and build
a new one.

-brad

> Hello All,
>
>
> I recently downloaded PR_RING and went through the install. One thing I
> noticed is that after modifying the mkpatch.sh script, it looks as though it
> goes out, grabs the kernel version, downloads and patches the src for you,
> dumping it off in kernel-version-ring3. It looks like you can just go in
> and compile this src and not have to patch anything, correct? From the docs
> it looks as though you have to go ahead and patch the kernel src. Which is
> correct?
>
>
> Thanks.
> _______________________________________________
> Ntop-misc mailing list
> Ntop-misc [at] listgateway
> http://listgateway.unipi.it/mailman/listinfo/ntop-misc
>

--
Brad Doctor, CISSP
_______________________________________________
Ntop-misc mailing list
Ntop-misc [at] listgateway
http://listgateway.unipi.it/mailman/listinfo/ntop-misc

JHally at epnet

Jan 12, 2006, 8:37 AM

Post #3 of 9 (2742 views)
Permalink

RE: PF_RING [In reply to]

Yes, but after running the mkpatch script I'm left with
linux-2.6.15-1-686-smp-ring3 in the ./workspace directory. I went ahead and
ran make menuconfig and the pf_ring selection is there, and it seems to
compile ok.

I'm assuming that this is indeed a patched kernel source as it seems to
compile and run ok (minus the panic in my other email). I'm curious if this
is the case and it's just not updated in the docs.

Is that the case?

>From the output below in steps 3,4,5,6 I'm lead to believe that the kernel
source is indeed patched and goes ahead and creates the patch file for later
use maybe?

Mkpatch.sh output:

Untarring Linux sources (read-write tree) in
/usr/local/src/PF_RING/PF_RING/workspace/linux-2.6.15-1-686-smp-ring3
Patching Linux sources ...
1. Install additional file include/linux/ring.h with definitions
for packet ring.
done
2. Install the ring sources under the kernel tree.
Installing kernel ring sources in
linux-2.6.15-1-686-smp-ring3/net/ring ... done
3. Patch net/core/dev.c ...
Patch #1 (define ring_handler)
Patch #2 (modify function netif_rx and netif_receive_skb)
Patch #3 (modify dev_queue_xmit, found in PATCH-3-to-dev.c)
... done
4. Patching file net/Makefile ... done
5. Copy net/ring/Kconfig to linux-2.6.15-1-686-smp-ring3/net/ring/Kconfig
done
6. Patching file net/Kconfig ... done
rmdir: `linux-2.6.15-1-686-smp-ring3/linux-2.6.15': Directory not empty
diff --unified --recursive --new-file linux-2.6.15
linux-2.6.15-1-686-smp-ring3 > linux-2.6.15-1-686-smp-ring3.patch
Making Linux patch file. This could take some time, please wait ... done
Your patch file is now in
/usr/local/src/PF_RING/PF_RING/workspace/linux-2.6.15-1-686-smp-ring3.patch.
gz

-----Original Message-----
From: ntop-misc-bounces [at] listgateway
[mailto:ntop-misc-bounces [at] listgateway] On Behalf Of Brad Doctor
Sent: Thursday, January 12, 2006 11:27 AM
To: ntop-misc [at] listgateway
Subject: Re: [Ntop-misc] PF_RING

PF_RING is a kernel patch and you are required to patch the kernel and build
a new one.

-brad

> Hello All,
>
>
> I recently downloaded PR_RING and went through the install. One thing I
> noticed is that after modifying the mkpatch.sh script, it looks as though
it
> goes out, grabs the kernel version, downloads and patches the src for you,
> dumping it off in kernel-version-ring3. It looks like you can just go in
> and compile this src and not have to patch anything, correct? From the
docs
> it looks as though you have to go ahead and patch the kernel src. Which
is
> correct?
>
>
> Thanks.
> _______________________________________________
> Ntop-misc mailing list
> Ntop-misc [at] listgateway
> http://listgateway.unipi.it/mailman/listinfo/ntop-misc
>

--
Brad Doctor, CISSP
_______________________________________________
Ntop-misc mailing list
Ntop-misc [at] listgateway
http://listgateway.unipi.it/mailman/listinfo/ntop-misc
_______________________________________________
Ntop-misc mailing list
Ntop-misc [at] listgateway
http://listgateway.unipi.it/mailman/listinfo/ntop-misc

bdoctor at ps-ax

Jan 12, 2006, 9:40 AM

Post #4 of 9 (2733 views)
Permalink

Re: PF_RING [In reply to]

The process does create a patch file, which is really the ultimate goal of
running mkpatch.sh. In your case that file is here (from your email):

/usr/local/src/PF_RING/PF_RING/workspace/linux-2.6.15-1-686-smp-ring3.patch.gz

So what you could then do is take this patch and apply it to your kernel
source. Or if you are packaging a kernel via RPM you can specify this as a
Patch and apply it automatically. Definitely not required to build from this
location though.

Hope this works for you! If not, let us know and we will get you through it.
-brad

> Yes, but after running the mkpatch script I'm left with
> linux-2.6.15-1-686-smp-ring3 in the ./workspace directory. I went ahead and
> ran make menuconfig and the pf_ring selection is there, and it seems to
> compile ok.
>
> I'm assuming that this is indeed a patched kernel source as it seems to
> compile and run ok (minus the panic in my other email). I'm curious if this
> is the case and it's just not updated in the docs.
>
> Is that the case?
>
> >From the output below in steps 3,4,5,6 I'm lead to believe that the kernel
> source is indeed patched and goes ahead and creates the patch file for later
> use maybe?
>
> Mkpatch.sh output:
>
> Untarring Linux sources (read-write tree) in
> /usr/local/src/PF_RING/PF_RING/workspace/linux-2.6.15-1-686-smp-ring3
> Patching Linux sources ...
> 1. Install additional file include/linux/ring.h with definitions
> for packet ring.
> done
> 2. Install the ring sources under the kernel tree.
> Installing kernel ring sources in
> linux-2.6.15-1-686-smp-ring3/net/ring ... done
> 3. Patch net/core/dev.c ...
> Patch #1 (define ring_handler)
> Patch #2 (modify function netif_rx and netif_receive_skb)
> Patch #3 (modify dev_queue_xmit, found in PATCH-3-to-dev.c)
> ... done
> 4. Patching file net/Makefile ... done
> 5. Copy net/ring/Kconfig to linux-2.6.15-1-686-smp-ring3/net/ring/Kconfig
> done
> 6. Patching file net/Kconfig ... done
> rmdir: `linux-2.6.15-1-686-smp-ring3/linux-2.6.15': Directory not empty
> diff --unified --recursive --new-file linux-2.6.15
> linux-2.6.15-1-686-smp-ring3 > linux-2.6.15-1-686-smp-ring3.patch
> Making Linux patch file. This could take some time, please wait ... done
> Your patch file is now in
> /usr/local/src/PF_RING/PF_RING/workspace/linux-2.6.15-1-686-smp-ring3.patch.
> gz
>
>
>
>
>
> -----Original Message-----
> From: ntop-misc-bounces [at] listgateway
> [mailto:ntop-misc-bounces [at] listgateway] On Behalf Of Brad Doctor
> Sent: Thursday, January 12, 2006 11:27 AM
> To: ntop-misc [at] listgateway
> Subject: Re: [Ntop-misc] PF_RING
>
> PF_RING is a kernel patch and you are required to patch the kernel and build
> a new one.
>
> -brad
>
> > Hello All,
> >
> >
> > I recently downloaded PR_RING and went through the install. One thing I
> > noticed is that after modifying the mkpatch.sh script, it looks as though
> it
> > goes out, grabs the kernel version, downloads and patches the src for you,
> > dumping it off in kernel-version-ring3. It looks like you can just go in
> > and compile this src and not have to patch anything, correct? From the
> docs
> > it looks as though you have to go ahead and patch the kernel src. Which
> is
> > correct?
> >
> >
> > Thanks.
> > _______________________________________________
> > Ntop-misc mailing list
> > Ntop-misc [at] listgateway
> > http://listgateway.unipi.it/mailman/listinfo/ntop-misc
> >
>
> --
> Brad Doctor, CISSP
> _______________________________________________
> Ntop-misc mailing list
> Ntop-misc [at] listgateway
> http://listgateway.unipi.it/mailman/listinfo/ntop-misc
> _______________________________________________
> Ntop-misc mailing list
> Ntop-misc [at] listgateway
> http://listgateway.unipi.it/mailman/listinfo/ntop-misc
>

--
Brad Doctor, CISSP
_______________________________________________
Ntop-misc mailing list
Ntop-misc [at] listgateway
http://listgateway.unipi.it/mailman/listinfo/ntop-misc

neil-johnson at uiowa

Jan 12, 2006, 10:17 AM

Post #5 of 9 (2698 views)
Permalink

RE: PF_RING [In reply to]

Here's what I documented.

PF_RING on FC4 ?
- Install FC4

- Install FC4 updates

- Download running FC4 kernel SOURCE rpm from your favorite Fedora
mirror (unname -r will give you version)

- install with rpm -Uvh kernel-<version>.src.rpm

- Prep kernel (add redhat patches):
cd /usr/src/redhat/SPECS
rpmbuild -bp --target $(arch) kernel-2.6.spec

- Move kernel to /usr/src
cd /usr/src/redhat/BUILD/kernel-<version>
mv linux-<version> /usr/src
cd /usr/src
ln -s ./linux-<version> linux
cd /usr/src/linux

- Download PF_RING (CVS Checkout)
edit mkpatch.sh so version equals generic kernel version from above
run mkpatch.sh
move patch file to /usr/src
run zcat <patchfile> | patch --dry-run -p0 to test
run zcat <patchfile> | patch -p0
cd linux
make menuconfig
Enbable PF_RING under Networking options.
make bzImage && make modules_install
make install (to install kernel in /boot)
edit /etc/modprobe.conf add "ring" to list to autoload module.
reboot and pray !

- Build new libpcap
Get version 0.8.1 of libpcap (google and look for one on source
forge).
Expand in dir <...>/PF_RING/userland/
copy files listed in <..>/PF_RING/userland/libpcap.0.8.1-ring/README
to libpcap-0.8.1
copy ring.h file from PF_RING/kernel...../ to /usr/include/linux
run ./configure and make to build libpcap.0.8.1
go into pcount and compile and run to check.

copy libpcap.a to /usr/lib and pcap.h /usr/include.

Compile nProbe.

Data on the way ?
########################################################
--
Neil Johnson
Network Engineering Group
Information Technology Services
University of Iowa
(319) 384-0938 (Desk)
(319) 330-2235 (Cell)
(319) 341-6838 (Pager)
GPG Public Key available upon request.

-----Original Message-----
From: ntop-misc-bounces [at] listgateway
[mailto:ntop-misc-bounces [at] listgateway] On Behalf Of Brad Doctor
Sent: Thursday, January 12, 2006 11:40 AM
To: ntop-misc [at] listgateway
Subject: Re: [Ntop-misc] PF_RING

The process does create a patch file, which is really the ultimate goal
of
running mkpatch.sh. In your case that file is here (from your email):

/usr/local/src/PF_RING/PF_RING/workspace/linux-2.6.15-1-686-smp-ring3.pa
tch.gz

So what you could then do is take this patch and apply it to your kernel
source. Or if you are packaging a kernel via RPM you can specify this
as a
Patch and apply it automatically. Definitely not required to build from
this
location though.

Hope this works for you! If not, let us know and we will get you
through it.
-brad

> Yes, but after running the mkpatch script I'm left with
> linux-2.6.15-1-686-smp-ring3 in the ./workspace directory. I went
ahead and
> ran make menuconfig and the pf_ring selection is there, and it seems
to
> compile ok.
>
> I'm assuming that this is indeed a patched kernel source as it seems
to
> compile and run ok (minus the panic in my other email). I'm curious
if this
> is the case and it's just not updated in the docs.
>
> Is that the case?
>
> >From the output below in steps 3,4,5,6 I'm lead to believe that the
kernel
> source is indeed patched and goes ahead and creates the patch file for
later
> use maybe?
>
> Mkpatch.sh output:
>
> Untarring Linux sources (read-write tree) in
> /usr/local/src/PF_RING/PF_RING/workspace/linux-2.6.15-1-686-smp-ring3
> Patching Linux sources ...
> 1. Install additional file include/linux/ring.h with definitions
> for packet ring.
> done
> 2. Install the ring sources under the kernel tree.
> Installing kernel ring sources in
> linux-2.6.15-1-686-smp-ring3/net/ring ... done
> 3. Patch net/core/dev.c ...
> Patch #1 (define ring_handler)
> Patch #2 (modify function netif_rx and netif_receive_skb)
> Patch #3 (modify dev_queue_xmit, found in PATCH-3-to-dev.c)
> ... done
> 4. Patching file net/Makefile ... done
> 5. Copy net/ring/Kconfig to
linux-2.6.15-1-686-smp-ring3/net/ring/Kconfig
> done
> 6. Patching file net/Kconfig ... done
> rmdir: `linux-2.6.15-1-686-smp-ring3/linux-2.6.15': Directory not
empty
> diff --unified --recursive --new-file linux-2.6.15
> linux-2.6.15-1-686-smp-ring3 > linux-2.6.15-1-686-smp-ring3.patch
> Making Linux patch file. This could take some time, please wait ...
done
> Your patch file is now in
>
/usr/local/src/PF_RING/PF_RING/workspace/linux-2.6.15-1-686-smp-ring3.pa
tch.
> gz
>
>
>
>
>
> -----Original Message-----
> From: ntop-misc-bounces [at] listgateway
> [mailto:ntop-misc-bounces [at] listgateway] On Behalf Of Brad
Doctor
> Sent: Thursday, January 12, 2006 11:27 AM
> To: ntop-misc [at] listgateway
> Subject: Re: [Ntop-misc] PF_RING
>
> PF_RING is a kernel patch and you are required to patch the kernel and
build
> a new one.
>
> -brad
>
> > Hello All,
> >
> >
> > I recently downloaded PR_RING and went through the install. One
thing I
> > noticed is that after modifying the mkpatch.sh script, it looks as
though
> it
> > goes out, grabs the kernel version, downloads and patches the src
for you,
> > dumping it off in kernel-version-ring3. It looks like you can just
go in
> > and compile this src and not have to patch anything, correct? From
the
> docs
> > it looks as though you have to go ahead and patch the kernel src.
Which
> is
> > correct?
> >
> >
> > Thanks.
> > _______________________________________________
> > Ntop-misc mailing list
> > Ntop-misc [at] listgateway
> > http://listgateway.unipi.it/mailman/listinfo/ntop-misc
> >
>
> --
> Brad Doctor, CISSP
> _______________________________________________
> Ntop-misc mailing list
> Ntop-misc [at] listgateway
> http://listgateway.unipi.it/mailman/listinfo/ntop-misc
> _______________________________________________
> Ntop-misc mailing list
> Ntop-misc [at] listgateway
> http://listgateway.unipi.it/mailman/listinfo/ntop-misc
>

--
Brad Doctor, CISSP
_______________________________________________
Ntop-misc mailing list
Ntop-misc [at] listgateway
http://listgateway.unipi.it/mailman/listinfo/ntop-misc
_______________________________________________
Ntop-misc mailing list
Ntop-misc [at] listgateway
http://listgateway.unipi.it/mailman/listinfo/ntop-misc

JHally at epnet

Jan 12, 2006, 2:16 PM

Post #6 of 9 (2767 views)
Permalink

RE: PF_RING [In reply to]

Great! I made it work a little differently though. Will send my notes when
I can clean them up

Thanks!

-----Original Message-----
From: ntop-misc-bounces [at] listgateway
[mailto:ntop-misc-bounces [at] listgateway] On Behalf Of Johnson, Neil M
Sent: Thursday, January 12, 2006 1:17 PM
To: ntop-misc [at] listgateway
Subject: RE: [Ntop-misc] PF_RING

Here's what I documented.

PF_RING on FC4 ?
- Install FC4

- Install FC4 updates

- Download running FC4 kernel SOURCE rpm from your favorite Fedora
mirror (unname -r will give you version)

- install with rpm -Uvh kernel-<version>.src.rpm

- Prep kernel (add redhat patches):
cd /usr/src/redhat/SPECS
rpmbuild -bp --target $(arch) kernel-2.6.spec

- Move kernel to /usr/src
cd /usr/src/redhat/BUILD/kernel-<version>
mv linux-<version> /usr/src
cd /usr/src
ln -s ./linux-<version> linux
cd /usr/src/linux

- Download PF_RING (CVS Checkout)
edit mkpatch.sh so version equals generic kernel version from above
run mkpatch.sh
move patch file to /usr/src
run zcat <patchfile> | patch --dry-run -p0 to test
run zcat <patchfile> | patch -p0
cd linux
make menuconfig
Enbable PF_RING under Networking options.
make bzImage && make modules_install
make install (to install kernel in /boot)
edit /etc/modprobe.conf add "ring" to list to autoload module.
reboot and pray !

- Build new libpcap
Get version 0.8.1 of libpcap (google and look for one on source
forge).
Expand in dir <...>/PF_RING/userland/
copy files listed in <..>/PF_RING/userland/libpcap.0.8.1-ring/README
to libpcap-0.8.1
copy ring.h file from PF_RING/kernel...../ to /usr/include/linux
run ./configure and make to build libpcap.0.8.1
go into pcount and compile and run to check.

copy libpcap.a to /usr/lib and pcap.h /usr/include.

Compile nProbe.

Data on the way ?
########################################################
--
Neil Johnson
Network Engineering Group
Information Technology Services
University of Iowa
(319) 384-0938 (Desk)
(319) 330-2235 (Cell)
(319) 341-6838 (Pager)
GPG Public Key available upon request.

-----Original Message-----
From: ntop-misc-bounces [at] listgateway
[mailto:ntop-misc-bounces [at] listgateway] On Behalf Of Brad Doctor
Sent: Thursday, January 12, 2006 11:40 AM
To: ntop-misc [at] listgateway
Subject: Re: [Ntop-misc] PF_RING

The process does create a patch file, which is really the ultimate goal
of
running mkpatch.sh. In your case that file is here (from your email):

/usr/local/src/PF_RING/PF_RING/workspace/linux-2.6.15-1-686-smp-ring3.pa
tch.gz

So what you could then do is take this patch and apply it to your kernel
source. Or if you are packaging a kernel via RPM you can specify this
as a
Patch and apply it automatically. Definitely not required to build from
this
location though.

Hope this works for you! If not, let us know and we will get you
through it.
-brad

> Yes, but after running the mkpatch script I'm left with
> linux-2.6.15-1-686-smp-ring3 in the ./workspace directory. I went
ahead and
> ran make menuconfig and the pf_ring selection is there, and it seems
to
> compile ok.
>
> I'm assuming that this is indeed a patched kernel source as it seems
to
> compile and run ok (minus the panic in my other email). I'm curious
if this
> is the case and it's just not updated in the docs.
>
> Is that the case?
>
> >From the output below in steps 3,4,5,6 I'm lead to believe that the
kernel
> source is indeed patched and goes ahead and creates the patch file for
later
> use maybe?
>
> Mkpatch.sh output:
>
> Untarring Linux sources (read-write tree) in
> /usr/local/src/PF_RING/PF_RING/workspace/linux-2.6.15-1-686-smp-ring3
> Patching Linux sources ...
> 1. Install additional file include/linux/ring.h with definitions
> for packet ring.
> done
> 2. Install the ring sources under the kernel tree.
> Installing kernel ring sources in
> linux-2.6.15-1-686-smp-ring3/net/ring ... done
> 3. Patch net/core/dev.c ...
> Patch #1 (define ring_handler)
> Patch #2 (modify function netif_rx and netif_receive_skb)
> Patch #3 (modify dev_queue_xmit, found in PATCH-3-to-dev.c)
> ... done
> 4. Patching file net/Makefile ... done
> 5. Copy net/ring/Kconfig to
linux-2.6.15-1-686-smp-ring3/net/ring/Kconfig
> done
> 6. Patching file net/Kconfig ... done
> rmdir: `linux-2.6.15-1-686-smp-ring3/linux-2.6.15': Directory not
empty
> diff --unified --recursive --new-file linux-2.6.15
> linux-2.6.15-1-686-smp-ring3 > linux-2.6.15-1-686-smp-ring3.patch
> Making Linux patch file. This could take some time, please wait ...
done
> Your patch file is now in
>
/usr/local/src/PF_RING/PF_RING/workspace/linux-2.6.15-1-686-smp-ring3.pa
tch.
> gz
>
>
>
>
>
> -----Original Message-----
> From: ntop-misc-bounces [at] listgateway
> [mailto:ntop-misc-bounces [at] listgateway] On Behalf Of Brad
Doctor
> Sent: Thursday, January 12, 2006 11:27 AM
> To: ntop-misc [at] listgateway
> Subject: Re: [Ntop-misc] PF_RING
>
> PF_RING is a kernel patch and you are required to patch the kernel and
build
> a new one.
>
> -brad
>
> > Hello All,
> >
> >
> > I recently downloaded PR_RING and went through the install. One
thing I
> > noticed is that after modifying the mkpatch.sh script, it looks as
though
> it
> > goes out, grabs the kernel version, downloads and patches the src
for you,
> > dumping it off in kernel-version-ring3. It looks like you can just
go in
> > and compile this src and not have to patch anything, correct? From
the
> docs
> > it looks as though you have to go ahead and patch the kernel src.
Which
> is
> > correct?
> >
> >
> > Thanks.
> > _______________________________________________
> > Ntop-misc mailing list
> > Ntop-misc [at] listgateway
> > http://listgateway.unipi.it/mailman/listinfo/ntop-misc
> >
>
> --
> Brad Doctor, CISSP
> _______________________________________________
> Ntop-misc mailing list
> Ntop-misc [at] listgateway
> http://listgateway.unipi.it/mailman/listinfo/ntop-misc
> _______________________________________________
> Ntop-misc mailing list
> Ntop-misc [at] listgateway
> http://listgateway.unipi.it/mailman/listinfo/ntop-misc
>

--
Brad Doctor, CISSP
_______________________________________________
Ntop-misc mailing list
Ntop-misc [at] listgateway
http://listgateway.unipi.it/mailman/listinfo/ntop-misc
_______________________________________________
Ntop-misc mailing list
Ntop-misc [at] listgateway
http://listgateway.unipi.it/mailman/listinfo/ntop-misc
_______________________________________________
Ntop-misc mailing list
Ntop-misc [at] listgateway
http://listgateway.unipi.it/mailman/listinfo/ntop-misc

bdoctor at ps-ax

Nov 17, 2006, 8:21 PM

Post #7 of 9 (2230 views)
Permalink

Re: PF_RING [In reply to]

Wally,

The patch also affects core/dev.c and is necessary. At this point, the entire
kernel needs to be recompiled.

-brad

> Hi,
>
> I'm currently playing with the idea of creating two PF_RING packages
> for the Gentoo Linux distribution. One for the kernel patch and one
> for libpcap.
>
> I'm hoping to have the PF_RING kernel patches included as a standard
> part of Gentoo's kernel, but for now I need to either...
>
> 1. Create a package that patches the users current kernel sources or..
> 2. Create a package that builds a PF_RING module that can be
> modprob'ed into the current running kernel.
>
> I'm focusing my attention on the 2.6.x kernel for now.
>
> Ultimately what will decide if I go with option 1 or 2 is whether, a
> PF_RING module can be built using 'make modules' on the patched
> sources or if a full make is required first.
>
> I've been testing on the 2.6.17 kernel and what I've found is that if I...
>
> 1. create a copy of my current sources
> 2. run make
> 3. patch the sources
> 4. add CONFIG_RING=m to .config
> 5. run 'make modules' I get this...
>
> CHK include/linux/version.h
> SPLIT include/linux/autoconf.h -> include/config/*
> CC [M] net/ring/ring_packet.o
> LD [M] net/ring/ring.o
> Building modules, stage 2.
> MODPOST
> WARNING: "set_skb_ring_handler" [net/ring/ring.ko] undefined!
> WARNING: "set_buffer_ring_handler" [net/ring/ring.ko] undefined!
> WARNING: "get_buffer_ring_handler" [net/ring/ring.ko] undefined!
> CC net/ring/ring.mod.o
> LD [M] net/ring/ring.ko
>
> If I do 1-4 then...
>
> 5. 'make'
>
> It compiles cleanly. My inexperienced guess is this from the fact that
> 'net/core/dev.o' also needs to be recompiled.
>
> So does the fact that 'net/core/dev.o' needs to be recompiled
> completely prohibit compiling a module that can be modprob'ed into the
> current running kernel?
>
> Wally
> _______________________________________________
> Ntop-misc mailing list
> Ntop-misc [at] listgateway
> http://listgateway.unipi.it/mailman/listinfo/ntop-misc
>

--
Brad Doctor, CISSP
_______________________________________________
Ntop-misc mailing list
Ntop-misc [at] listgateway
http://listgateway.unipi.it/mailman/listinfo/ntop-misc

dreamgirl314 at gmail

May 9, 2011, 5:51 PM

Post #8 of 9 (942 views)
Permalink

Re: PF_RING [In reply to]

Hi Luca,

I am using an application which uses libpcap-0.9.8, hence I think I am
getting the errors, since I could only find the latest versions of PF_RING
which use libpcap-1.0.0 or greater. Could you please help me find PF_RING
which uses libpcap-0.9.8 since I am using Justniffer which requires this
version.

Regards
Archana

deri at ntop

May 10, 2011, 12:41 AM

Post #9 of 9 (941 views)
Permalink

Re: PF_RING [In reply to]

Archana
0.98 is a few years old. If you want to use that one use an old vrsion of PF_RING. On the other hand I don't see what's the problem using 1.x as it has the same api as 0.98\

Luca

On May 10, 2011, at 2:51 AM, Archana N wrote:

> Hi Luca,
>
> I am using an application which uses libpcap-0.9.8, hence I think I am getting the errors, since I could only find the latest versions of PF_RING which use libpcap-1.0.0 or greater. Could you please help me find PF_RING which uses libpcap-0.9.8 since I am using Justniffer which requires this version.
>
> Regards
> Archana
> _______________________________________________
> Ntop-misc mailing list
> Ntop-misc [at] listgateway
> http://listgateway.unipi.it/mailman/listinfo/ntop-misc

---
If you can not measure it, you can not improve it - Lord Kelvin

_______________________________________________
Ntop-misc mailing list
Ntop-misc [at] listgateway
http://listgateway.unipi.it/mailman/listinfo/ntop-misc

Index | Next | Previous | View Threaded

Interested in having your list archived? Contact Gossamer Threads