From bd73c7de4ac7c136cd3dd8f8be9a621f4a09f083 Mon Sep 17 00:00:00 2001 From: guy Date: Wed, 7 Sep 2005 08:29:17 +0000 Subject: Warn about some broken drivers *cough* Broadcom *cough* ignoring DLIOCRAW and overwriting the Ethertype with the SAP we happened to bind to (the fact that we requested SAP promiscuity nonwithstanding). --- pcap.3 | 8 ++++++-- 1 file changed, 6 insertions(+), 2 deletions(-) diff --git a/pcap.3 b/pcap.3 index aa5939e..2be5697 100644 --- a/pcap.3 +++ b/pcap.3 @@ -1,4 +1,4 @@ -.\" @(#) $Header: /tcpdump/master/libpcap/Attic/pcap.3,v 1.64.2.7 2005-07-07 02:04:35 guy Exp $ +.\" @(#) $Header: /tcpdump/master/libpcap/Attic/pcap.3,v 1.64.2.8 2005-09-07 08:29:17 guy Exp $ .\" .\" Copyright (c) 1994, 1996, 1997 .\" The Regents of the University of California. All rights reserved. @@ -689,7 +689,11 @@ supplied to as the source link-layer address, if the header contains such an address, might be changed to be the address assigned to the interface on which the packet it sent, if the platform doesn't support sending -completely raw and unchanged packets. +completely raw and unchanged packets. Even worse, some drivers on some +platforms might change the link-layer type field to whatever value +libpcap used when attaching to the device, even on platforms that +.I do +nominally support sending completely raw and unchanged packets. .PP .B pcap_sendpacket() is like -- cgit v1.2.3