[AG-DEV] Bridge Pings

Todd Zimmerman toddz at sfu.ca
Thu Jul 6 11:37:55 CDT 2006


Thanks for the update, Eric.

I've thought about running a CVS version - I'm sure there are a bunch of Bridge fixes in there;
however I hate to do that on a production venue/bridge server.  Having said that - if the fixes are
worth it, I may just do it.

Any idea when 3.0.2 will be released?

Todd

Eric Olson wrote:
> Hi Todd,
> We have worked on a fix for this already, although it has not been
> released yet.
> 
> Developers (modifying an installation is not normally recommended for
> regular users) can test this out by updating the installed
> RegistryClient.py file.  Here is the current cvs version:
> http://fl-cvs.mcs.anl.gov/viewcvs/viewcvs.cgi/*checkout*/AccessGrid/AccessGrid/Registry/RegistryClient.py?rev=1.21&content-type=text/plain
> 
> 
> If you're running a bridge and want to test the bridge side of the code,
> you'll need a few more files, so you could test from a recently updated
> cvs checkout.
> 
> Eric
> 
> Todd Zimmerman wrote:
>> Just got a note from one of our AG3 users complaining that the
>> venueclient was showing no bridges as
>> being available.
>>
>>
>> After a quick inspection, it appears the venueclient checks to see if
>> the bridges are up by pinging
>> them.  By blocking inbound icmp packets, I can recreate the problem on
>> my local box, so I assume
>> this is the issue.
>>
>> This is a fairly major problem for some of our sites/campuses that
>> block all inbound icmp traffic
>> (pings).  It effectively makes them unable to use AG3.
>>
>> Is there any way to force AG3 to not attempt to ping the bridges?
>>
>> Todd
>>
> 




More information about the ag-dev mailing list