Summary: | DHCP option to prevent requesting the previously assigned IP address | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | sfp-a7x <gentoo-a7x> |
Component: | [OLD] baselayout | Assignee: | Gentoo's Team for Core System packages <base-system> |
Status: | RESOLVED WORKSFORME | ||
Severity: | enhancement | ||
Priority: | High | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
sfp-a7x
2006-11-25 15:28:31 UTC
1. The server may be configured to hand out a specific IP per MAC address 2. If you do not specifically DHCP_RELEASE your IP, and re-request it even without having the cache file, the server may give you the same one again. 2.1. The server may be configured to IGNORE DHCP_RELEASE messages. 3. The cache file only really has an effect where (your IP was released or expired from the server) AND (the IP in question is presently free) AND (the server honours specific requests). It's possible best to delete the cache file using a preup block. Test with the dhcpcd client manually with debugging on, and you can figure out which of the behaviors 1-3 are applicable to your DHCP server. i dont see any change required in our net scripts ... dhcpcd-3.0.0 doesn't use .cache files any more, which fixes this |