Stunnel/Rsync - Revision history

Admin: Replacing charlesreid1.com:3000 with git.charlesreid1.com

2019-10-09T03:56:11Z

Replacing charlesreid1.com:3000 with git.charlesreid1.com

← Older revision		Revision as of 03:56, 9 October 2019
Line 26:		Line 26:
	===Configure Rsync Server===		===Configure Rsync Server===

	Main repository: https://charlesreid1.com~~:3000~~/docker/d-stunnel		Main repository: https://git.charlesreid1.com/docker/d-stunnel

	To configure the rsync stunnel server:		To configure the rsync stunnel server:
Line 33:		Line 33:
	* The Makefile will ultimately set the port number, and pass that into the build script. The build script will use sed to find/replace the token PORT with the numerical port.		* The Makefile will ultimately set the port number, and pass that into the build script. The build script will use sed to find/replace the token PORT with the numerical port.

	Makefile that calls build and run scripts: https://charlesreid1.com~~:3000~~/docker/d-stunnel/src/master/Makefile		Makefile that calls build and run scripts: https://git.charlesreid1.com/docker/d-stunnel/src/master/Makefile

	Build rsync stunnel docker container script: https://charlesreid1.com~~:3000~~/docker/d-stunnel/src/master/build_rsync.sh		Build rsync stunnel docker container script: https://git.charlesreid1.com/docker/d-stunnel/src/master/build_rsync.sh

	The build docker container script actually uses the Dockerfile, which assembles the various files that are needed to run both stunnel and rsync. The build script updates the port number in both the Dockerfile and in the rsync stunnel configuration file using sed, then bakes these files into the final container image using docker build.		The build docker container script actually uses the Dockerfile, which assembles the various files that are needed to run both stunnel and rsync. The build script updates the port number in both the Dockerfile and in the rsync stunnel configuration file using sed, then bakes these files into the final container image using docker build.

	Dockerfile_rsync_stunnel: https://charlesreid1.com~~:3000~~/docker/d-stunnel/src/master/Dockerfile_rsync_stunnel		Dockerfile_rsync_stunnel: https://git.charlesreid1.com/docker/d-stunnel/src/master/Dockerfile_rsync_stunnel

	Universal rsync stunnel configuration file: https://charlesreid1.com~~:3000~~/docker/d-stunnel/src/master/stunnel.server.rsync.conf		Universal rsync stunnel configuration file: https://git.charlesreid1.com/docker/d-stunnel/src/master/stunnel.server.rsync.conf

	Finally, the Makefile calls the run script and passes the port number to the run script, which hooks up the necessary ports between the host and the container, mounts the necessary volumes, and sets up the docker network interface (as well as running the container in the foreground or background).		Finally, the Makefile calls the run script and passes the port number to the run script, which hooks up the necessary ports between the host and the container, mounts the necessary volumes, and sets up the docker network interface (as well as running the container in the foreground or background).

	Run rsync stunnel container: https://charlesreid1.com~~:3000~~/docker/d-stunnel/src/master/run_rsync.sh		Run rsync stunnel container: https://git.charlesreid1.com/docker/d-stunnel/src/master/run_rsync.sh

	===Running Rsync Server===		===Running Rsync Server===
Line 77:		Line 77:
	where A.B.C.D is the server's IP address.)		where A.B.C.D is the server's IP address.)

	See https://charlesreid1.com~~:3000~~/docker/d-stunnel/src/master/stunnel.server.rsync_over_273.conf for details		See https://git.charlesreid1.com/docker/d-stunnel/src/master/stunnel.server.rsync_over_273.conf for details

	==Stunnel Server for Rsync==		==Stunnel Server for Rsync==
Line 104:		Line 104:
	</pre>		</pre>

	See https://charlesreid1.com~~:3000~~/docker/d-stunnel/src/master/stunnel.server.rsync_over_273.conf		See https://git.charlesreid1.com/docker/d-stunnel/src/master/stunnel.server.rsync_over_273.conf

	===Running Stunnel Server for Rsync===		===Running Stunnel Server for Rsync===
