UDP over SSH - Revision history

HR at 11:52, 21 March 2021

2021-03-21T11:52:29Z

← Older revision		Revision as of 11:52, 21 March 2021
Line 48:		Line 48:

	Now our local UDP traffic on port 6454 is tunneled (and forwarded) to the remote device at 10.0.0.2 .		Now our local UDP traffic on port 6454 is tunneled (and forwarded) to the remote device at 10.0.0.2 .

			== See also ==
			*[[SSH over Tor]] (UDP over SSH over Tor is also possible)

	== References ==		== References ==

HR at 13:55, 5 February 2021

2021-02-05T13:55:32Z

← Older revision		Revision as of 13:55, 5 February 2021
Line 1:		Line 1:
	~~Forward~~ UDP traffic on a specific port (like Art-Net <ref>[[wikipedia:Art-Net]]</ref>) to a remote client via SSH <ref>[[wikipedia:SSH_(Secure_Shell)]]</ref>.		Tunnel UDP traffic on a specific port (like Art-Net <ref>[[wikipedia:Art-Net]]</ref>) to a remote client via SSH <ref>[[wikipedia:SSH_(Secure_Shell)]]</ref>.

	== Background ==		== Background ==
Line 42:		Line 42:


	On our local device we configure socat to listen on local UDP port 6454 and forward the traffic to local TCP port 7000, where the SSH port forward is configured:		On our local device we configure socat to listen on local UDP port 6454 and forward the traffic to local TCP port 7000, where the SSH port forward is configured, which tunnels our UDP datagrams to the remote computer:

	sudo socat UDP-LISTEN:6454 TCP:localhost:7000		sudo socat UDP-LISTEN:6454 TCP:localhost:7000


	Now our local UDP traffic on port 6454 is tunneled to the remote device at 10.0.0.2 .		Now our local UDP traffic on port 6454 is tunneled (and forwarded) to the remote device at 10.0.0.2 .

	== References ==		== References ==

HR at 13:50, 5 February 2021

2021-02-05T13:50:50Z

← Older revision		Revision as of 13:50, 5 February 2021
Line 1:		Line 1:
	Forward UDP traffic on a specific port (like Art-Net) to a remote client via SSH.		Forward UDP traffic on a specific port (like Art-Net <ref>[[wikipedia:Art-Net]]</ref>) to a remote client via SSH <ref>[[wikipedia:SSH_(Secure_Shell)]]</ref>.

	== Background ==		== Background ==
Line 8:		Line 8:

	SSH is based on TCP. Encapsulating UDP datagrams in TCP packets might have unwanted side effects. While a UDP datagram gets dropped if a transmission error occurs, TCP packets will be retransmitted which may cause unwanted delays. If such a delay is of any significance is open for discussion.		SSH is based on TCP. Encapsulating UDP datagrams in TCP packets might have unwanted side effects. While a UDP datagram gets dropped if a transmission error occurs, TCP packets will be retransmitted which may cause unwanted delays. If such a delay is of any significance is open for discussion.

			Using DTLS <ref>[[wikipedia:Datagram_Transport_Layer_Security]]</ref> might be a better approach to encrypt UDP traffic.

	== Diagram ==		== Diagram ==
Line 23:		Line 25:
	===== Requirements =====		===== Requirements =====
	* socat		* socat
			* SSH
	* SSH <ref>[[wikipedia:SSH_(Secure_Shell)]]</ref>
	* remote computer that can receive SSH connections (e.g. Raspberry Pi) and whose SSH port is exposed to the internet (e.g. via port forwarding).		* remote computer that can receive SSH connections (e.g. Raspberry Pi) and whose SSH port is exposed to the internet (e.g. via port forwarding).

HR: /* Implementations */

2021-02-05T01:32:29Z

Implementations

← Older revision		Revision as of 01:32, 5 February 2021
Line 24:		Line 24:
	* socat		* socat
	* SSH <ref>[[wikipedia:SSH_(Secure_Shell)]]</ref>		* SSH <ref>[[wikipedia:SSH_(Secure_Shell)]]</ref>
	* remote computer that can receive SSH connections (e.g. Raspberry Pi) and whose SSH port is exposed to the internet.		* remote computer that can receive SSH connections (e.g. Raspberry Pi) and whose SSH port is exposed to the internet (e.g. via port forwarding).

	===== Example =====		===== Example =====

	Connect to the remote computer (example.com) via SSH and forward our local TCP port 7000 to the remote computer:		Connect to the remote computer (example.com) via SSH and forward our local TCP port 7000 to the remote computer's local TCP port 7000:

	ssh -L 7000:localhost:7000 example.com		ssh -L 7000:localhost:7000 example.com
