Project

General

Profile

Actions
Copy link

Bug #15616

closed

GUI interface assignment input-check

Added by Georgiy Tyutyunnik 15 days ago. Updated 12 days ago.

Status:
Not a Bug
Priority:
Low
Assignee:
-
Category:
Web Interface
Target version:
-
Start date:
Due date:
% Done:

0%

Estimated time:
Release Notes:
Default
Affected Plus Version:
Affected Architecture:
All

Description

Under some circumstances it's possible to attempt an assignment of non-existing interface which will lead to a creation of non-functioning interface entry in GUI.
Steps to reproduce:
1) create VTI IPSec;
2) open Interfaces -> Assignment tab and assign all existing interfaces besides VTI IPSec;
3) open another management tab, delete VTI IPSec and Apply;
4) return to the Interfaces -> Assignment tab without renewing it, assign IPSec interface;
It will result in the creation of "bogus" interface which is registered as some already existing Network port in Assignments tab but will be still present in config as <ipsecX> category. It will not be configurable like usual assigned VTI IPSec interface.
Screenshots attached (resulting interface OPT9, originally supposed to be ipsec2, presented in Assignment tab as duplicate igc0)

Files

Download all files
3.png (72.2 KB) 3.png Georgiy Tyutyunnik, 07/12/2024 02:37 PM
2.png (72.1 KB) 2.png Georgiy Tyutyunnik, 07/12/2024 02:37 PM
1.png (62.9 KB) 1.png Georgiy Tyutyunnik, 07/12/2024 02:37 PM
Actions
Copy link
 #1

Updated by Marcos M 15 days ago

  • Status changed from New to Not a Bug

This can happen just about anywhere in the GUI. It does not support concurrent modification.

Actions
Copy link
 #2

Updated by Jim Pingle 12 days ago

Beyond the concurrent modification issue, ipsecX interfaces are exempt from the existence check on assignment because they don't always exist in the OS level. If we enforced that for IPsec VTI interfaces it would break other things like the assignment check at boot.

Actions
Copy link

Also available in: Atom PDF