Bug 25021 – UDM module networks/network should skip typical Router-IPs

Bug 25021 - UDM module networks/network should skip typical Router-IPs


Summary:	UDM module networks/network should skip typical Router-IPs

Status:	RESOLVED WONTFIX

Product:	UCS
Classification:	Unclassified
Component:	UMC - Networks
Version:	UCS 4.2
Hardware:	Other Linux

Importance:	P3 enhancement (vote)
Target Milestone:	---
Assigned To:	UMC maintainers
QA Contact:

URL:
Keywords:

Depends on:	18581
Blocks:
	Show dependency tree / graph

Reported:	2011-11-30 14:25 CET by Felix Botner
Modified:	2020-07-03 20:53 CEST (History)
CC List:	3 users (show)

See Also:
What kind of report is it?:	Development Internal
What type of bug is this?:	---
Who will be affected by this bug?:	---
How will those affected feel about the bug?:	---
User Pain:
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
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.

Description Felix Botner

2011-11-30 14:25:47 CET

+++ This bug was initially created as a clone of Bug #18581 +++

Das über das UDM-Modul Netzwerk gepflegte Netzwerkobjekt sollte typische
Router/Gateway-IPs bei der Vergabe auslassen, z.B. .1 und .254

zumindest die .1 Adresse wird in 3.0 wieder vorgeschlagen.

Comment 1 Andreas Büsching

2011-12-02 16:55:06 CET

In simpleComputer ist für das CLI folgender Fall implementiert

if not self['ip']:
...
  if '.' in self['ip'][0] and self['ip'][0].split('.')[-1] in ["0", "1", "254"]:
    network_object.stepIp()
    network_object.modify()
    continue

Das Web-Frontend nutzt diesen Teil nicht, da es schon vor dem Anlegen des Rechners die nächstmögliche IP-Adresse ermittelt (Netzwerk-Objekt erzeugen, hochzählen und rausgeben). Die ermittelten Werte werden dann in die entsprechenden Attribute beim Anlegen eingetragen und dadurch wird dieser Code-Snippet nicht angesprungen.

Am sinnvollsten wäre es wenn diese Sonderregel in stepIp vom Network-Objekt implementiert wird. dann machen beide Frontends es automatisch richtig.

Comment 2 Stefan Gohmann

2017-06-16 20:40:00 CEST

This issue has been filed against UCS 3. UCS 3 is out of the normal maintenance and many UCS components have vastly changed in UCS 4.

If this issue is still valid, please change the version to a newer UCS version otherwise this issue will be automatically closed in the next weeks.

Comment 3 Ingo Steuwer

2020-07-03 20:53:58 CEST

This issue has been filed against UCS 4.2.

UCS 4.2 is out of maintenance and many UCS components have changed in later releases. Thus, this issue is now being closed.

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