Line 45:		Line 45:


	Now our local UDP traffic on port 6454 is tunneled to the remote device at 10.0.0.2 .		Now our local UDP traffic on port 6454 is tunneled to the remote device at 10.0.0.2 .


	== References ==		== References ==

HR at 11:57, 4 February 2021

2021-02-04T11:57:48Z

← Older revision		Revision as of 11:57, 4 February 2021
Line 1:		Line 1:
⚫	== ~~Abstract~~ ==

	Forward UDP traffic on a specific port (like Art-Net) to a remote client via SSH.		Forward UDP traffic on a specific port (like Art-Net) to a remote client via SSH.

Line 6:		Line 4:

	This comes in handy if you don't want to expose the remote device's UDP port directly to the internet and/or you want the connection through the Internet to be encrypted.		This comes in handy if you don't want to expose the remote device's UDP port directly to the internet and/or you want the connection through the Internet to be encrypted.

		⚫	== Caveat ==

			SSH is based on TCP. Encapsulating UDP datagrams in TCP packets might have unwanted side effects. While a UDP datagram gets dropped if a transmission error occurs, TCP packets will be retransmitted which may cause unwanted delays. If such a delay is of any significance is open for discussion.

	== Diagram ==		== Diagram ==

HR: Typo

2021-02-02T17:18:00Z

Typo

← Older revision		Revision as of 17:18, 2 February 2021
Line 1:		Line 1:
	== Abstract ==		== Abstract ==

	Forward UDP traffic on a specific port (like ~~Artnet~~) to a remote client via SSH.		Forward UDP traffic on a specific port (like Art-Net) to a remote client via SSH.

	== Background ==		== Background ==

HR: /* Abstract */

2021-02-02T07:05:40Z

Abstract

← Older revision		Revision as of 07:05, 2 February 2021
Line 1:		Line 1:
	== Abstract ==		== Abstract ==

	Forward UDP traffic on a specific port to a remote client via SSH.		Forward UDP traffic on a specific port (like Artnet) to a remote client via SSH.

	== Background ==		== Background ==

HR: Created page with "== Abstract == Forward UDP traffic on a specific port to a remote client via SSH. == Background == This comes in handy if you don't want to expose the remote device's UDP p..."

2021-02-01T19:10:30Z

Created page with "== Abstract == Forward UDP traffic on a specific port to a remote client via SSH. == Background == This comes in handy if you don't want to expose the remote device's UDP p..."

New page

== Abstract ==

Forward UDP traffic on a specific port to a remote client via SSH.

== Background ==

This comes in handy if you don't want to expose the remote device's UDP port directly to the internet and/or you want the connection through the Internet to be encrypted.

== Diagram ==

[[File:UDP over SSH Diagram 02.png]]

== Implementations ==

=== Linux ===

==== Socat ====

Socat <ref>[[wikipedia:Socat]]</ref> is a command-line utility to read from and write to TCP and UDP network connections.

===== Requirements =====
* socat
* SSH <ref>[[wikipedia:SSH_(Secure_Shell)]]</ref>
* remote computer that can receive SSH connections (e.g. Raspberry Pi) and whose SSH port is exposed to the internet.

===== Example =====

Connect to the remote computer (example.com) via SSH and forward our local TCP port 7000 to the remote computer:

ssh -L 7000:localhost:7000 example.com

'''Note:''' if you want to forward a port in the 1 - 1023 range you need root privileges (sudo).

Via the SSH shell on the remote computer (example.com) configure socat to listen on TCP port 7000 and forward the traffic (from port 7000) to IP address 10.0.0.2 on UDP port 6454:

sudo socat TCP-LISTEN:7000,fork UDP6:10.0.0.2:6454

On our local device we configure socat to listen on local UDP port 6454 and forward the traffic to local TCP port 7000, where the SSH port forward is configured:

sudo socat UDP-LISTEN:6454 TCP:localhost:7000

Now our local UDP traffic on port 6454 is tunneled to the remote device at 10.0.0.2 .

== References ==
<div class="references-small"> <references /> </div>

[[Category:Networking]]