On Wed, 2007-07-25 at 17:20 +0200, tomasz abramowicz wrote: > so should i start another stunnel process on server B which listens > on 1986, encrypts, and sends to server A on 1986, which in turn in > listening on 1986 and forwards unencrypted to localhost 1984? Yes, that's how to do it. Rather, you can use the existing stunnel process listening on 1985. Set up a "client" stunnel on port 1986 forwarding connections to port 1985 on the remote machine, something like On A: stunnel -c -d 1986 -r B:1985 On B: stunnel -c -d 1986 -r A:1985 Use %Rsync localhost:1986 on both sides. Best regards, Tom -- ---------------------------------------------------------------------------- Thomas Aeby, Kirchweg 52, 1735 Giffers, Switzerland, Tel: (+41)264180040 Internet: suppressed PGP public key available ---------------------------------------------------------------------------- ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ Bigsister-general mailing list suppressed https://lists.sourceforge.net/lists/listinfo/bigsister-general
Mail converted by mhonarc 2.6.15
This archive provided courtesy of JSW4.NET, Internet Hosting Services for Small Business.