On Wed, May 19, 2010 at 8:29 AM, Mark Huijgen <[email protected]> wrote: > > On 05/14/2010 09:21 PM, Jeffrey Altman wrote: >> On 5/14/2010 3:11 PM, Steve Simmons wrote: >> >> >>> Next step would be to have him try 1.5.74, but before he goes that far I'd >>> be interested in anyone who's seen similar problems and what if anything >>> fixed them. >>> >> This is the solution. The NAT ping functionality in the 1.5.74 rx >> library was added to ensure that there is sufficient outbound traffic to >> convince the firewall or NAT to leave the in-bound port open. > > Would it be safe to apply this NAT ping functionality to the 1.4.x > series also?
For you to apply it to builds you do? Sure. It's not likely to be in the next 1.4 release with the most obvious issue being for reasons of testing. We always have the question of what falls on which side of the features divide for stable trees. At this point we certainly hope 1.6 is very near. > I have patched my 1.4.12 linux client with these 2 patches I found in git: > > rx lowlevel nat ping > http://git.openafs.org/?p=openafs.git;a=commitdiff_plain;h=d24078658d183ea2e72e61c1888e9900bac0ec32 > rx nat event connection reference > http://git.openafs.org/?p=openafs.git;a=commitdiff_plain;h=d9cf88428aa542d1cd304e82f02333eced0194ae > > Are these 2 patches enough? Yes. _______________________________________________ OpenAFS-info mailing list [email protected] https://lists.openafs.org/mailman/listinfo/openafs-info
