SciStream at APS - Revision history

Tguruswamy: /* Outbound Request ("Client side": 192.168.150.2) */

2025-04-14T18:29:31Z

Outbound Request ("Client side": 192.168.150.2)

← Older revision		Revision as of 18:29, 14 April 2025
Line 49:		Line 49:
	=== Outbound Request ("Client side": 192.168.150.2) ===		=== Outbound Request ("Client side": 192.168.150.2) ===

	Purpose: Sets up the sending end of the tunnel. This establishes a listener on the ~~local~~ SciStream endpoint that waits for incoming connections from the client application and forwards that data to the other SciStream endpoint.		Purpose: Sets up the sending end of the tunnel. This establishes a listener on the specified SciStream endpoint that waits for incoming connections from the client application and forwards that data to the other SciStream endpoint.

	<pre>podman run --rm --net=host -v ./server2:/scistream --entrypoint=s2uc castroflaviojr/scistream:1.2.1 outbound-request --remote_ip 192.168.150.1 --s2cs 192.168.150.2:5000 --receiver_ports 5100 --num_conn 1 --server_cert=/scistream/server.crt bd9f1a7e-04d7-11f0-b44c-946dae415862 192.168.150.1:5100		<pre>podman run --rm --net=host -v ./server2:/scistream --entrypoint=s2uc castroflaviojr/scistream:1.2.1 outbound-request --remote_ip 192.168.150.1 --s2cs 192.168.150.2:5000 --receiver_ports 5100 --num_conn 1 --server_cert=/scistream/server.crt bd9f1a7e-04d7-11f0-b44c-946dae415862 192.168.150.1:5100

Tguruswamy: /* Inbound Request ("Server side": 192.168.150.1) */

2025-04-14T18:29:20Z

Inbound Request ("Server side": 192.168.150.1)

← Older revision		Revision as of 18:29, 14 April 2025
Line 20:		Line 20:

	=== Inbound Request ("Server side": 192.168.150.1) ===		=== Inbound Request ("Server side": 192.168.150.1) ===
	'''Purpose:''' Sets up the receiving end of the tunnel. This establishes a listener that waits for incoming connections from the outbound request (other SciStream endpoint) and it forwards this connection to the <remote_ip>:<receiver_ports>.		'''Purpose:''' Sets up the receiving end of the tunnel. This establishes a listener on the specified SciStream endpoint that waits for incoming connections from the outbound request (other SciStream endpoint) and it forwards this connection to the <remote_ip>:<receiver_ports>.

	<pre>podman run --rm --net=host -v ./server1:/scistream --entrypoint=s2uc castroflaviojr/scistream:1.2.1 inbound-request --remote_ip 192.168.150.1 --s2cs 192.168.150.1:5000 --receiver_ports 5300 --num_conn 1 --server_cert=/scistream/server.crt		<pre>podman run --rm --net=host -v ./server1:/scistream --entrypoint=s2uc castroflaviojr/scistream:1.2.1 inbound-request --remote_ip 192.168.150.1 --s2cs 192.168.150.1:5000 --receiver_ports 5300 --num_conn 1 --server_cert=/scistream/server.crt

Tguruswamy: /* Inbound Request ("Server side": 192.168.150.1) */

2025-04-14T18:28:57Z

Inbound Request ("Server side": 192.168.150.1)

← Older revision		Revision as of 18:28, 14 April 2025
Line 20:		Line 20:

	=== Inbound Request ("Server side": 192.168.150.1) ===		=== Inbound Request ("Server side": 192.168.150.1) ===
	'''Purpose:''' Sets up the receiving end of the tunnel. This establishes a listener that waits for incoming connections from the outbound request and it forwards this connection to the <remote_ip>:<receiver_ports>.		'''Purpose:''' Sets up the receiving end of the tunnel. This establishes a listener that waits for incoming connections from the outbound request (other SciStream endpoint) and it forwards this connection to the <remote_ip>:<receiver_ports>.

	<pre>podman run --rm --net=host -v ./server1:/scistream --entrypoint=s2uc castroflaviojr/scistream:1.2.1 inbound-request --remote_ip 192.168.150.1 --s2cs 192.168.150.1:5000 --receiver_ports 5300 --num_conn 1 --server_cert=/scistream/server.crt		<pre>podman run --rm --net=host -v ./server1:/scistream --entrypoint=s2uc castroflaviojr/scistream:1.2.1 inbound-request --remote_ip 192.168.150.1 --s2cs 192.168.150.1:5000 --receiver_ports 5300 --num_conn 1 --server_cert=/scistream/server.crt

