Opened 5 years ago
Last modified 4 years ago
#3495 new enhancement
Custom IPv4 pool (contributed patch)
| Reported by: | tomek | Owned by: | UnAssigned |
|---|---|---|---|
| Priority: | medium | Milestone: | Outstanding Tasks |
| Component: | configuration | Version: | git |
| Keywords: | Cc: | ||
| CVSS Scoring: | Parent Tickets: | ||
| Sensitive: | no | Defect Severity: | N/A |
| Sub-Project: | DHCP | Feature Depending on Ticket: | |
| Estimated Difficulty: | 0 | Add Hours to Ticket: | 0 |
| Total Hours: | 0 | Internal?: | no |
Description
This is a fifth ticket created for a patch by Shawn Lewis.
Shawn:
In the current implementation of IPv4 pool (Pool4 in /lib/dhcpsrv/pool.h), the constructor would set the
first and last addresses for a pool based on the prefix, if they are not explicitly specified. But this may
cause conflicted IP addresses or other management issues in practice. For example, if we have a subnet
192.168.1.0/24. The first IP address 192.168.1.0 would be the network ID, while the last IP address
192.168.1.255 would be the broadcast address for the subnet. In addition, 192.168.1.1 and 192.168.1.254
are typically used by network gateways. Therefore, we derive a new Pool4Custom class from Pool4, to
avoid using these four IP addresses. The /lib/dhcpsrc/pool.h(cc) has been updated.
Subtickets
Change History (6)
comment:1 Changed 5 years ago by tomek
- Milestone changed from Kea-proposed to Kea1.0
comment:3 Changed 5 years ago by tomek
- Milestone changed from Kea1.0 to Kea0.9.1
We haven't managed to address this one, moving to 0.9.1.
comment:4 Changed 5 years ago by tomek
- Milestone changed from Kea0.9.1 to Kea0.9.2
Moving to 0.9.2 as discussed on Kea weekly call today (2014-10-08).
If we hear back from the contributor and receive updated patch, we'll move it back to 0.9.1.
comment:5 Changed 4 years ago by hschempf
- Milestone changed from Kea0.9.2 to DHCP Outstanding Tasks
comment:6 Changed 4 years ago by tomek
- Milestone changed from DHCP Outstanding Tasks to Outstanding Tasks
Milestone renamed
As discussed on Kea meeting (2014-07-16) we not include this ticket in 0.9, due to lack of available processing time. Therefore moving to 1.0.