Bug 32648 - "Identifier" should be removed from network configuration dialogue
"Identifier" should be removed from network configuration dialogue
Status: RESOLVED WONTFIX
Product: UCS
Classification: Unclassified
Component: UMC - Network settings
UCS 4.1
Other Linux
: P5 normal (vote)
: ---
Assigned To: UMC maintainers
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2013-09-20 10:00 CEST by Moritz Muehlenhoff
Modified: 2019-01-03 07:18 CET (History)
4 users (show)

See Also:
What kind of report is it?: Bug Report
What type of bug is this?: 2: Improvement: Would be a product improvement
Who will be affected by this bug?: 2: Will only affect a few installed domains
How will those affected feel about the bug?: 1: Nuisance – not a big deal but noticeable
User Pain: 0.023
Enterprise Customer affected?:
School Customer affected?:
ISV affected?:
Waiting Support:
Flags outvoted (downgraded) after PO Review:
Ticket number:
Bug group (optional):
Max CVSS v3 score:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Moritz Muehlenhoff univentionstaff 2013-09-20 10:00:30 CEST
The "Network" tab of the "basic settings" dialogue allows the configuration of IPv6 addresses. An IPv6 address requires the following values:

IPv6 address
IPv6 prefix
Identifier

The identifier is only used internally in UCR for variables in the format interfaces/IDENTIFIER/ipv6/address.

For the user this entry field is confusing since "Identifier" is also IPv6 terminology (http://www.ipv6-portal.de/informationen/technik/interface-identifier.html)

The identifier should rather be autogenerated, e.g. interface01, interface02 etc.
Comment 1 Florian Best univentionstaff 2013-09-20 10:06:08 CEST
Could be done together with Bug #31767.
Comment 2 Philipp Hahn univentionstaff 2013-09-20 11:28:42 CEST
The rational behind introducing an identifier is that with IPv6 it is common to assign an unique IPv6 address for each service to simplify later relocation, that is DNS → IPv6 does not need to be updated and work instantaneous without the current problem of DNS cached out-dated entries. This is important for load-balancing and HA.
So the idea is use an identifier, which later still helps the administrator to understand, for what service the IPv6 address is used. Auto-generating it would not be helpful here.

@Sönke: correct me if I'm wrong.
Comment 3 Sönke Schwardt-Krummrich univentionstaff 2013-09-27 09:16:25 CEST
(In reply to Philipp Hahn from comment #2)
> So the idea is use an identifier, which later still helps the administrator
> to understand, for what service the IPv6 address is used. Auto-generating it
> would not be helpful here.

Yes and no. 
First of all, the wording is unclear. "Identifier" may be a descriptive identifier as described by Philipp or the IPv6 identifier. I think, this should be changed at minimum.

Using a descriptive identifier for IPv6 addresses leads to another mapping (identifier ←→ IPv6 address) that has to be kept in sync with the mapping 
DNS name ←→ IPv6 address.

1) The simpliest way would be the internal automatic generation of interface 
   identifiers.
2) If 1) is not enough, it would also be possible to switch via checkbox between 
   the simple mode described in 1) and the expert mode as it is currently 
   implemented.
3) Solution 1) will be implemented and a button shows a popup dialog that 
   displays all available DNS forward and reverse zone entries for the 
   corresponding IPv6 address. This way the user does not have to maintain two 
   mapping but may check which services/DNS entries refer to the selected address.
Comment 4 Stefan Gohmann univentionstaff 2019-01-03 07:18:09 CET
This issue has been filled against UCS 4.1. The maintenance with bug and security fixes for UCS 4.1 has ended on 5st of April 2018.

Customers still on UCS 4.1 are encouraged to update to UCS 4.3. Please contact
your partner or Univention for any questions.

If this issue still occurs in newer UCS versions, please use "Clone this bug" or simply reopen the issue. In this case please provide detailed information on how this issue is affecting you.