From 68f9976b9258796daf49124b7f31a67a18b98513 Mon Sep 17 00:00:00 2001 From: "Steinar H. Gunderson" Date: Wed, 29 Aug 2018 09:34:00 +0200 Subject: [PATCH] Some README updates. --- README | 22 ++++++++++++++-------- 1 file changed, 14 insertions(+), 8 deletions(-) diff --git a/README b/README index 0712cbd..e9520d3 100644 --- a/README +++ b/README @@ -18,8 +18,10 @@ A short list of features: - Multicast support, both for sending and receiving (supports only protocols that can go over UDP, e.g. MPEG-TS). Supports both ASM and SSM. - TLS output support, through the TLSe library (requires libtomcrypt) - and the Linux kernel's kTLS (Linux 4.13 or newer). There are a few + and the Linux kernel's kTLS (Linux 4.17 or newer). There are a few limitations; see below. + - fMP4 (HLS) output support, generating playlists on-the-fly. Note that this + requires some extra metadata currently only set by Nageru (not VLC). - IPv4 support. Yes, Cubemap even supports (some) legacy protocols. @@ -38,6 +40,9 @@ access mux, like this: Then look through cubemap.config.sample, copy it to cubemap.config, compile and start cubemap. +Nageru, my free video mixer, can also produce Metacube streams natively. +See the manual at https://nageru.sesse.net/doc/ for more information. + To upgrade cubemap (after you've compiled a new binary), or to pick up new config: @@ -54,13 +59,14 @@ Cubemap supports TLS on output, so that you can play video on TLS web sites without issues with mixed content. TLS on input streams is not (yet) supported. -TLS requires kTLS, ie., Linux >= 4.13 with CONFIG_TLS enabled. Only cipher -suites supported by kTLS is supposed, ie., AES-128-GCM (if no such cipher -suite is available, the connection will be aborted). If the server is restarted -before the key exchange for a connection is completed, that connection will -not survive the restart, unlike all other connections. (This is a TLSe -limitation.) You can have different certificates on different ports (and -have separate ports for TLS and non-TLS), but SNI is not yet supported. +TLS requires kTLS for both send and receive, ie., Linux >= 4.17 with CONFIG_TLS +enabled. Only cipher suites supported by kTLS is supposed, ie., AES-128-GCM +(if no such cipher suite is available, the connection will be aborted). If the +server is restarted before the key exchange for a connection is completed, +that connection will not survive the restart, unlike all other connections. +(This is a TLSe limitation.) You can have different certificates on different +ports (and have separate ports for TLS and non-TLS), but SNI is not yet +supported. Munin plugins: -- 2.39.2