Token Ring multicasts are handled the same way other 802.x multicasts

are handled, with an I/G bit at the bottom (when handed to the host) of
the first byte of the destination address.

diff --git a/gencode.c b/gencode.c
index e296afda0d9e49c51f39c761dbed6bfd10666880..71aec3d9a7d0855f6cd411e9f687193cd21ea635 100644 (file)
--- a/gencode.c
+++ b/gencode.c
@@ -21,7 +21,7 @@
  */
 #ifndef lint
 static const char rcsid[] =
-    "@(#) $Header: /tcpdump/master/libpcap/gencode.c,v 1.176 2002-08-08 08:22:45 guy Exp $ (LBL)";
+    "@(#) $Header: /tcpdump/master/libpcap/gencode.c,v 1.177 2002-08-08 09:09:58 guy Exp $ (LBL)";
 #endif
 
 #ifdef HAVE_CONFIG_H
@@ -4343,13 +4343,19 @@ gen_multicast(proto)
                }
 
                if (linktype == DLT_FDDI) {
-                       /* XXX TEST THIS: MIGHT NOT PORT PROPERLY XXX */
+                       /*
+                        * XXX TEST THIS: MIGHT NOT PORT PROPERLY XXX
+                        *
+                        * XXX - was that referring to bit-order issues?
+                        */
                        /* fddi[1] & 1 != 0 */
                        return gen_mac_multicast(1);
                }
 
-               /* TODO - check how token ring handles multicast */
-               /* if (linktype == DLT_IEEE802) ... */
+               if (linktype == DLT_IEEE802) {
+                       /* tr[2] & 1 != 0 */
+                       return gen_mac_multicast(2);
+               }
 
                if (linktype == DLT_IEEE802_11) {
                        /*