[tcpdump-workers] Automatic report from sources (tcpdump libpcap htdocs) between 08.06.2004 - 09.06.2004 GMT
CVS log entries from 08.06.2004 (Tue) 09:06:44 - 09.06.2004 (Wed) 09:06:31 GMT = Summary by authors = Author: hannes File: tcpdump/print-lspping.c; Revisions: 1.3 = Log entries = Description: add support for the LDP_IPV4, LDP_IPV6 BGP_IPV4 subTLVs inside the target FEC TLV Modified files: File: tcpdump/print-lspping.c; Revision: 1.3; Date: 2004/06/09 05:14:42; Author: hannes; Lines: (+60 -6) = Summary of modified files = File: tcpdump/print-lspping.c Revisions: 1.3 Authors: hannes (+60 -6) -- Automatic cron job from /tcpdump/bin/makelog - This is the tcpdump-workers list. Visit https://lists.sandelman.ca/ to unsubscribe.
[tcpdump-workers] Unexpected primitive ack DL_UNITDATA_IND
Hi, I have an application which uses libpcap 0.7.2 to monitor network traffic by tracking the size of IP packets as well as their source and destination. One of our QA people just encountered a rather odd error on Solaris 8 which we have never seen before: recv_ack: info: Unexpected primitive ack DL_UNITDATA_IND Does anybody know what this means? It seems to have occurred while calling pcap_open_live (snaplen is sizeof(struct ip) + sizeof(struct ether_header), promisc is 1, to_ms is 100). Thanks, Gordon -- Gordon Tyler (Software Developer) Quest Software http://java.quest.com/ 260 King Street East, Toronto, Ontario M5A 4L5, Canada Voice: 416-643-4846 | Fax: 416-594-1919 - This is the tcpdump-workers list. Visit https://lists.sandelman.ca/ to unsubscribe.
Re: [tcpdump-workers] Unexpected primitive ack DL_UNITDATA_IND
On Jun 9, 2004, at 1:58 PM, Rick Jones wrote: On the surface I wouldn't think so - simply attaching to a PPA I don't think means traffic could arrive - however, if one has attached, and then binds to a SAP, then traffic could indeed start arriving. (Il-informed guesstimation, and hopefully I'm recalling the correct distinction between attach and bind) Well, we *are* doing an info request after binding, so perhaps it might happen then. I'm not sure why we're doing that; it dates back to libpcap 0.4. Do you know of any reason why the dl_mac_type from an info request before binding to a SAP might be different from the dl_mac_type from a request after binding to a SAP? - This is the tcpdump-workers list. Visit https://lists.sandelman.ca/ to unsubscribe.
