Hi folks! On May 24, 2005, at 5:42 PM, Harald Barth wrote:
Sorry, I can't help you, but your talking about NAT makes me wonder if 1.3.X has something built in that makes it NATable? My experience with 1.2.X was rather unsatisfactory as it sometimes works, but sometimes (I assume when several clients behind the NAT want something from the same server outside) just fails for some minutes and then starts working again.So, is the rx in 1.3.X broken and leaking resources? Has this something to do with timeouts and NAT-stuff? Is there a way to terminate connections forcefully? If this is the NAT stuff makeing me unhappy, how do I turn it off?
The problem is by no means esoteric: We have a HPC cluster doing data analysis and the configuration files are in a different cell. I think I don't have to give reasons why we don't want and also cannot give public IP addresses to the cluster nodes.
To give a bit more background in case someone has already solved this: everything is on Linux2.4, the (possible) NAT gateway would be on the AFS database server and all fileservers of the local cell also are connected to the private network. And for the quick ones: rsync doesn't cut it for our case ;-)
Ciao,
Roland
--
TU Muenchen, Physik-Department E18, James-Franck-Str. 85747 Garching
Telefon 089/289-12592; Telefax 089/289-12570
--
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
A: Top-posting.
Q: What is the most annoying thing on a mailing list?
-----BEGIN GEEK CODE BLOCK-----
Version: 3.12
GS/CS/M/MU d-(++) s:+ a-> C+++ UL++++ P-(+) L+++ E(+) W+ !N K- w--- M+
!V Y+
PGP++ t+(++) 5 R+ tv-- b+ DI++ e+++>++++ h---- y+++ ------END GEEK CODE BLOCK------
PGP.sig
Description: This is a digitally signed message part
