Ethereal-cvs: [ethereal-cvs] cvs commit: ethereal/wiretap snoop.c ngsniffer.c netxray.c
guy 1999/08/23 22:19:44 CDT
Modified files:
wiretap snoop.c ngsniffer.c netxray.c netmon.c
iptrace.c libpcap.c wtap.h
Log:
Add a new Wiretap encapsulation type WTAP_ENCAP_FDDI_BITSWAPPED, meaning
"FDDI with the MAC addresses bit-swapped"; whether the MAC addresses are
bit-swapped is a property of the machine on which the capture was taken,
not of the machine on which the capture is being read - right now, none
of the capture file formats we read indicate whether FDDI MAC addresses
are bit-swapped, but this does let us treat non-"libpcap" captures as
being bit-swapped or not bit-swapped independent of the machine on which
they're being read (and of the machine on which they were captured, but
I have the impression they're bit-swapped on most platforms), and allows
us to, if, as, and when we implement packet capture in Wiretap, mark
packets in a capture file written in Wiretap-native format based on the
machine on which they are captured (assuming the rule "Ultrix, Alpha,
and BSD/OS are the only platforms that don't bit-swap", or some other
compile-time rule, gets the right answer, or that some platform has
drivers that can tell us whether the addresses are bit-swapped).
(NOTE: if, for any of the capture file formats used only on one
platform, FDDI MAC addresses aren't bit-swapped, the code to read that
capture file format should be fixed to flag them as not bit-swapped.)
Use the encapsulation type to decide whether to bit-swap addresses in
"dissect_fddi()".
Revision Changes Path
1.8 +2 -2 ethereal/wiretap/snoop.c
1.20 +2 -2 ethereal/wiretap/ngsniffer.c
1.12 +2 -2 ethereal/wiretap/netxray.c
1.12 +2 -2 ethereal/wiretap/netmon.c
1.9 +2 -2 ethereal/wiretap/iptrace.c
1.15 +11 -1 ethereal/wiretap/libpcap.c
1.34 +25 -9 ethereal/wiretap/wtap.h
