Project

General

Profile

Actions

Feature #851

closed

Consider including the voice network in the calculation of the security of the network

Added by Soren Stoutner 7 months ago. Updated 6 months ago.

Status:
Closed
Priority:
Next Release
Start date:
05/16/2022
Due date:
% Done:

0%

Estimated time:

Description

Currently the overall security of the network (Antiquated, Insecure, or Secure) is calculated solely from the Data network. It might be advisable to also include the voice network. However, this increases the complexity of the calculation.

Probably the most logical way to combine them would be to consider any connection that does not have 5G NR, IWLAN, or Unknown (depending on the outcome of https://redmine.stoutner.com/issues/849) for both Data and Voice networks to be Insecure, and similarly to extend the rules for Antiquated networks to both Data and Voice.

One of the things that makes this complex is that the realtime notification service only receives information about one of the network types at a time. It should be possible to store the last state of each network, but when switching protocols the Data and Voice often toggle between several different states before they quiesce, often passing through Unknown. And to make matters worse, they often don't do so at the same time. Typically the voice network moves first and the data network moves later. This could make changing Unknown to be consider Antiquated cause even more notification flapping.

Actions #1

Updated by Soren Stoutner 7 months ago

If this is implemented, it would make sense to color code the Data and Voice protocols on the main screen to the overall network security color.

Actions

Also available in: Atom PDF