Note that Ethernet_802.3 IPX frames can appear on network other than

Ethernet/802.3 networks, due to, e.g., bridging of broadcast frames.

diff --git a/print-llc.c b/print-llc.c
index d7a59c3834a0db28a2b1807eafb741473f28374c..280ea88a906a98606cd027d6c28c60d449cd47df 100644 (file)
--- a/print-llc.c
+++ b/print-llc.c
@@ -24,7 +24,7 @@
 
 #ifndef lint
 static const char rcsid[] =
 
 #ifndef lint
 static const char rcsid[] =

-    "@(#) $Header: /tcpdump/master/tcpdump/print-llc.c,v 1.39 2001-06-15 07:59:14 itojun Exp $";
+    "@(#) $Header: /tcpdump/master/tcpdump/print-llc.c,v 1.40 2001-07-21 23:14:23 guy Exp $";

 #endif
 
 #ifdef HAVE_CONFIG_H
 #endif
 
 #ifdef HAVE_CONFIG_H


@@ -90,6 +90,11 @@ llc_print(const u_char *p, u_int length, u_int caplen,
                 * the IPX packet starts right after the Ethernet header,
                 * with a signature of two bytes of 0xFF (which is
                 * LLCSAP_GLOBAL).
                 * the IPX packet starts right after the Ethernet header,
                 * with a signature of two bytes of 0xFF (which is
                 * LLCSAP_GLOBAL).

+                *
+                * (It might also have been an Ethernet_802.3 IPX at
+                * one time, but got bridged onto another network,
+                * such as an 802.11 network; this has appeared in at
+                * least one capture file.)

                 */
                ipx_print(p, length);
                return (1);
                 */
                ipx_print(p, length);
                return (1);