Line 180:		Line 180:
	</pre>		</pre>

	See stunnel for rsync config file for Raspberry Pi clients: https://charlesreid1.com~~:3000~~/rpi/pi-stunnel/src/master/stunnel.rpiclient.rsync_over_273.conf		See stunnel for rsync config file for Raspberry Pi clients: https://git.charlesreid1.com/rpi/pi-stunnel/src/master/stunnel.rpiclient.rsync_over_273.conf

	==Stunnel Client==		==Stunnel Client==

Admin: /* Running Rsync Server */

2017-04-09T05:46:55Z

Running Rsync Server

← Older revision		Revision as of 05:46, 9 April 2017
Line 54:		Line 54:
	$ sudo service rsync start		$ sudo service rsync start
	</pre>		</pre>

			Alternatively, you can get an rsync docker container up and running: [[Docker/Rsync]]

	===Adding Tcp Wrappers for Secure Rsync Protocol===		===Adding Tcp Wrappers for Secure Rsync Protocol===

Admin: /* Configure Rsync Server */

2017-04-09T05:46:19Z

Configure Rsync Server

← Older revision		Revision as of 05:46, 9 April 2017
Line 26:		Line 26:
	===Configure Rsync Server===		===Configure Rsync Server===

	On the server, we want to run an rsync daemon that will listen for incoming requests to synchronize files. The daemon will compare incoming files to the current copies of files, and update any changes it does not have.		Main repository: https://charlesreid1.com:3000/docker/d-stunnel

	To ~~run an~~ rsync ~~daemon~~, ~~edit the~~ rsync ~~config~~ file ~~at <code>/etc/rsyncd~~.~~conf<~~/~~code>~~.		To configure the rsync stunnel server:
			* First, define a universal rsync stunnel configuration file.
			* Everywhere you need to specify the numerical port, use the token PORT
			* The Makefile will ultimately set the port number, and pass that into the build script. The build script will use sed to find/replace the token PORT with the numerical port.

	In the config file you will set the name of your module, which has a specific data directory on the server. You can potentially have multiple clients syncing to multiple locations on the server by using multiple modules, but we are just using one.		Makefile that calls build and run scripts: https://charlesreid1.com:3000/docker/d-stunnel/src/master/Makefile

	~~See rsyncd~~.conf in https://charlesreid1.com:3000/~~rpi~~/pi-~~transmission~~		Build rsync stunnel docker container script: https://charlesreid1.com:3000/docker/d-stunnel/src/master/build_rsync.sh

			The build docker container script actually uses the Dockerfile, which assembles the various files that are needed to run both stunnel and rsync. The build script updates the port number in both the Dockerfile and in the rsync stunnel configuration file using sed, then bakes these files into the final container image using docker build.

			Dockerfile_rsync_stunnel: https://charlesreid1.com:3000/docker/d-stunnel/src/master/Dockerfile_rsync_stunnel

			Universal rsync stunnel configuration file: https://charlesreid1.com:3000/docker/d-stunnel/src/master/stunnel.server.rsync.conf

			Finally, the Makefile calls the run script and passes the port number to the run script, which hooks up the necessary ports between the host and the container, mounts the necessary volumes, and sets up the docker network interface (as well as running the container in the foreground or background).

			Run rsync stunnel container: https://charlesreid1.com:3000/docker/d-stunnel/src/master/run_rsync.sh

	===Running Rsync Server===		===Running Rsync Server===

Admin at 05:37, 9 April 2017

2017-04-09T05:37:31Z

← Older revision		Revision as of 05:37, 9 April 2017
Line 2:		Line 2:

	NOTE: I was not able to get this working reliably on port 273, but was able to get stunnel+rsync working reliably over port 443. Mileage may vary.		NOTE: I was not able to get this working reliably on port 273, but was able to get stunnel+rsync working reliably over port 443. Mileage may vary.

			=Overview/Approach=

			Used the following approach:
			* Reorganized all of the files in the repository so that each service had its own configuration and build sequence
			* Makefile was entry point: make rsync or make ssh
			* The Makefile would set the port, and feed that as an argument to each script.
			* Build script, run script, open firewall script
			* This enabled flexibility in port number, and enabled switching from 273 to 443 more easily
			* Better organization of stunnel - since each service requires different configurations and ports should be easy to switch in and out.

	=Server=		=Server=

Admin at 05:33, 9 April 2017

2017-04-09T05:33:02Z

