Bug #7443

Issues Creating IPv6 Static Mappings

Added by Daryl Morse almost 3 years ago. Updated 6 months ago.

Target version:
Start date:
Due date:
% Done:


Estimated time:
Affected Version:
Affected Architecture:


There are a few issues creating IPv6 static mappings.

When entering the address for IPv4 static mapping, the entire address is required. If you try to enter the entire address for an IPv6 static mapping, it is an error.

In my case, the PD is a /56. Thinking the message probably meant the full /64 prefix should be zero, I entered ::50. It was accepted and the static mapping was created with the displayed address of ::50.

After releasing and renewing adapter, it was working.

However, Status / DHCPv6 Leases thinks the address is ::50, not prefix::50.

On top of that, even after pinging the host, Status / DHCPv6 Leases thinks the host is offline.

This needs some work. Whatever is done should be made consistent with creating an IPv4 static mapping.

Ideally, it should display the available range for which a static address can be created so the user will not have to look elsewhere, but even if the available range was displayed, the user would still have to know which addresses are available, so maybe that's overly complicated.

To be consistent, the user should either have to enter the entire address for both IPv4 and IPv6 static mappings, or only the variable portion (i.e., excluding the subnet or /64 prefix).

Once the address is entered, the static mapping and the lease should both display the full address. DHCPv6 Leases is confused by the partial address, not knowing it should be the full address.

Prefix.PNG (9.49 KB) Prefix.PNG Daryl Morse, 04/01/2017 11:04 PM
mapping.PNG (17.7 KB) mapping.PNG Daryl Morse, 04/01/2017 11:10 PM
lease.PNG (6.61 KB) lease.PNG Daryl Morse, 04/01/2017 11:12 PM


#1 Updated by Jim Thompson almost 3 years ago

  • Assignee set to Renato Botelho
  • Priority changed from High to Normal

#2 Updated by Daryl Morse almost 3 years ago

This issue is with the 2.4 beta.

#3 Updated by Chris Collins almost 2 years ago

Did this ever get fixed? I ended up at this page trying to diagnose static ipv6 mappings.

I have configured static mappings for 2 devices, but they are been assigned addresses from the dynamic pool, as reported by Daryl there is also inconsistency on what is expected to be inputted on dhcp6 vs dhcp4 and the leases page shows the device as offline.

Unlike Daryl however I cannot get the static ipv6 leased regardless if I reset the network device or not.

#4 Updated by Chris Collins almost 2 years ago

The actual lease works now, so now I am just basically verifying the original bug report. Its cosmetic only but I agree the behaviour should be changed.

#5 Updated by Jim Pingle 6 months ago

  • Category set to DHCP Server

#6 Updated by Jim Pingle 6 months ago

  • Category changed from DHCP Server to DHCP (IPv6)

Also available in: Atom PDF