From: Tomek Mrugalski Date: Fri, 19 Aug 2016 17:48:51 +0000 (+0200) Subject: [4483] User's Guide updated. X-Git-Tag: trac4631_base~15^2~10 X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=a2d0d05441183cc87e89abdb8891abd1db28ef95;p=thirdparty%2Fkea.git [4483] User's Guide updated. --- diff --git a/doc/guide/classify.xml b/doc/guide/classify.xml index a33f005d43..ed109046f6 100644 --- a/doc/guide/classify.xml +++ b/doc/guide/classify.xml @@ -181,7 +181,7 @@ Integer literal 123 '123' - An integer value + A 32 bits unsigned integer value @@ -257,7 +257,8 @@ Length of packet pkt.len 0x00000100 - The length of a DHCP packet (UDP header field) padded to 4 bytes. + The length of a DHCP packet (UDP header field), expressed + as 32 bits unsigned integer. Hardware address in DHCPv4 packet @@ -301,19 +302,33 @@ 192.0.2.1 The value of the siaddr field of the DHCPv4 packet (IPv4 address, 4 bytes) + + Message Type in DHCPv4 packet + pkt4.msgtype + 1 + The value of the message type field in the DHCPv4 + packet (expressed as 32 bits unsigned integer). + + + Transaction ID (xid) in DHCPv4 packet + pkt4.transid + 12345 + The value of the transaction id in the DHCPv4 + packet (expressed as 32 bits unsigned integer). + Message Type in DHCPv6 packet pkt6.msgtype 1 The value of the message type field in the DHCPv6 - packet. + packet (expressed as 32 bits unsigned integer). Transaction ID in DHCPv6 packet pkt6.transid 12345 The value of the transaction id in the DHCPv6 - packet. + packet (expressed as 32 bits unsigned integer). @@ -411,8 +426,14 @@ - Integers in the expression are converted to strings - when the expression is read into Kea. + Integers in the expression are converted to 32 bit unsigned integers and + are represented as four byte strings. For example 123 is represented as + 0x0000007b. All expressions that return numeric values use 32 bits + unsigned integers, even if the field in the packet is smaller. In general + it is easier to use decimal notation to represent integers, but it is also + possible to use hex notation. When using hex notation to represent an + integer care should be taken to make sure the value is represented as 32 + bits, e.g. use 0x00000001 instead of 0x1 or 0x01.