I sent a report on this previously, but it didn't seem to go through on
the list.
Perhaps you're not getting stuff on the list delivered; I saw it, and
responded.
I did see it eventually, but I get the digest, and it only showed up in the
digest I got after a > 24 hour delay.
One problem occurs
Pawel Pokrywka wrote:
Hello,
I need to specify packet direction for my sniffing application, but
current libpcap doesn't offer this functionality. I've found a patch[1],
which adds ability to set direction of packet capture.
The patch works good, but it modifies pcap_pkthdr struct from pcap.h,
whic
Sivakumar Ramagopal wrote:
When it dissects the packets for a particular protocol, it uses its
built-in notion of which port numbers are used on which ports.
Did you mean notion of which *protocols* are used on which ports?
Yes.
-
This is the tcpdump-workers list.
Visit https://lists.sandelman.ca/
>
> "identifies" in what sense?
"identifies" in the same sense as what you have explained :)
>
> When it displays a name for a TCP port number, e.g.:
>
> 15:22:22.268265 IP host2.49536 > host2.http: . ack 1 win 65535
>
> it uses "getservbyport()", so it either uses /etc/services or whatever
CVS log entries from 30.04.2005 (Sat) 09:07:08 - 01.05.2005 (Sun) 09:07:33 GMT
=
Summary by authors
=
Author: guy
File: libpcap/gencode.c; Revisions: 1.239, 1.238, 1.237, 1.236, 1.235,
1