From: Marcin Siodelski Date: Thu, 27 Mar 2014 12:22:54 +0000 (+0100) Subject: [3258] Updated bind10-guide: limitations and supported standards. X-Git-Tag: bind10-1.2.0rc1-release~27^2~3 X-Git-Url: http://git.ipfire.org/gitweb.cgi?a=commitdiff_plain;h=fa087f7abcad2630be393aa1a6fbf06ed5574c8e;p=thirdparty%2Fkea.git [3258] Updated bind10-guide: limitations and supported standards. --- diff --git a/doc/guide/bind10-guide.xml b/doc/guide/bind10-guide.xml index 932ccd52a1..1d2b374108 100644 --- a/doc/guide/bind10-guide.xml +++ b/doc/guide/bind10-guide.xml @@ -4994,6 +4994,11 @@ Dhcp4/dhcp-ddns/qualifying-suffix "example.com" string RFC 3046: Relay Agent Information option is supported. + + RFC 3925: + Vendor-Identifying Vendor Class and Vendor-Identifying Vendor-Specific + Information option are supported. + RFC 6842: Server by default sends back client-id option. That capability may be @@ -5026,24 +5031,10 @@ Dhcp4/dhcp-ddns/qualifying-suffix "example.com" string - - On startup, the DHCPv4 server does not get the full configuration from - BIND 10. To remedy this, after starting BIND 10, modify any parameter - and commit the changes, e.g. - -> config show Dhcp4/renew-timer -Dhcp4/renew-timer 1000 integer (default) -> config set Dhcp4/renew-timer 1001 -> config commit - - - - - The DHCPv4 server does not support - BOOTP. That is a design choice and the limitation is - permanent. If you have legacy nodes that can't use DHCP and - require BOOTP support, please use the latest version of ISC DHCP, - available from . + + BOOTP (RFC 951) + is not supported. + Raw sockets operation is working on Linux @@ -5056,11 +5047,7 @@ Dhcp4/renew-timer 1000 integer (default) sending ICMP echo request. - Address rebinding (REBIND) and duplication report (DECLINE) - are not supported yet. - - - DNS Update is not yet supported. + Address duplication report (DECLINE) is not supported yet. @@ -6420,7 +6407,11 @@ Dhcp6/dhcp-ddns/qualifying-suffix "example.com" string RFC 3315: Supported messages are SOLICIT, - ADVERTISE, REQUEST, RELEASE, RENEW, and REPLY. + ADVERTISE, REQUEST, RELEASE, RENEW, REBIND and REPLY. + + + RFC 3633: Supported options are IA_PD and + IA_PREFIX. New status code: NoPrefixAvail. RFC 3646: Supported option is DNS_SERVERS. @@ -6440,46 +6431,39 @@ Dhcp6/dhcp-ddns/qualifying-suffix "example.com" string yet, rather than actual limitations. - - - On-line configuration has some limitations. Adding new subnets or - modifying existing ones work, as is removing the last subnet from - the list. However, removing non-last (e.g. removing subnet 1,2 or 3 if - there are 4 subnets configured) will cause issues. The problem is - caused by simplistic subnet-id assignment. The subnets are always - numbered, starting from 1. That subnet-id is then used in leases - that are stored in the lease database. Removing non-last subnet will - cause the configuration information to mismatch data in the lease - database. It is possible to manually update subnet-id fields in - MySQL database, but it is awkward and error prone process. A better - reconfiguration support is planned. - - - - - - On startup, the DHCPv6 server does not get the full configuration from - BIND 10. To remedy this, after starting BIND 10, modify any parameter - and commit the changes, e.g. - -> config show Dhcp6/renew-timer -Dhcp6/renew-timer 1000 integer (default) -> config set Dhcp6/renew-timer 1001 -> config commit - - - - Temporary addresses are not supported. + + + On-line configuration has some limitations. Adding new subnets or + modifying existing ones work, as is removing the last subnet from + the list. However, removing non-last (e.g. removing subnet 1,2 or 3 if + there are 4 subnets configured) will cause issues. The problem is + caused by simplistic subnet-id assignment. The subnets are always + numbered, starting from 1. That subnet-id is then used in leases + that are stored in the lease database. Removing non-last subnet will + cause the configuration information to mismatch data in the lease + database. It is possible to manually update subnet-id fields in + MySQL database, but it is awkward and error prone process. A better + reconfiguration support is planned. + - Prefix delegation is not supported. + + Server will allocate, renew or rebind maximum one lease for a + particular IA option (IA_NA or IA_PD) sent by a client. + RFC 3315 and + RFC 3633 allow + for multiple addresses or prefixes to be allocated for a single IA. + - Confirmation (CONFIRM), and duplication report (DECLINE) - are not yet supported. + Temporary addresses are not supported. - DNS Update is not supported. + + Confirmation (CONFIRM), duplication report (DECLINE), + stateless configuration (INFORMATION-REQUEST) and client + reconfiguration (RECONFIGURE) are not yet supported. +