Tguruswamy: /* Outbound Request ("Client side": 192.168.150.2) */

2025-04-14T18:28:33Z

Outbound Request ("Client side": 192.168.150.2)

← Older revision		Revision as of 18:28, 14 April 2025
Line 48:		Line 48:

	=== Outbound Request ("Client side": 192.168.150.2) ===		=== Outbound Request ("Client side": 192.168.150.2) ===

			Purpose: Sets up the sending end of the tunnel. This establishes a listener on the local SciStream endpoint that waits for incoming connections from the client application and forwards that data to the other SciStream endpoint.

	<pre>podman run --rm --net=host -v ./server2:/scistream --entrypoint=s2uc castroflaviojr/scistream:1.2.1 outbound-request --remote_ip 192.168.150.1 --s2cs 192.168.150.2:5000 --receiver_ports 5100 --num_conn 1 --server_cert=/scistream/server.crt bd9f1a7e-04d7-11f0-b44c-946dae415862 192.168.150.1:5100		<pre>podman run --rm --net=host -v ./server2:/scistream --entrypoint=s2uc castroflaviojr/scistream:1.2.1 outbound-request --remote_ip 192.168.150.1 --s2cs 192.168.150.2:5000 --receiver_ports 5100 --num_conn 1 --server_cert=/scistream/server.crt bd9f1a7e-04d7-11f0-b44c-946dae415862 192.168.150.1:5100
Line 55:		Line 57:
	** <code>--remote_ip</code>: The eventual destination IP address we want data to be forwarded to.		** <code>--remote_ip</code>: The eventual destination IP address we want data to be forwarded to.
	** <code>--s2cs</code>: The IP and port for the local s2cs scistream control server.		** <code>--s2cs</code>: The IP and port for the local s2cs scistream control server.
	** <code>--receiver_ports</code>: Local port which the client application will connect to.		** <code>--receiver_ports</code>: Local port which the client application will connect to (i.e. client should connect to {s2cs_ip:receiver_port}).
	** <code>--num_conn</code>: Number of connections to establish.		** <code>--num_conn</code>: Number of connections to establish.
	** <code>--server_cert</code>: Path to the server certificate for TLS.		** <code>--server_cert</code>: Path to the server certificate for TLS.

Fcastro at 18:21, 14 April 2025

2025-04-14T18:21:23Z

← Older revision		Revision as of 18:21, 14 April 2025
Line 12:		Line 12:
	'''Client side (Outbound Request):''' Source that sends data. TCP client that actively creates new connections		'''Client side (Outbound Request):''' Source that sends data. TCP client that actively creates new connections

	* Your client application connects to the local port (5100) on the client machine		** Your client application connects to the local port (5100) on the client machine
	** The SciStream outbound request forwards this connection through the secure tunnel		** The SciStream outbound request forwards this connection through the secure tunnel
	** The SciStream inbound request receives the forwarded connection		** The SciStream inbound request receives the forwarded connection

Fcastro: /* How data flows through the tunnel */

2025-04-14T18:20:06Z

How data flows through the tunnel

← Older revision		Revision as of 18:20, 14 April 2025
Line 6:		Line 6:

	== How data flows through the tunnel ==		== How data flows through the tunnel ==

	The tunnel consists of parts that work together:		The tunnel consists of parts that work together:

Fcastro at 18:19, 14 April 2025

2025-04-14T18:19:31Z

