[tcpdump-workers] [PATCH 2/2] print-olsr: Add basic IPv6 support.

2009-05-16 Thread Florian Forster
From: Florian Forster Unfortunately OLSR uses the same IDs for IPv4 and IPv6 packets, even though the size of "messages" differ. The version of the internet protocol is therefore handed to the "olsr_print" function. The code isn't very nice, due to a high density of #ifdef INET6'es. If IPv6-supp

[tcpdump-workers] [PATCH 1/2] util.c: Add the `mask62plen' utility function.

2009-05-16 Thread Florian Forster
From: Florian Forster The function does the same as `mask2plen' but for IPv6. Signed-off-by: Florian Forster --- interface.h |1 + util.c | 29 + 2 files changed, 30 insertions(+), 0 deletions(-) diff --git a/interface.h b/interface.h index 688a2ac..f6a4

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

2009-05-16 Thread Guy Harris
On May 16, 2009, at 10:32 AM, Johan Mazel wrote: I suppose that the values for linktype are the ones I'm talking in my first mail : 01 for Ethernet, 06 for Token Ring, 07 for ARCnet, etc... ??? Libpcap has two sets of link-layer type values - the DLT_ values, which are what are returned b

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

2009-05-16 Thread Aaron Turner
On Sat, May 16, 2009 at 10:12 AM, Guy Harris wrote: > > On May 16, 2009, at 3:18 AM, Johan Mazel wrote: > >> Does this restriction means that I can't aggregate trace of different >> version of Ethernet (eg.: 802.3 and 802.11) ? > > (802.11 isn't a version of Ethernet.) > > If your 802.11 device su

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

2009-05-16 Thread Johan Mazel
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

2009-05-16 Thread Guy Harris
On May 16, 2009, at 3:18 AM, Johan Mazel wrote: Does this restriction means that I can't aggregate trace of different version of Ethernet (eg.: 802.3 and 802.11) ? (802.11 isn't a version of Ethernet.) If your 802.11 device supplies "fake Ethernet" headers, you can aggregate its packets wi

Re: [tcpdump-workers] Problems with select (the other way around...)

2009-05-16 Thread Ricardo Balbinot
tks.. a noob question (should have read the man page carefully). Regards, Ricardo 2009/5/15 Michael Richardson > > > "Ricardo" == Ricardo Balbinot writes: >Ricardo> tv.tv_sec = 1; >Ricardo> tv.tv_usec = 0; >Ricardo> FD_ZERO(&rfds); >Ricardo> FD_SET(handle_fd,&rfds); >Ri

[tcpdump-workers] [PATCH] print-olsr: Don't trust the package payload.

2009-05-16 Thread Florian Forster
From: Florian Forster Especially not to do pointer arithmetic. This is a real problem even without malicious people around if you use OLSR via IPv6, because the message IDs didn't change but addresses are now longer than four bytes. Signed-off-by: Florian Forster --- print-olsr.c | 13 +

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

2009-05-16 Thread Johan Mazel
> > 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