Bug #7443
closedIssues Creating IPv6 Static Mappings
100%
Description
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.
Files
Updated by Jim Thompson over 7 years ago
- Assignee set to Renato Botelho
- Priority changed from High to Normal
Updated by Chris Collins over 6 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.
Updated by Chris Collins over 6 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.
Updated by Jim Pingle about 5 years ago
- Category changed from DHCP (IPv4) to DHCP (IPv6)
Updated by Viktor Gurov over 4 years ago
Daryl Morse wrote:
There are a few issues creating IPv6 static mappings.
..However, Status / DHCPv6 Leases thinks the address is ::50, not prefix::50.
Updated by Jim Pingle over 4 years ago
- Status changed from New to Pull Request Review
- Target version set to 2.5.0
Updated by Renato Botelho over 4 years ago
- Status changed from Pull Request Review to Feedback
- % Done changed from 0 to 100
PR has been merged. Thanks!
Updated by Anonymous about 4 years ago
- Status changed from Feedback to Resolved