Hi,

Yes, sockets are creating for every new tcpdump instance, so that works
quite well. Any info on the first question? Should I even worry about it ?

On Wed, Mar 16, 2016 at 12:29 PM, Alfredo Cardigliano <[email protected]>
wrote:

> Please check under /proc/net/pf_ring/ that new socket files are created
> when starting tcpdump, to make sure tcpdump is using pf_ring.
>
> Alfredo
>
> > On 16 Mar 2016, at 12:15, m1234dm1234n1234 . <[email protected]>
> wrote:
> >
> > Downloaded PF_RING v6.3.0 and compiled module with no problems.
> > Then went to /userland/lib and /userland/libpcap and compiled those with
> prefix /usr/local/pfring, all went well.
> > After that, i configured tcpdump with same prefix, and when I started to
> compile, a bunch of messages started to appear :
> >
> > "gcc -O2 -DHAVE_CONFIG_H  -I./missing  -D_U_="__attribute__((unused))"
> -DHAVE_PF_RING -I. -I./../libpcap  -I./missing -I../libpcap -c
> ./addrtoname.c
> > gcc -O2 -DHAVE_CONFIG_H  -I./missing  -D_U_="__attribute__((unused))"
> -DHAVE_PF_RING -I. -I./../libpcap  -I./missing -I../libpcap -c ./af.c
> > gcc -O2 -DHAVE_CONFIG_H  -I./missing  -D_U_="__attribute__((unused))"
> -DHAVE_PF_RING -I. -I./../libpcap  -I./missing -I../libpcap -c ./checksum.c
> > gcc -O2 -DHAVE_CONFIG_H  -I./missing  -D_U_="__attribute__((unused))"
> -DHAVE_PF_RING -I. -I./../libpcap  -I./missing -I../libpcap -c ./cpack.c
> > gcc -O2 -DHAVE_CONFIG_H  -I./missing  -D_U_="__attribute__((unused))"
> -DHAVE_PF_RING -I. -I./../libpcap  -I./missing -I../libpcap -c ./gmpls.c
> > gcc -O2 -DHAVE_CONFIG_H  -I./missing  -D_U_="__attribute__((unused))"
> -DHAVE_PF_RING -I. -I./../libpcap  -I./missing -I../libpcap -c ./oui.c
> > gcc -O2 -DHAVE_CONFIG_H  -I./missing  -D_U_="__attribute__((unused))"
> -DHAVE_PF_RING -I. -I./../libpcap  -I./missing -I../libpcap -c ./gmt2local.c
> > gcc -O2 -DHAVE_CONFIG_H  -I./missing  -D_U_="__attribute__((unused))"
> -DHAVE_PF_RING -I. -I./../libpcap  -I./missing -I../libpcap -c ./ipproto.c
> > gcc -O2 -DHAVE_CONFIG_H  -I./missing  -D_U_="__attribute__((unused))"
> -DHAVE_PF_RING -I. -I./../libpcap  -I./missing -I../libpcap -c ./nlpid.c
> > gcc -O2 -DHAVE_CONFIG_H  -I./missing  -D_U_="__attribute__((unused))"
> -DHAVE_PF_RING -I. -I./../libpcap  -I./missing -I../libpcap -c ./l2vpn.c
> > gcc -O2 -DHAVE_CONFIG_H  -I./missing  -D_U_="__attribute__((unused))"
> -DHAVE_PF_RING -I. -I./../libpcap  -I./missing -I../libpcap -c ./machdep.c
> > gcc -O2 -DHAVE_CONFIG_H  -I./missing  -D_U_="__attribute__((unused))"
> -DHAVE_PF_RING -I. -I./../libpcap  -I./missing -I../libpcap -c
> ./parsenfsfh.c
> > gcc -O2 -DHAVE_CONFIG_H  -I./missing  -D_U_="__attribute__((unused))"
> -DHAVE_PF_RING -I. -I./../libpcap  -I./missing -I../libpcap -c
> ./print-802_11.c
> > gcc -O2 -DHAVE_CONFIG_H  -I./missing  -D_U_="__attribute__((unused))"
> -DHAVE_PF_RING -I. -I./../libpcap  -I./missing -I../libpcap -c
> ./print-ap1394.c
> > gcc -O2 -DHAVE_CONFIG_H  -I./missing  -D_U_="__attribute__((unused))"
> -DHAVE_PF_RING -I. -I./../libpcap  -I./missing -I../libpcap -c ./print-ah.c
> > gcc -O2 -DHAVE_CONFIG_H  -I./missing  -D_U_="__attribute__((unused))"
> -DHAVE_PF_RING -I. -I./../libpcap  -I./missing -I../libpcap -c
> ./print-arcnet.c
> > gcc -O2 -DHAVE_CONFIG_H  -I./missing  -D_U_="__attribute__((unused))"
> -DHAVE_PF_RING -I. -I./../libpcap  -I./missing -I../libpcap -c
> ./print-aodv.c
> > gcc -O2 -DHAVE_CONFIG_H  -I./missing  -D_U_="__attribute__((unused))"
> -DHAVE_PF_RING -I. -I./../libpcap  -I./missing -I../libpcap -c ./print-arp.c
> > "
> >
> > This is not the whole list, but you get the point.
> >
> > TCPDump does finish compiling without errors, and it does start, but how
> can I check that it uses PF_ring enabled libpcap?
> >
> > Is there some crucial step i missed?
> > _______________________________________________
> > Ntop-misc mailing list
> > [email protected]
> > http://listgateway.unipi.it/mailman/listinfo/ntop-misc
>
>
> _______________________________________________
> Ntop-misc mailing list
> [email protected]
> http://listgateway.unipi.it/mailman/listinfo/ntop-misc
>
_______________________________________________
Ntop-misc mailing list
[email protected]
http://listgateway.unipi.it/mailman/listinfo/ntop-misc

Reply via email to