Project

General

Profile

Actions

Bug #10854

closed

DHCPv6 Server assigns addresses from outside of specified range (Regression from 2.4.4)

Added by Jason Cohen over 5 years ago. Updated over 5 years ago.

Status:
Not a Bug
Priority:
Normal
Assignee:
-
Category:
DHCP (IPv4)
Target version:
-
Start date:
08/26/2020
Due date:
% Done:

0%

Estimated time:
Plus Target Version:
Release Notes:
Affected Version:
2.4.5-p1
Affected Architecture:

Description

The DHCPv6 server appears to be ignoring the specified range when assigning addresses. For example, I set one of my LANs to assign addresses from 2001:470:e1e0:9::100 through 2001:470:e1e0:9::150. Instead, it assigns addresses like 2001:470:e1e0:9::14a or 2001:470:e1e0:9::14f. Static DHCPv6 assignments work as expected. This appears to be a regression from the behavior in 2.4.4 as it was working as expected until I upgraded from a 2.4.4 release to 2.4.5-p1. In order to verify that the client wasn't just ignoring the router, I captured the DHCPv6 packet traffic and confirmed that the router advertised 2001:470:e1e0:9::14a.

Actions #1

Updated by Jason Cohen over 5 years ago

NOTE: I tried editing the specified range and re-saving to restart the DHCPv6 server to see if that resolved the issue but I am still seeing addresses assigned outside the specified range.

Actions #2

Updated by Jim Pingle over 5 years ago

  • Status changed from New to Not a Bug

That's not a bug, it's doing exactly what you asked. IPv6 addresses are hexidecimal, not decimal. 100-150 in hex includes the addresses you mentioned.

Actions #3

Updated by Jim Pingle over 5 years ago

  • Category set to DHCP (IPv4)
Actions

Also available in: Atom PDF