----- Original Message ----- From: "fooler" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Sunday, February 17, 2002 3:08 PM Subject: Re: [plug] 192.168.100.1?
> ----- Original Message ----- > From: "Pong" <[EMAIL PROTECTED]> > To: <[EMAIL PROTECTED]> > Sent: Sunday, February 17, 2002 10:43 AM > Subject: Re: [plug] 192.168.100.1? > > > > the other subscribers on the same cable broadcast segment can send a > > 224.0.0.1 multicast packet but your pc/hardware router will not forward it > > to your lan even if its time-to-live value is greater than 1 (assuming > > the router implements multicast routing correctly). so only the router can > > see that multicast packet, but the internal hosts in your lan will not. > > this is not true :-> by increasing the ttl, an application can perform an > *expanding ring search* for a particular server... the first multicast > datagram is sent with a ttl of 1, if no response is received, a ttl of 2 is > tried, then 3 and so on and so forth... in this way, the application > locates the closest server in terms of hops. ooppss sorry.. i am referring to not within the range of 224.0.0.0 and 224.0.0.255... within this range regardless of the ttl value, it cannot multicast further than *one* hop fooler. _ Philippine Linux Users Group. Web site and archives at http://plug.linux.org.ph To leave: send "unsubscribe" in the body to [EMAIL PROTECTED] To subscribe to the Linux Newbies' List: send "subscribe" in the body to [EMAIL PROTECTED]
