From: Brian McGahan (bmcgahan@internetworkexpert.com)
Date: Thu Jun 23 2005 - 14:34:28 GMT-3
John,
Yes tunneling would decrement the TTL. Bridging is not really a
valid option because you can't bridge just IPv4 multicast while routing
IPv4 unicast. You would have to bridge the IPv4 stack as a whole. Most
likely the easiest solution is to tell your application guys to just
increase the TTL to 255. Use the network to control where the feed is
delivered (access-lists, scoping, etc), not the application itself.
HTH,
Brian McGahan, CCIE #8593
bmcgahan@internetworkexpert.com
Internetwork Expert, Inc.
http://www.InternetworkExpert.com
Toll Free: 877-224-8987 x 705
Outside US: 775-826-4344 x 705
24/7 Support: http://forum.internetworkexpert.com
Live Chat: http://www.internetworkexpert.com/chat/
> -----Original Message-----
> From: Sheahan, John [mailto:John.Sheahan@priceline.com]
> Sent: Thursday, June 23, 2005 12:30 PM
> To: Brian McGahan
> Subject: RE: Changing a multicast packets TTL
>
> Thanks a lot for the help, Brian.
>
> I was thinking the same thing but wanted to make sure. If I did you a
> tunnel, it would still decrement the TTL anyway, wouldn't it?
>
> -----Original Message-----
> From: Brian McGahan [mailto:bmcgahan@internetworkexpert.com]
> Sent: Thursday, June 23, 2005 1:26 PM
> To: Montiean; Sheahan, John; ccielab@groupstudy.com
> Subject: RE: Changing a multicast packets TTL
>
> This would not have any effect. The problem he is seeing is
> that the TTL is expiring, not that it is administratively scoped.
AFAIK
> there's no way on the router to edit the TTL of a packet. Looks like
> you're either going to have to bridge it or have them increase the
TTL.
>
> Brian McGahan, CCIE #8593
> bmcgahan@internetworkexpert.com
>
> Internetwork Expert, Inc.
> http://www.InternetworkExpert.com
> Toll Free: 877-224-8987 x 705
> Outside US: 775-826-4344 x 705
> 24/7 Support: http://forum.internetworkexpert.com
> Live Chat: http://www.internetworkexpert.com/chat/
>
>
> > -----Original Message-----
> > From: nobody@groupstudy.com [mailto:nobody@groupstudy.com] On Behalf
> Of
> > Montiean
> > Sent: Thursday, June 23, 2005 2:46 PM
> > To: Sheahan, John; ccielab@groupstudy.com
> > Subject: Re: Changing a multicast packets TTL
> >
> > Hi,
> > Rather than decresing ttl at the source, you might need to lower
ttl
> > under
> > each interface on each hop. But this might come up with another
> problem
> > especially at the border router.
> >
> > r6(config-if)#ip multicast ttl-threshold ?
> > <0-255> TTL threshold
> >
> > By default, it has set to 0. So it suppose to pass all the multicast
> > packet.
> > Check link below for detail.
> >
> > http://www.cisco.com/warp/public/105/mcastguide0.html#ttlsetting
> >
> > HTH,
> > Montiean
> >
> > ----- Original Message -----
> > From: "Sheahan, John" <John.Sheahan@priceline.com>
> > To: <ccielab@groupstudy.com>
> > Sent: Thursday, June 23, 2005 8:44 AM
> > Subject: Changing a multicast packets TTL
> >
> >
> > > I have a multicast application that I am trying to route that has
a
> TTL
> > > of 1 in every packet and will not route due to this fact.
> > >
> > > I have asked the application guys to see if there is a way of
> changing
> > > that but haven't gotten an answer yet.
> > >
> > > Does anyone know of a way to get this to work besides bridging?
> > >
> > >
> > >
> > > Thanks
> > >
> > >
>
This archive was generated by hypermail 2.1.4 : Wed Jul 06 2005 - 14:43:42 GMT-3