Bonjour, I made a test and ttl is set correctly in multicast (see result from ps below: -t 127)
/usr/bin/VPCScreenCapture -N Philippe d'Anfray -E philippe.d-anf...@cea.fr -L Saclay France -P 00 -A 84a65c2f1472543ad50b4131460f306c -c H261AS -f 16 -b 800 -q 85 -t 127 224.2.141.24/61520 It does not seem to be a firewall issue , I checked with the "network" people here (and we hame behaviour on two different sites...) Cordialement Philippe Andrew Rowley a écrit : > > Could this mean that the TTL is not being set correctly in VPC Screen e.g. > the TTL is 0? > > The alternative is that VPCScreen is not open in the local software firewall > (some firewalls need you to open outgoing and incoming traffic). > > >> -----Original Message----- >> From: ag-tech-boun...@lists.mcs.anl.gov [mailto:ag-tech- >> boun...@lists.mcs.anl.gov] On Behalf Of Philippe d'Anfray >> Sent: 26 March 2010 15:33 >> To: ag-t...@mcs.anl.gov >> Subject: Re: [AG-TECH] VPCscreen behaviour >> >> Bonjour >> >> I just tried out various configurations, it confirms what you have >> already observed. The solution remains to use vpcscreen through a bridge >> for the producer ? >> >> 1) "Producer" Multicast only VPC screen >> >> Receiver Multicast same site: screen >> Receiver Multicast other site: nothing >> Receiver With Bridge (same site) : nothing (except if we use "our" >> bridge which is on the same machine than the venue server) >> >> 2) "Producer" Multicast VPC screen + Video >> >> Receiver Multicast same site: screen + video >> Receiver Multicast other site: video only >> Receiver With Bridge (same site) : video only (except if we use "our" >> bridge which is on the same machine than the venue server then we have >> both) >> >> 3) No problem when the producer uses a bridge. >> >>
<<attachment: Philippe_d-Anfray.vcf>>
