All things related to multicast

[Jeff Olenchek <>]

        >We had a 7513/120-8.5.S melt (RIP packets would stop being sent)
        >when a lan administator used a package called DriveImage. DriveImage
        >sends data to address 230.0.0.1/01-00-5e-00-00-01.
        >
        
        Jeff--
        
        ....
        
        The easiest fix would be to get DriveImage's developers to set
        some bit pattern in the second and third bytes of the IP address. 
        Even just making their software use 230.1.0.1 would be sufficient,
        since it would not look like 0x01-00-5e-00-00-01 at the MAC layer
        (it would be 0x01-00-5e-01-00-01).  However, I still think that
        the router should be able to drop this traffic without falling
        over.
        
        Just my $0.005,
        Tom
        - -- 
        Thomas Maufer

Tom,
Thank you for all the information. I have sent an email to Powerquest
asking about their software and I will try to persue this with them.
I will share any information with this list.

A secondary effect was that this group was in our mroute table:
        (130.240.192.207, 230.0.0.1), 00:00:52/00:02:07, flags: PCM
          Incoming interface: ATM9/0/0.2, RPF nbr 192.107.47.130, Mbgp
          Outgoing interface list: Null

        (130.240.193.217, 230.0.0.1), 00:00:52/00:02:07, flags: PCM
          Incoming interface: ATM9/0/0.2, RPF nbr 192.107.47.130, Mbgp
          Outgoing interface list: Null
I believe this caused the traffic to be forwarded off-campus.

I also sent an email to 
.

jeff