Bug 34131 - IPv6: Tooltip bei »Reverse-Zone anlegen« für IPv6 minimal falsch
IPv6: Tooltip bei »Reverse-Zone anlegen« für IPv6 minimal falsch
Product: UCS
Classification: Unclassified
Component: UMC - DNS
UCS 3.2
Other Linux
: P5 minor (vote)
: UCS 4.2
Assigned To: Philipp Hahn
Florian Best
: interim-1
Depends on:
  Show dependency treegraph
Reported: 2014-02-14 18:01 CET by Moritz Bunkus
Modified: 2017-04-04 18:29 CEST (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?: 1: Will affect a very few installed domains
How will those affected feel about the bug?: 1: Nuisance – not a big deal but noticeable
User Pain: 0.006
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:


Note You need to log in before you can comment on or make changes to this bug.
Description Moritz Bunkus 2014-02-14 18:01:30 CET
Der Tooltip sagt, dass mit 0en aufgefüllt werden muss. Das angeführte Beispiel tut das aber gerade nicht: »2001:0db8:010« (fehlende 0 im letzten Block).
Comment 1 Philipp Hahn univentionstaff 2016-11-02 13:58:51 CET
I guess the bug is about the following message from management/univention-directory-manager-modules/modules/univention/admin/syntax.py:1345:
> error_message = _('A subnet for reverse lookup consists of the first one to three parts of an IPv4 address (example: "192.168.0") or of the first 1 to 31 nibbles of an IPv6 address with leading zeroes and without :: substitution (example: "2001:0db8:010")')

In German its
> "Ein Subnetz für den Reverse Lookup besteht aus den ersten 1 bis 3 Teilen "
> "einer IPv4-Adresse (z.B. \"192.168.0\") oder den ersten 1 bis 31 Nibbles "
> "einer IPv6-Adresse mit führenden Nullen und ohne die :: Ersetzung (z.B. "
> "\"2001:0db8:010\")"

That is all correct.

What might be misleading is the confusion about 'leading 0s' vs. 'trailing 0s': Normally 1:2:3:4:5:6:7:8 is a short-hand for 0001:0002:0003:.... and not 1000:2000:3000:...
 $ python -c 'import ipaddr;print ipaddr.IPv6Address("1:2:3:4:5:6:7:8").exploded'

To protect from this error UMC requires you to enter the "leading 0s", as UMC has interest only for the network nibbles, but not the host nibbles.
There is nothing wrong with striping *trailing* 0s - this is even required as the prefix length only must be a multiple of 4, not of 16. So "2001:0db8:010" is the /44 subnet:
 $ python -c 'import ipaddr;print ipaddr.IPv6Network("2001:0db8:100::/44").compressed'
"2001:0db8:0100" would be the /48 subnet.
Comment 2 Moritz Bunkus 2016-11-02 14:14:11 CET
I see. The examples would be much clearer if the netmasks where given as well, e.g. "2001:0db8:010 for the network 2001:0db8:0100::/44 or 2001:0db8:0100 for 2001:0db8:0100::/48".
Comment 3 Philipp Hahn univentionstaff 2016-11-04 10:21:12 CET
r74100 | Bug #34131 udm: Improve help for reverseLookupSubnet

Package: univention-directory-manager-modules
Version: 12.0.5-2A~
Branch: ucs_4.2-0
Comment 4 Moritz Bunkus 2016-11-04 10:29:42 CET
Thanks :)
Comment 5 Florian Best univentionstaff 2016-12-22 16:54:43 CET
OK: Changelog entry
Comment 6 Stefan Gohmann univentionstaff 2017-04-04 18:29:11 CEST
UCS 4.2 has been released:

If this error occurs again, please use "Clone This Bug".