| Simon Kelley | 316e273 | 2010-01-22 20:16:09 +0000 | [diff] [blame] | 1 | Dnsmasq from version 2.52 has a couple of rather application-specific |
| 2 | features designed to allow for implementation of the DHCP part of CPE |
| 3 | WAN management protocol. |
| 4 | |
| 5 | http://www.broadband-forum.org/technical/download/TR-069_Amendment-2.pdf |
| 6 | http://en.wikipedia.org/wiki/TR-069 |
| 7 | |
| 8 | The relevant sections are F.2.1 "Gateway Requirements" and F.2.5 "DHCP |
| 9 | Vendor Options". |
| 10 | |
| 11 | First, dnsmasq checks for DHCP requests which contain an option-125 |
| 12 | vendor-class option which in turn holds a vendor section for IANA |
| 13 | enterprise number 3561 which contains sub-options codes 1 and 2. If |
| 14 | this is present then the network-tag "cpewan-id" is set. |
| 15 | This allows dnsmasq to be configured to reply with the correct |
| 16 | GatewayManufacturerOUI, GatewaySerialNumber and GatewayProductClass like this: |
| 17 | |
| 18 | dhcp-option=cpewan-id,vi-encap:3561,4,"<GatewayManufacturerOUI>" |
| 19 | dhcp-option=cpewan-id,vi-encap:3561,5,"<SerialNumber>" |
| 20 | dhcp-option=cpewan-id,vi-encap:3561,6,"<ProductClass>" |
| 21 | |
| 22 | Second, the received sub-options 1, 2, and 3 are passed to the DHCP |
| 23 | lease-change script as the environment variables DNSMASQ_CPEWAN_OUI, |
| 24 | DNSMASQ_CPEWAN_SERIAL, and DNSMASQ_CPEWAN_CLASS respectively. This allows |
| 25 | the script to be used to maintain a ManageableDevice table as |
| 26 | specified in F.2.1. Note that this data is not retained in dnsmasq's |
| 27 | internal DHCP lease database, so it is not available on every call to |
| 28 | the script (this is the same as some other data such as vendor and |
| 29 | user classes). It will however be available for at least the "add" |
| 30 | call, and should be stored then against the IP address as primary |
| 31 | key for future use. |
| 32 | |
| 33 | |
| 34 | This feature was added to dnsmasq under sponsorship from Ericsson. |
| 35 | |
| 36 | |