From: Tomek Mrugalski Date: Fri, 26 Aug 2016 14:38:17 +0000 (+0200) Subject: [master] Removed obsolete text in dhcp{4,6}.dox X-Git-Tag: trac4633_base~6 X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=bbb1532fd9d9e2af1c3a04aa0ef37e429a6e1291;p=thirdparty%2Fkea.git [master] Removed obsolete text in dhcp{4,6}.dox --- diff --git a/src/bin/dhcp4/dhcp4.dox b/src/bin/dhcp4/dhcp4.dox index 1663d5da8c..938d2ecb98 100644 --- a/src/bin/dhcp4/dhcp4.dox +++ b/src/bin/dhcp4/dhcp4.dox @@ -249,16 +249,9 @@ to evaluate the next class. @subsection dhcpv4ClassifierUsage How client classification information is used in DHCPv4 -Currently there is a short code section that alternates packet processing depending on -which class it belongs to. (It is planned to move that capability to an external hook -library, see ticket #3275.) The class specific behavior is: - -- docsis3.0 packets have siaddr (next server) field set -- docsis3.0 packets have file field set to the content of the boot-file-name option -- eRouter1.0 packets have siaddr (next server) field cleared - -Aforementioned modifications are conducted in -@ref isc::dhcp::Dhcpv4Srv::vendorClassSpecificProcessing. +The classification code has been revamped in Kea 1.1. The old code that did specific +things for cable modems can now be achieved with the general classification code. Users +can simply define the class with next-address and/or filename in it. It is possible to define class restrictions in subnet, so a given subnet is only accessible to clients that belong to a given class. That is implemented as diff --git a/src/bin/dhcp6/dhcp6.dox b/src/bin/dhcp6/dhcp6.dox index 559206348e..b2992ff462 100644 --- a/src/bin/dhcp6/dhcp6.dox +++ b/src/bin/dhcp6/dhcp6.dox @@ -260,10 +260,6 @@ to evaluate the next class. @subsection dhcpv6ClassifierUsage How client classification information is used in DHCPv6 -Currently there is no class behavior coded in DHCPv6, hence no v6 equivalent of -@ref isc::dhcp::Dhcpv4Srv::vendorClassSpecificProcessing. Should any need for such a code arise, -it will be conducted in an external hooks library. - It is possible to define class restrictions in subnet, so a given subnet is only accessible to clients that belong to a given class. That is implemented as isc::dhcp::Pkt6::classes_ being passed in isc::dhcp::Dhcpv6Srv::selectSubnet() to isc::dhcp::CfgMgr::getSubnet6().