You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: addons/internet-access-control.rst
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -47,8 +47,8 @@ Linux
47
47
48
48
For both operating systems, the backend configuration is identical. In general different modes are available. The mode selection depends on the network environment and the desired blocking behavior.
49
49
50
-
Block all outbound traffic for TCP ports
51
-
This is the default mode and should work in most environments. In this mode the Veyon Service adds special rules to the firewall which block any traffic to the configured ports. Use this mode if blocking the TCP ports 80/443 and one or multiple custom ports (separated by space) is sufficient. To block all traffic use the second mode.
50
+
Block all outbound traffic for TCP and UDP ports
51
+
This is the default mode and should work in most environments. In this mode the Veyon Service adds special rules to the firewall which block any traffic to the configured ports. Use this mode if blocking the TCP and UDP ports 80/443 and one or multiple custom ports (separated by space) is sufficient. To block all traffic use the second mode.
52
52
53
53
Block all outbound traffic to non-local subnets
54
54
In this mode, all network traffic directed to networks outside the local subnets is blocked. On Windows, the Veyon service temporarily changes the configuration of all firewall profiles (domain, private, public) to “ Outbound connections that do not match a rule are blocked”. If :guilabel:`Exceptions` are configured, appropriate rules are added to allow access to these networks, hosts or ports. This can be used, for example, to preserve access to the intranet and other internally hosted platforms. External websites can also be defined as exceptions here under certain circumstances, but the addresses of all servers/CDNs from which the website loads resources must then also be specified.
Copy file name to clipboardExpand all lines: addons/network-discovery.rst
+14-1Lines changed: 14 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -37,7 +37,7 @@ Finally, the network object directory backend needs to be changed to *Network di
37
37
:align:center
38
38
39
39
Change network object directory backend to Network Discovery
40
-
40
+
41
41
Now you can start Veyon Master and should see the computers in your network running a Veyon Server. Depending on the size of the subnet or network range(s), the initial scan process might take a while (up to 1-2 minutes in the worst case).
42
42
43
43
Options
@@ -118,6 +118,19 @@ The same substring extraction is possible for computer names as well (except for
118
118
119
119
Please refer to the `Wikipedia article on regular expressions <https://en.wikipedia.org/wiki/Regular_expression>`_ for more information on the concept, syntax and available pattern options.
120
120
121
+
Advanced settings
122
+
-----------------
123
+
124
+
In the :guilabel:`Advanced` view mode several options for fine-tuning the behavior are available:
125
+
126
+
Property for generating persistent network object IDs
127
+
Per default Veyon calculates unique internal IDs for each network object based on multiple information such as hostname, computer name etc. These IDs are used when saving and loading custom computer positions in Veyon Master. In order to use fixed positions for computers based on their host or computer name (especially if the computer name is configured to equal e.g. the user name), you can choose the corresponding option.
128
+
129
+
Data retrieval timeout
130
+
This setting influences the maximum time Network Discovery waits to obtain the computer name via DNS or to query certain session-related characteristics from a remote computer.
Copy file name to clipboardExpand all lines: admin/reference.rst
+7-2Lines changed: 7 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -186,13 +186,18 @@ Autostart
186
186
187
187
.. _RefSessions:
188
188
189
-
.. index:: Sessions, Session settings, Terminal server, Remote desktop server, RDP, Single session mode, Multi session mode
189
+
.. index:: Sessions, Session settings, Terminal server, Remote desktop server, RDP, Local session mode, Active session mode, Multi session mode
190
190
191
-
Single session mode (create server instance for local/physical session only)
191
+
Local session mode (single server instance for primary local session)
192
192
Choose this option for single-user scenarios, i.e. each user is working locally on a dedicated computer. In this mode the Veyon Service will always start exactly one server instance for the primary session of the computer, e.g. the console session on Windows.
193
193
194
194
**Default:** *enabled*
195
195
196
+
Active session mode (single server instance for active local or remote session)
197
+
Choose this option if you always want to view or access the active session, no matter if it's a local or remote session or the session type changes in inbetween. If e.g. a local session is being taken over via Remote Desktop, the Veyon Server instance is restarted inside the remote session and switches back to the local session as soon as the remote session is terminated.
198
+
199
+
**Default:** *disabled*
200
+
196
201
.. _RefMultiSessionMode:
197
202
198
203
Multi session mode (for terminal and remote desktop servers)
0 commit comments