-----BEGIN PGP SIGNED MESSAGE-----
According to: http://groups.yahoo.com/group/amanda-users/message/32078 There is an excellent writeup somewhere in the amanda-hackers list archive, titled "How Amanda uses UDP and TCP ports", dated 23.07.2001, by John R. Jackson, which explains all this thoroughly. Looking through the eGroups archive, it appears that everthing between 2001/7/11 and 2001/9/29 got lost from the yahoo group. Searches on even "TCP ports" got me nothing. Useless yahoo! However, it was in fact posted on 2001/6/23, and is at: http://groups.yahoo.com/group/amanda-hackers/message/2733 A very good document, it should be in the doc dir. Re: If the Amanda tape server is outside, NAT will have to be told how to translate the incoming connections from dumper to the client. To do that, the UDP and TCP port ranges will have to be known and only one client can be inside. If you are willing to allocate each client a unique port range, the NAT can probably be programmed. I live with real IPs as well, so I don't deal with this. It would be most nice if the port ranges could be specified on the client on some config file or command line. Putting them into amanda.conf (on the tape server) is wrong because the client is more likely to be in close touch with the firewall/NAT box than the tape server. ] ON HUMILITY: to err is human. To moo, bovine. | firewalls [ ] Michael Richardson, Sandelman Software Works, Ottawa, ON |net architect[ ] [EMAIL PROTECTED] http://www.sandelman.ottawa.on.ca/ |device driver[ ] panic("Just another NetBSD/notebook using, kernel hacking, security guy"); [ -----BEGIN PGP SIGNATURE----- Version: 2.6.3ia Charset: latin1 Comment: Finger me for keys iQCVAwUBPDeXOoqHRg3pndX9AQHN8gP/UJSwd+qLfi/3zzw5DEMaJCXfmLgMsfwh 5lquPgCFd9AVBjNvHILoc5ZAlhd0JdyC0NOFuaxtMKAD6ywYHySmHFmfop2XVc7m o0EktOYyfhGu7Rpr7W22fKKFcH5WaEVKNMDcoq0CdfnSa10hYr5t9Rf/oYo8+c8o z8FBNDjSD9c= =bsJB -----END PGP SIGNATURE-----
