Andrew Rowley a écrit : > Yes, the ttl looks like the culprit. Are you sure that -t is the correct way > to set the ttl in VPCScreen? > This is what "VPCScreenCapture -h" tells us. There is no way to fix the TTL through the AG Client Interface (VPCScreenCapture is called with -t 127) may be this value is not used and some substitute (16) is hard coded somewhere ?
Bonne soirée Philippe VPCScreen by the ANU Internet Futures team Usage: VPCScreenCapture [-h] [-K <str>] [-c <str>] [-N <str>] [-T <str>] [-E <str>] [-L <str>] [-P <str>] [-A <str>] [-b <num>] [-f <num>] [-s <str>] [-q <num>] [-t <num>] [-m] destination (address/port) -h, --help Show help -K, --key=<str> Set the encryption key for sending -c, --codec=<str> Set the codec to use for sending -N, --name=<str> SDES name -T, --note=<str> SDES note -E, --email=<str> SDES email -L, --location=<str> SDES location -P, --phone=<str> SDES phone -A, --appsite=<str> APP specific site -b, --bandwidth=<num> Bandwidth in bits per second -f, --framerate=<num> Frame rate in frames per second -s, --size=<str> Specify fixed size either CIF or PAL for -q, --quality=<num> Specify quality of encoding (1 -- 100) -t, --ttl=<num> TTL for multicast transmission -m, --minimize Start the interface minimized
<<attachment: Philippe_d-Anfray.vcf>>
