Project

General

Profile

Actions

Regression #13739

closed

Interfaces without a configured name appear as lowercase

Added by Christopher Cope almost 2 years ago. Updated almost 2 years ago.

Status:
Resolved
Priority:
High
Assignee:
Category:
Interfaces
Target version:
Start date:
Due date:
% Done:

100%

Estimated time:
Plus Target Version:
23.01
Release Notes:
Force Exclusion
Affected Version:
Affected Architecture:
All

Description

23.01-DEVELOPMENT (amd64)
built on Fri Dec 09 06:12:49 UTC 2022
FreeBSD 14.0-CURRENT

The WAN & LAN interfaces are lowercase on first boot, but in the interface configuration they still show as capital. Simply clicking save makes them capital again.

Files

lower.png (21.8 KB) lower.png Christopher Cope, 12/09/2022 11:37 AM
Actions #1

Updated by Jim Pingle almost 2 years ago

Where exactly are they printed lowercase?

Boot output? The console menu? A dashboard widget? Interface status page? Somewhere else?

Actions #2

Updated by Christopher Cope almost 2 years ago

Jim Pingle wrote in #note-1:

Where exactly are they printed lowercase?

Boot output? The console menu? A dashboard widget? Interface status page? Somewhere else?

Apologies about the lack of detail. All of the above. It seems the default is now lowercase.

I have attached the console menu after clicking save on the WAN configuration.

Actions #3

Updated by Jim Pingle almost 2 years ago

  • Tracker changed from Bug to Regression
  • Subject changed from WAN & LAN appear as lowercase to Interfaces without a configured name appear as lowercase
  • Target version set to 2.7.0
  • Plus Target Version set to 23.01

The interfaces lack a descr tag initially, so they are assumed to be the internal name of the interface ('wan', 'lan'). It isn't specific to WAN/LAN, it would happen to any interface without a descr tag.

This used to be forced to uppercase when that assumption was made, somewhere recently this regressed.

Actions #4

Updated by Steve Wheeler almost 2 years ago

  • Priority changed from Normal to High
  • Affected Architecture All added

In addition this changes the auto generated gateway name for any dynamic gateway on an affected interface.

So if WAN_DHCP is set as the default gateway that no longer exists and the system loses it's default route.

Actions #5

Updated by Marcos M almost 2 years ago

  • Assignee set to Marcos M
  • Release Notes changed from Default to Force Exclusion
Actions #6

Updated by Marcos M almost 2 years ago

  • Status changed from New to Pull Request Review
Actions #7

Updated by Marcos M almost 2 years ago

  • Status changed from Pull Request Review to Feedback
  • % Done changed from 0 to 100
Actions #8

Updated by Steve Wheeler almost 2 years ago

  • Status changed from Feedback to Resolved

This looks good in todays snap.

Tested:

23.01-DEVELOPMENT (amd64)
built on Tue Dec 13 06:06:53 UTC 2022
FreeBSD 14.0-CURRENT

Actions

Also available in: Atom PDF