[tcpdump-workers] format cry from the wilderness

2004-06-29 Thread Eddie Kohler
I had thought that only 'tcpdump -v' had redesigned output for common protocols, but 'tcpdump' (no -v) does too. "IP" appears before IP addresses although there was no real ambiguity before, more superfluous punctuation, case changes -- and the result isn't yet "internally consistent" since it'

Re: [tcpdump-workers] Data from packet dissector looks really weird

2004-06-29 Thread alex medvedev
hallo, from the ether_ntoa man page: The string is returned in a statically allocated buffer, which subsequent calls will overwrite. maybe a strcpy() after each call will solve it? :) -alexm 13:42 29/06/2004 On Tue, 29 Jun 2004, Claudio Lavecchia wrote: > > /* LOOK AT THIS CAREFULLY!!!*/ > sr

Re: [tcpdump-workers] PCAP - IP Fragments

2004-06-29 Thread Darren Reed
In some email I received from Hans Klute, sie wrote: [ Charset ISO-8859-1 unsupported, converting... ] > Hi! > > I just realized a bug/feature of pcap that I didn?t think of. > I wrote a sniffer based on pcap. This sniffer can handle fragmented IP > packets. Now I realized that if you set up a fil

[tcpdump-workers] PCAP - IP Fragments

2004-06-29 Thread Hans Klute
Hi! I just realized a bug/feature of pcap that I didn´t think of. I wrote a sniffer based on pcap. This sniffer can handle fragmented IP packets. Now I realized that if you set up a filter with a UDP or TCP port, you will not get the additional fragments, because in these packets there are no UDP/

[tcpdump-workers] Data from packet dissector looks really weird

2004-06-29 Thread Claudio Lavecchia
Title: Message Hello everybody,   I am writing a packet dissector using libpcap and I have a nasty bug that is giving me hard times. I would be glad if someone could explain me what is going on.   I use libpcap 0.7.2 and run my packet dissector on two different environments (redhat 7.3 and