FW: FW: [AG-TECH] TTL - Multicast

[Ivan R. Judson]

-----Original Message-----
From: owner-openmash-developers at bmrc.berkeley.edu
[mailto:owner-openmash-developers at bmrc.berkeley.edu]On Behalf Of Lloyd
Lim
Sent: Friday, March 15, 2002 12:01 PM
To: Open Mash Developers
Subject: Re: FW: [AG-TECH] TTL - Multicast


On Thursday 14 March 2002 10:08 am, Ivan R. Judson wrote:
>Does anybody have a suggestion for Kevin?
>
>--Ivan
>
>-----Original Message-----
>From: owner-ag-tech at mcs.anl.gov [mailto:owner-ag-tech at mcs.anl.gov]On
> Behalf Of Nolan, Kevin [NCSUS]
>Sent: Thursday, March 14, 2002 11:02 AM
>To: 'ag-tech at mcs.anl.gov'
>Subject: [AG-TECH] TTL - Multicast
>
>I got this from my network person when running the AG from three of
> our labs located in Belgium, New Jersey and California.
>
>The problem we're seeing with both VIC and Rat is that as the TTL
> value gets increased, the amount of data being transmitted is
> decreased as a way to alleviate network congestion.  The problem with
> this is that our remote sites generally connect via high-bandwidth
> links, and the associated lower frame rates are unacceptable for
> real-time communication between sites.  Is there any way that we can
> change these values, or does the source code have to be modified?
>
> - Kevin Nolan (J&J)

Yes, this is actually documented in our otherwise lame documentation.
See <http://www.openmash.org/users/tools/usage/vic.html>.

In short, use -B kbps to specify the maximum value for the bandwidth 
slider.  For example:

vic 233.0.25.25/22334/255

will normally give you a rather small maximum bandwidth.

vic -B 1024 233.0.25.25/22334/255

will give you a maximum bandwidth of 1 Mb/s.

You probably want to be careful when you do stuff like this.

Lloyd