pkgsrc changes:
Fix hard-coded paths in manual pages.
Pointed out in PR 36316 by Jonathan A. Kollasch.
Changes:
[Common to all programs]
- supports compilation on Solaris
- supports interface names other than {alphabet}{numeric} format.
- allows a user to specify the owner/group for the installed files.
- fixed a bug that IA-PD/IA-NA cannot coexist in one DHCP message when they
have the same IA-ID.
[DHCPv6 Relay]
- supported script execution for dhcp6relay.
- accepts ULA
- changes the destination port of a relayed DHCP packet from 546 to 547, when
it is supposed to be bound for a relay, instead of a client.
[DHCPv6 Server]
- implemented DHCPv6 Confirm message processing
- implemented DHCPv6 Decline message processing
- fixed a Solicitation message validation as stated in RFC3315 15.2.
- fixed a bug that Rebind does not work for IA-NA.
- supported an address pool that has only one entry.
- fixed an IA allocation failure from pool when it doubly requested by the same
client
- recognizes "-P" option.
Tested by KAWAMOTO Yoshihisa (kawamoto@).
WIDE-DHCPv6 is an open-source implementation of Dynamic Host
Configuration Protocol for IPv6 (DHCPv6) developed by the KAME
project.
The implementation mainly conforms to the following standards:
- RFC3315: Dynamic Host Configuration Protocol for IPv6 (DHCPv6)
- RFC3319: Dynamic Host Configuration Protocol (DHCPv6) Options
for Session Initiation Protocol (SIP) Servers
- RFC3633: IPv6 Prefix Options for Dynamic Host Configuration
Protocol (DHCP)
- RFC3646: DNS Configuration options for Dynamic Host
Configuration Protocol for IPv6 (DHCPv6)
- RFC4075: Simple Network Time Protocol (SNTP) Configuration
Option for DHCPv6
- RFC4242: Information Refresh Time Option for Dynamic Host
Configuration Protocol for IPv6 (DHCPv6)
All the components of the main protocol are provided, i.e.,
DHCPv6 clients, servers, and relay agents.
Supported message types are as follows:
Solicit, Advertise, Request, Renew, Rebind, Release, Reply,
Information-request, Relay-forward and Relay-reply.
Note that the current implementation does not support IPv6
temporary address allocation by DHCPv6, and there is no plan to
implement that feature at the moment.