← Older revision		Revision as of 18:19, 14 April 2025
Line 1:		Line 1:
	= SciStream Tunnel Setup Guide =		= SciStream Tunnel Setup Guide =

	This guide provides step-by-step instructions on how to tunnel a connection through SciStream using <code>s2uc</code> running from a container. This setup involves two endpoints, each running on separate hosts, to establish a secure tunnel for forwarding packets.		This guide provides step-by-step instructions on how to tunnel a connection through SciStream using <code>s2uc</code> running from a container. This setup involves two endpoints, each running on separate hosts, to establish a secure tunnel(TLS) for forwarding packets.

	Scistream TLS certificates are on the test servers at <code>/local/scistream</code>. Use the folder corresponding to the server -- i.e. on server1, always use /server1; on server2, use /server2.		Scistream's API TLS certificates are on the test servers at <code>/local/scistream</code>. Use the folder corresponding to the server -- i.e. on server1, always use /server1; on server2, use /server2.

			== How data flows through the tunnel ==
			The tunnel consists of parts that work together:

			'''Server side (Inbound Request):''' Destination that receives data. TCP server listens for connections.
			'''Client side (Outbound Request):''' Source that sends data. TCP client that actively creates new connections

			* Your client application connects to the local port (5100) on the client machine
			** The SciStream outbound request forwards this connection through the secure tunnel
			** The SciStream inbound request receives the forwarded connection
			** Data is delivered to your server application listening on the receiver port (5300)

	== Request Configuration ==		== Request Configuration ==

	=== Inbound Request ("Server side": 192.168.150.1) ===		=== Inbound Request ("Server side": 192.168.150.1) ===
			'''Purpose:''' Sets up the receiving end of the tunnel. This establishes a listener that waits for incoming connections from the outbound request and it forwards this connection to the <remote_ip>:<receiver_ports>.

	<pre>podman run --rm --net=host -v ./server1:/scistream --entrypoint=s2uc castroflaviojr/scistream:1.2.1 inbound-request --remote_ip 192.168.150.1 --s2cs 192.168.150.1:5000 --receiver_ports 5300 --num_conn 1 --server_cert=/scistream/server.crt		<pre>podman run --rm --net=host -v ./server1:/scistream --entrypoint=s2uc castroflaviojr/scistream:1.2.1 inbound-request --remote_ip 192.168.150.1 --s2cs 192.168.150.1:5000 --receiver_ports 5300 --num_conn 1 --server_cert=/scistream/server.crt

Tguruswamy: /* SciStream Tunnel Setup Guide */

2025-04-14T15:22:26Z

SciStream Tunnel Setup Guide

← Older revision		Revision as of 15:22, 14 April 2025
Line 3:		Line 3:
	This guide provides step-by-step instructions on how to tunnel a connection through SciStream using <code>s2uc</code> running from a container. This setup involves two endpoints, each running on separate hosts, to establish a secure tunnel for forwarding packets.		This guide provides step-by-step instructions on how to tunnel a connection through SciStream using <code>s2uc</code> running from a container. This setup involves two endpoints, each running on separate hosts, to establish a secure tunnel for forwarding packets.

	Scistream ~~test server~~ certificates are on the test servers at <code>/local/scistream</code>. Use the folder corresponding to the server -- i.e. on server1, always use /server1; on server2, use /server2.		Scistream TLS certificates are on the test servers at <code>/local/scistream</code>. Use the folder corresponding to the server -- i.e. on server1, always use /server1; on server2, use /server2.

	== Request Configuration ==		== Request Configuration ==

Tguruswamy: remove server names

2025-04-14T15:21:59Z

remove server names

← Older revision		Revision as of 15:21, 14 April 2025
Line 3:		Line 3:
	This guide provides step-by-step instructions on how to tunnel a connection through SciStream using <code>s2uc</code> running from a container. This setup involves two endpoints, each running on separate hosts, to establish a secure tunnel for forwarding packets.		This guide provides step-by-step instructions on how to tunnel a connection through SciStream using <code>s2uc</code> running from a container. This setup involves two endpoints, each running on separate hosts, to establish a secure tunnel for forwarding packets.

	Scistream test server certificates are on ~~updraft1/2~~ at <code>/local/scistream</code>. Use the folder corresponding to the server -- i.e. on ~~updraft1~~, always use /server1; on ~~updraft2~~, use /server2.		Scistream test server certificates are on the test servers at <code>/local/scistream</code>. Use the folder corresponding to the server -- i.e. on server1, always use /server1; on server2, use /server2.

	== Request Configuration ==		== Request Configuration ==

Tguruswamy: add cert location

2025-04-09T19:22:09Z

add cert location

← Older revision		Revision as of 19:22, 9 April 2025
Line 3:		Line 3:
	This guide provides step-by-step instructions on how to tunnel a connection through SciStream using <code>s2uc</code> running from a container. This setup involves two endpoints, each running on separate hosts, to establish a secure tunnel for forwarding packets.		This guide provides step-by-step instructions on how to tunnel a connection through SciStream using <code>s2uc</code> running from a container. This setup involves two endpoints, each running on separate hosts, to establish a secure tunnel for forwarding packets.

	== ~~Endpoint~~ Configuration ==		Scistream test server certificates are on updraft1/2 at <code>/local/scistream</code>. Use the folder corresponding to the server -- i.e. on updraft1, always use /server1; on updraft2, use /server2.

			== Request Configuration ==

	=== Inbound Request ("Server side": 192.168.150.1) ===		=== Inbound Request ("Server side": 192.168.150.1) ===