Bug 53024 – Veyon performance not acceptable

Bug 53024 - Veyon performance not acceptable


Summary:	Veyon performance not acceptable

Status:	RESOLVED DUPLICATE of bug 53055

Product:	UCS@school
Classification:	Unclassified
Component:	UMC - Computer room
Version:	unspecified
Hardware:	Other Linux

Importance:	P5 normal (vote)
Target Milestone:	---
Assigned To:	UCS@school maintainers
QA Contact:

URL:
Keywords:

Depends on:	52425
Blocks:
	Show dependency tree / graph

Reported:	2021-03-31 12:32 CEST by Dirk Schnick
Modified:	2021-04-14 12:26 CEST (History)
CC List:	7 users (show)

See Also:
What kind of report is it?:	Bug Report
What type of bug is this?:	5: Major Usability: Impairs usability in key scenarios
Who will be affected by this bug?:	4: Will affect most installed domains
How will those affected feel about the bug?:	3: A User would likely not purchase the product
User Pain:	0.343
Enterprise Customer affected?:
School Customer affected?:	Yes
ISV affected?:
Waiting Support:
Flags outvoted (downgraded) after PO Review:
Ticket number:	2021032921000513
Bug group (optional):
Max CVSS v3 score:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.

Description Dirk Schnick

2021-03-31 12:32:28 CEST

The customer tried the new veyon way and the performance is very bad. See attached video.
In the code I can see that veyon always ping the hosts and ignores the UCR implemented with 52425.




+++ This bug was initially created as a clone of Bug #52425 +++

+++ This bug was initially created as a clone of Bug #51976 +++

Laptops being added to the computerroom will always appear "offline" when there are two MACs and IPs assigned and they use WiFi instead of Ethernet.

Laptops frequently have mutliple NICs (Ethernet and WiFi) and thus are configured accordingly. But in schools they are frequently only connected to the WiFi when in use and as the Ethernet interface is not reachable they will apear "offline" even though they are not.

Computerroom should check both (or all) assigned IPs.


---------------

The implemented solution is causing massive waiting times due to the timeouts of "ping" if the target IP is not reachable. We need to find a solution for this problem.

Comment 5 Nico Gulden

2021-04-14 12:26:57 CEST


*** This bug has been marked as a duplicate of bug 53055 ***