All things related to multicast

[Mark Fullmer <>]

> > 224.0.1.22    991     SVRLOC.MCAST.NET
> > 224.0.1.35    917     SVRLOC-DA.MCAST.NET
> 
> I'm not familiar with the above two.  What are they about?

It's a service location protocol.  It appears to be
Novell clients and servers using it.  see www.srvloc.org

> This one is very nasty, not because of "Dogfight", but,
> because SGI "objectserver" also uses it.  (Yes, I have 
> seen users accidentally sharing peoplepages phonebook entries 
> with people halfway across the world.  People they never 
> even heard of.  Very amusing.  In one case, I recall
> hearing a user saying, "Whoever the 
> !@#$%^&*
>  is this
> guy, and what is he doing on my system!?")

Same with the svrloc.  We had people complaining about filesystems
showing up from other countries in their service list.

> > 224.0.1.60    142     HP-DEVICE-DISC.MCAST.NET
> 
> What is this one?  I have not heard of it.

I think it's HP hubs.

> While you are on the subject, you should also add "rwhod" in 
> its several variants.  Sometimes rwhod is configured with TTL=16
> or higher, and you end up with a worldwide broadcast domain
> sharing rwhod information.  Ugly.
> 
> I believe I have seen traffic on both 224.0.1.3 and 224.0.2.1.
> You can also filter the port (udp 513 IIRC).
> 
> Another potentially ugly one which is sometimes configured, 
> for reasons I don't understand, with a high TTL, is sunrpc.  
> Again, you have a choice of filtering the address, IIRC, 
> 224.0.2.2, or the port, 111.

I wish there was a better way to know about these groups ahead
of time.

--
mark