| Next revision | Previous revision |
| blocks:server:network-faq [2022-03-29 11:54] – created admin | blocks:server:network-faq [2026-11-13 10:17] (current) – [Does Blocks support single-sign-on solutions, such as Active Directory?] admin |
|---|
| |
| ====What kind of network traffic does Blocks cause?==== | ====What kind of network traffic does Blocks cause?==== |
| Blocks typically run over regular Ethernet networks (or wifi, if required). It uses industry standard IP protocols (UDP and TCP). Most traffic is of "web browser" type, with the exception being more exotic optional devices, such as MODBUS, ArtNET, WATCHOUT, etc. | Blocks should generally use wired (Ethernet) network, but can use or wifi if required and of sufficient quality and bandwidth. Blocks uses industry standard protocols such as HTTP, TCP and UDP. Most traffic is of "web browser" type (HTTP/HTTPS). |
| |
| Some devices or functions use UDP broadcasts. E.g., wake-on-lan used by [[blocks:porteus_kiosk|PIXILAB Player]], some smart displays and [[https://dataton.com/watchout|Dataton WATCHOUT]] as well as ArtNET, or multicast (Dataton WATCHOUT). If used, such features must be allowed on the network for those functions to work properly. | PIXILAB Player (and possibly other devices, such as some some "smart displays" with built-in players) may use wake-on-lan broadcast message to be powered up. Other optional devices based on ArtNET, or media servers (such as Dataton WATCHOUT), etc, also may use multicast or broadcast. In those cases, broacasts or multicasts must be allowed on the network for those functions to work properly. |
| |
| ====Is DHCP and local DNS required for using digital guide features?==== | ====Is DHCP and local DNS required for using digital guide features?==== |
| |
| ====Does Blocks support single-sign-on solutions, such as Active Directory?==== | ====Does Blocks support single-sign-on solutions, such as Active Directory?==== |
| Yes. Learn more about how to configure various SSO-providers here: | Yes. Learn more about how to configure SSO-providers here: |
| |
| * [[blocks:sso:adfs|ADFS]]. | * [[blocks:sso:adfs|Microsoft Active Directory]]. |
| * [[blocks:sso:okta|OKTA]] | |
| * [[blocks:sso:keycloak|Keycloak]] | * [[blocks:sso:keycloak|Keycloak]] |
| |
| ====Is there any support for remote management?==== | ====Is there any support for remote management?==== |
| We're including [[https://anydesk.com/en|Anydesk]], an excellent 3rd party remote management program, on our Linux server image. By default, [[blocks:anydesk|Anydesk]] is disabled. It can be enabled //on demand// or //on server start// (e.g., for unattended access). If you want to use Anydesk, find its port requirements and other details under "Which ports does AnyDesk use?" here: https://support.anydesk.com/FAQ | We're including [[https://anydesk.com/en|Anydesk]], an excellent 3rd party remote management program, on our Linux server image. By default, [[blocks:anydesk|Anydesk]] is disabled. It can be enabled //on demand// or //on server start// (e.g., for unattended access). If you want to use Anydesk, find its port requirements and other details under "Which ports does AnyDesk use?" here: https://support.anydesk.com/FAQ |