Bug 31767 - No possibility to assign multiple IPv4 addresses to VLANs, Bonds, Bridges
No possibility to assign multiple IPv4 addresses to VLANs, Bonds, Bridges
Status: RESOLVED WONTFIX
Product: UCS
Classification: Unclassified
Component: UMC - Basic settings
UCS 4.1
Other Linux
: P5 enhancement (vote)
: ---
Assigned To: UMC maintainers
:
Depends on: 30816
Blocks:
  Show dependency treegraph
 
Reported: 2013-06-19 13:44 CEST by Alexander Kläser
Modified: 2019-01-03 07:18 CET (History)
3 users (show)

See Also:
What kind of report is it?: Bug Report
What type of bug is this?: 1: Cosmetic issue or missing function but workaround exists
Who will be affected by this bug?: 2: Will only affect a few installed domains
How will those affected feel about the bug?: 2: A Pain – users won’t like this once they notice it
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): Usability, Workaround is available
Max CVSS v3 score:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Alexander Kläser univentionstaff 2013-06-19 13:44:53 CEST
Currently it is not possible to assign multiple IPv4 addresses to VLANs, Bonds, or Bridges. This is due to limitations in the naming convention of UCR. For physical devices, additional IPv4 addresses are assigned as suffix of the interface name, e.g. ethX_Y.

A possible solution could be a mapping similar to IPv6 addresses, i.e.:

  ethX/ipv6/<identifier>/...
Comment 1 Florian Best univentionstaff 2013-09-20 10:06:25 CEST
Could be done together with Bug #32648.
Comment 2 Philipp Hahn univentionstaff 2013-12-12 13:54:05 CET
Virtual-interfaces are deprecated, as they only work for IPv4 and not for IPv6.
Linux supports adding additional IP addresses to interfaces since a very long time by using "ip addr add ... dev ...".
(Even Debian has no special support for multiple IP addresses and just recommends to no longer use "iface ... inet static" but "iface ... inet manual" and to configure all addresses by hand through /etc/network/interfaces.)

For UCS this can be done through UCR:

xargs -d '\n' ucr set <<'__UCR__'
interfaces/eth0/options/1=up ip addr add 1.2.3.4/24 dev $IFACE
interfaces/eth0/options/2=down ip addr del 1.2.3.4/24 dev $IFACE
__UCR__

For bridges, VLANs and bonding interfaces this can even be done through the UMC "basic settings" module by adding the "up ... / down ..." part into the "Additional bridge/vlan/bonding options" text fields.
Comment 3 Stefan Gohmann univentionstaff 2019-01-03 07:18:22 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.