Project

General

Profile

Actions
Copy link

Bug #10437

closed

Changing interface description will break gateway groups

Added by Jon Brabender about 4 years ago. Updated about 4 years ago.

Status:
Duplicate
Priority:
Normal
Assignee:
-
Category:
Gateways
Target version:
-
Start date:
04/06/2020
Due date:
% Done:

0%

Estimated time:
Plus Target Version:
Release Notes:
Affected Version:
2.4.4-p3
Affected Architecture:

Description

Reproduce:
  • System with Multiple Wans (Description/Interface= WAN/em0, WAN2/em1)
  • Create an gateway group using these WANs
  • * System/Routing/Gateway Groups
  • * for example WAN_Failover_Group, WAN/Tier1, WAN2/Tier2
  • Rename the DESCRIPTION of the Interface
  • * Interfaces/WAN2
  • * "Description=WAN_BACKUP"
  • WAN2 is removed from the gateway group
  • * System/Routing/Gateway Groups
  • * WAN_Failover_Group no longer contains "em1" (prior WAN2, now WAN_BACKUP)
  • * Group must be edited to add the interface back to the group.

Navigate to a WAN interface that is being used in a Gateway Group

Interfaces/WAN_Failover

I believe this may have been the "intent" of ticket "#8218"

Actions
Copy link
 #1

Updated by Jim Pingle about 4 years ago

  • Status changed from New to Duplicate

This is the same root issue as #8218 / #8151, so it doesn't need its own entry.

This would only happen with dynamic interfaces like DHCP, not static interfaces or gateways.

Actions
Copy link
 #2

Updated by Jon Brabender about 4 years ago

Those issues are "changing the name"...this is "changing the description"...I realize changing the "name" is not allowed, but I assumed the description is always dereferenced from the interface name...so "changing the description" does not work either? And is not considered a bug (to be clear)...and if changing an "interface description" (which is allowed by the UI) causes this problem...what other side effects should we be expecting?

Actions
Copy link
 #3

Updated by Jim Pingle about 4 years ago

In effect the "description" of the interface is its name in this context. It alters the name of the gateway. The field name nitpick is just semantics. The end result is the same no matter what path it takes. It's all the same root cause.

Actions
Copy link
 #4

Updated by Jon Brabender about 4 years ago

Thanks, I guess it just confusing because it is "allowed", but the side effects are not clear. Is there anything else (beyond the gateway groups) that are impacted?

Actions
Copy link
 #5

Updated by Jon Brabender about 4 years ago

Looking through the config.xml, I can see what you mean about DHCP interfaces (deriving names from the description)...I'm sure there must have been a good reason to choose to derive the <gateway_item><name> from the <interfaces><descr>. Just suggesting for DHCP interface description changes to either not allow, or to present a message on what is going to break.
Thanks again

Actions
Copy link

Also available in: Atom PDF