Re: [tcpdump-workers] Libpcap - pcapfindalldevs

Ok. Thanks a lot for the explanation. Regards. Johan Mazel 2009/9/4 Guy Harris > > On Sep 4, 2009, at 8:45 AM, Johan Mazel wrote: > > I wrote a short piece of code in C to show the problem. >> >> My code is the following one: >> *#include >> #include &

Re: [tcpdump-workers] Libpcap - pcapfindalldevs

Sorry for the second mail Correction : My machine runs on Ubuntu 9.04. My libpcap version is 1.0.0-1. Johan Mazel 2009/9/4 Johan Mazel > I wrote a short piece of code in C to show the problem. > > My code is the following one: > *#include > #include > > int main(){

Re: [tcpdump-workers] Libpcap - pcapfindalldevs

;show copying" and "show warranty" for details. This GDB was configured as "x86_64-linux-gnu". If this is a bug in Libpcap, how can I submit it ? Regards. Johan 2009/2/2 Guy Harris > > On Feb 2, 2009, at 5:39 AM, Johan Mazel wrote: > > My problem is tha

Re: [tcpdump-workers] Problem with generation of Pcap traces for

Ok. Thanks a lot, both of you, for all the informations provided. Johan - This is the tcpdump-workers list. Visit https://cod.sandelman.ca/ to unsubscribe.

Re: [tcpdump-workers] Problem with generation of Pcap traces for

Hello (802.11 isn't a version of Ethernet.) > > If your 802.11 device supplies "fake Ethernet" headers, you can aggregate > its packets with Ethernet packets; if it supplies 802.11 headers, with or > without radio headers, you can't. > Ok, I'll verify this point. > I mean that with my different

Re: [tcpdump-workers] Problem with generation of Pcap traces for

> > So you'd need to call pcap_create() on each of the interfaces whose traffic > you want to aggregate *AND* call pcap_activate() on all of them. That is exactly what I'm doing. :) In addition, you should make sure the interfaces all have the same > link-layer type, as pcap files don't support

Re: [tcpdump-workers] Problem with generation of Pcap traces for

ow understand the point of using a pcap_t in this case. It is actually really helping me since I do not want to log the whole packet. And with my 2 pcap_t, I will be able to capture the full packet and only log a part of it. Anyway, thanks a lot for all the help. Regards. Johan Mazel - This is the tcpdump-workers list. Visit https://cod.sandelman.ca/ to unsubscribe.

[tcpdump-workers] Problem with generation of Pcap traces for Wireshark through Libpcap

shark, I get: "Protocols in frame: null:data". My question is: did I miss a function is the pcap library that allow me generate my perfect tracefile ? If it is the case, what is the name of this wonderful function ? :) Or is it a bug ? Thanks for your time. Johan Mazel - This is the tcpdump-w

Re: [tcpdump-workers] Filter incoming or leaving packets

> > You've already opened the device with pcap_open_live(), and assigned the > result to "descr", right? (You have to do that before you call > pcap_setdirection.) > Ok, that was the problem. It's fully functionnal now. Thanks for the help. Johan Mazel - This

Re: [tcpdump-workers] Filter incoming or leaving packets

reate a manual filter which will force the absence of capture of any which comes from the mac address of the interface considered. Thanks for the help and the tips. Johan Mazel 2009/2/27 Aaron Turner > On Fri, Feb 27, 2009 at 6:53 AM, Johan Mazel > wrote: > > Hello > > I woul

[tcpdump-workers] Filter incoming or leaving packets

packets coming or going from/to one host in particular but nothing about incoming/leaving packets. Thanks in advance for the help. Johan Mazel - This is the tcpdump-workers list. Visit https://cod.sandelman.ca/ to unsubscribe.

Re: [tcpdump-workers] Problems with two threads capturing on

I reran some test and apparently, the problem have disapeared. Thanks again for all the help. Johan 2009/2/22 Johan Mazel > 2009/2/22 Guy Harris > >> >> On Feb 22, 2009, at 11:41 AM, Johan Mazel wrote: >> >> What happens if you run one instance of tcpdump captu

Re: [tcpdump-workers] Problems with two threads capturing on

2009/2/22 Guy Harris > > On Feb 22, 2009, at 11:41 AM, Johan Mazel wrote: > > What happens if you run one instance of tcpdump capturing on wlan0 and >>> another instance capturing on eth0? Do they both report packets being >>> captured, or does just the one cap

Re: [tcpdump-workers] Problems with two threads capturing on

> > On Feb 20, 2009, at 1:46 AM, Johan Mazel wrote: > > I'm trying to use libpcap to capture packets on two interfaces (eth0 and >> wlan0). >> > > Linux, I presume? > You guess right: Ubuntu 8.10 and libpcap 0.9.8-5. :) > My problem is that pack

[tcpdump-workers] Problems with two threads capturing on different interfaces

mays be a problem of scheduling but I have no idea how to fix it. Thanks in advance for the help. Johan Mazel - This is the tcpdump-workers list. Visit https://cod.sandelman.ca/ to unsubscribe.

Re: [tcpdump-workers] Libpcap - pcapfindalldevs

quot;); > #endif >} > > >if (i==0) >{ > #ifdef WIN32 >fprintf(stderr," \tNo interfaces found! Exiting.\n"); > #else >fprintf(stderr," \tThis software must be run as root: No interfaces > found!"); > #endif >ex

[tcpdump-workers] Libpcap - pcapfindalldevs

Hi I'm trying to use pcap_findalldevs in order to scan the device available on my host to capture. My code (in C++) looks like that: result = pcap_findalldevs(&found_devices, errbuf); if(result < 0) { FindAllDevsException myFindAllDevsException(errbuf); cout << "Scan error" << endl