I've done a little more experimentation, and it doesn't appear to be a
problem with Obs. By snooping around with ping, I've determined that all
machines on my local subnet are 0 TTL away from each other. Apparently the
TTL of an outgoing packet from my Linux bos is not checked before it gets
dumped on the network.
* Eradicator *
I LOVE Frungy! It's the Sport of Kings!
-----Original Message-----
From: Mayhem & Chaos Coordinator [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, November 09, 1999 8:11 PM
To: [EMAIL PROTECTED]
Subject: Re: Obs multicasting issue
I've heard of this happening before -- I'll check to see if I am screwing
something up somewhere.
--ruaok Freezerburn! All else is only icing. -- Soul Coughing
Robert Kaye -- [EMAIL PROTECTED] http://moon.eorbit.net/~robert
----- Original Message -----
From: Derek Westcott <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Monday, November 08, 1999 11:49 AM
Subject: Obs multicasting issue
> I'd like to set up Obs to allow playing only on a specific set of machines
> (or possibly only locally) to reduce network traffic and to not violate
any
> copyright laws. I tried setting the TTL in obs.conf to 0 (the Linux
> multicast HOWTO claims this restricts to the local host), but all machines
> on my local subnet can still tune in. I can restrict play to the local
host
> by using route to send all multicast traffic to the loopback, but this
seems
> like a heavy-handed approach.
>
> Is there a cleaner solution?
>
> * Eradicator *
> I LOVE Frungy! It's the Sport of Kings!
>