← Older revision		Revision as of 05:33, 9 April 2017
Line 1:		Line 1:
	This page was immensely helpful: http://www.netbits.us/docs/stunnel_rsync.html		This page was immensely helpful: http://www.netbits.us/docs/stunnel_rsync.html

			NOTE: I was not able to get this working reliably on port 273, but was able to get stunnel+rsync working reliably over port 443. Mileage may vary.

	=Server=		=Server=

Admin at 05:17, 5 April 2017

2017-04-05T05:17:01Z

← Older revision		Revision as of 05:17, 5 April 2017
Line 235:		Line 235:

	[[Category:Rsync]]		[[Category:Rsync]]

			[[Category:Stunnel.conf]]

Admin at 09:25, 1 April 2017

2017-04-01T09:25:30Z

← Older revision		Revision as of 09:25, 1 April 2017
Line 1:		Line 1:
			This page was immensely helpful: http://www.netbits.us/docs/stunnel_rsync.html

	=Server=		=Server=

Admin: /* Debugging rsync */

2017-04-01T08:58:54Z

Debugging rsync

← Older revision		Revision as of 08:58, 1 April 2017
Line 227:		Line 227:

	By running <code>tail -f /var/log/syslog</code> on the server in a window, then running rsync over stunnel commands in another, you should see messages about rsync activity showing up in the syslog. This should also give you more helpful and descriptive information when things go wrong, and help you diagnose the error.		By running <code>tail -f /var/log/syslog</code> on the server in a window, then running rsync over stunnel commands in another, you should see messages about rsync activity showing up in the syslog. This should also give you more helpful and descriptive information when things go wrong, and help you diagnose the error.




	* Debugging:
	** How to debug stunnel
	** How to debug rsync
	** Workflow for checking connections while running commands





	=Flags=		=Flags=

Admin: /* Stunnel Client for Rsync */

2017-04-01T08:58:40Z

Stunnel Client for Rsync

← Older revision		Revision as of 08:58, 1 April 2017
Line 153:		Line 153:
	See stunnel for rsync config file for Raspberry Pi clients: https://charlesreid1.com:3000/rpi/pi-stunnel/src/master/stunnel.rpiclient.rsync_over_273.conf		See stunnel for rsync config file for Raspberry Pi clients: https://charlesreid1.com:3000/rpi/pi-stunnel/src/master/stunnel.rpiclient.rsync_over_273.conf

	==Stunnel Client ~~for Rsync~~==		==Stunnel Client==

	===Configuring Stunnel Client for Rsync===		===Configuring Stunnel Client for Rsync===

Admin: /* Rsync */

2017-04-01T08:58:23Z

Rsync

← Older revision		Revision as of 08:58, 1 April 2017
Line 106:		Line 106:
	This describes the client configuration required to get rsync working over stunnel.		This describes the client configuration required to get rsync working over stunnel.

	==Rsync==		==Rsync Client==

	The client's rsync will operate, as usual, on local port 873. Behind the scenes, stunnel will transparently map that port to a remote rsync daemon/server, so it will appear to the rsync client that it is communicating with a local rsync daemon/server.		The client's rsync will operate, as usual, on local port 873. Behind the scenes, stunnel will transparently map that port to a remote rsync daemon/server, so it will appear to the rsync client that it is communicating with a local rsync daemon/server.

	===Configuring Rsync===		===Configuring Rsync Client===

	No special rsync setup is needed for the client. All we have to do is point the rsync client to the rsync server, and specify one of the modules in our configuration file. The rsync daemon running on the remote server will take care of the rest.		No special rsync setup is needed for the client. All we have to do is point the rsync client to the rsync server, and specify one of the modules in our configuration file. The rsync daemon running on the remote server will take care of the rest.

	===Running Rsync===		===Running Rsync Client===

	The client does not need to run the rsync daemon, only the server does. When you are on the client, you can just run rsync from the command line, and pass it the location of the rsync server (which is localhost port 873). Stunnel takes care of the rest, so the rsync daemon on the remote server appears to be just another local service.		The client does not need to run the rsync daemon, only the server does. When you are on the client, you can just run rsync from the command line, and pass it the location of the rsync server (which is localhost port 873). Stunnel takes care of the rest, so the rsync daemon on the remote server appears to be just another local service.