--- Begin Message ---
"Defined" in what sense?
First of all, I want to define a header, with a magic byte maybe, a time
stamp, length of the whole packet and so on. Something which wraps my
actual data and which libpcap can recognize or rather expect as data
which can be read from my device
--- Begin Message ---
Hello everyone, another question that I have is which DLT-type I should
use for my libpcap-module. Since Im writing a module which acquires data
from a kernel module, which in turn has no IP-based packages at all. I
have to define my very own data-type from the base onwards
--- Begin Message ---
Maybe this should be also mentioned within the libpcap module howto?
https://www.tcpdump.org/libpcap-module-HOWTO.html
BR Christian
Make sure that libpcap.a includes pcap-kpnode.o, by making sure that
pcap-kpnode.c is in the list of source modules to be compiled and inc
--- Begin Message ---
Make sure that libpcap.a includes pcap-kpnode.o, by making sure that
pcap-kpnode.c is in the list of source modules to be compiled and included in
libpcap.
For Makefile.in, that means adding it to
MODULE_C_SRC = @MODULE_C_SRC@
after @MODULE_C_SRC@ so you have
--- Begin Message ---
configure:6075: checking for pcap_loop
configure:6075: gcc -o conftest -g -O2 conftest.c -L/usr/local/lib
-Wl,-rpath,/usr/local/lib -lpcap >&5
/usr/bin/ld: /usr/local/lib/libpcap.so: undefined reference to `scsimon_create'
/usr/bin/ld: /usr/local/lib/libpcap.so: undefined
--- Begin Message ---
Am 15.08.22 um 20:09 schrieb Guy Harris:
What are the contents of config.log?
Ohhh f**. Ok sorry it's moday afternoon
here it comes:
This file contains any messages produced by compilers while
running configure, to aid debugging if configure makes a mistake.
It was crea
--- Begin Message ---
Then I opened the tcpdump.zip archive
(.zip? Not .tar.gz? The current releases from
https://www.tcpdump.org/index.html#latest-releases
are provided in .tar.gz form, as are all the other release in
https://www.tcpdump.org/release/
Gzipped tarballs are pr
--- Begin Message ---
I pick up this thread of mine again from 7th march of this year
(wireshark extension for a Kernel Module (like Usbmon) ) enhanced with
a configure issue, which was discussed lot of times ( tcpdump configure
script doesn't correctly handle static builds ). But Im not sure,
--- Begin Message ---
forget to evoke autoconf again, now it's within the library and I have
to do the next step.
Thank you so far
BR Christian
> ___
> tcpdump-workers mailing list
> tcpdump-workers@lists.tcpdump.org
> https://lists.sandelman.ca/mailman
--- Begin Message ---
Hello Guy, thank you for your help.
>> further down:
>> #ifdef PCAP_SUPPORT_KPNODE
>> || strstr(device, "kpnode") != NULL
>> #endif
> That's presumably in pcap_lookupnet(); if so, that's the correct way to add
> kpnode there.
>
> (I need to change that to use a bett
--- Begin Message ---
hello out there, I created a kernel probe module and I want to watch the
outputs of that module with pcap/Wireshark or tcpdump... Just like
usbmon. My prefered tool is dumpcap. So I defined a char device in the
dev-directory /dev/kpnode from which the pcap interface can read t
11 matches
Mail list logo