| 1 | # |
| 2 | # For a description of the syntax of this configuration file, |
| 3 | # see scripts/kbuild/config-language.txt. |
| 4 | # |
| 5 | |
| 6 | config BUSYBOX_CONFIG_APP_UDHCPD |
| 7 | bool "udhcp server (udhcpd)" |
| 8 | default n |
| 9 | help |
| 10 | udhcpd is a DHCP server geared primarily toward embedded systems, |
| 11 | while striving to be fully functional and RFC compliant. |
| 12 | |
| 13 | config BUSYBOX_CONFIG_APP_DHCPRELAY |
| 14 | bool "dhcprelay" |
| 15 | default n |
| 16 | depends on BUSYBOX_CONFIG_APP_UDHCPD |
| 17 | help |
| 18 | dhcprelay listens for dhcp requests on one or more interfaces |
| 19 | and forwards these requests to a different interface or dhcp |
| 20 | server. |
| 21 | |
| 22 | config BUSYBOX_CONFIG_APP_DUMPLEASES |
| 23 | bool "Lease display utility (dumpleases)" |
| 24 | default n |
| 25 | depends on BUSYBOX_CONFIG_APP_UDHCPD |
| 26 | help |
| 27 | dumpleases displays the leases written out by the udhcpd server. |
| 28 | Lease times are stored in the file by time remaining in lease, or |
| 29 | by the absolute time that it expires in seconds from epoch. |
| 30 | |
| 31 | config BUSYBOX_CONFIG_FEATURE_UDHCPD_WRITE_LEASES_EARLY |
| 32 | bool "Rewrite the lease file at every new acknowledge" |
| 33 | default n |
| 34 | depends on BUSYBOX_CONFIG_APP_UDHCPD |
| 35 | help |
| 36 | If selected, udhcpd will write a new file with leases every |
| 37 | time a new lease has been accepted, thus eliminating the need |
| 38 | to send SIGUSR1 for the initial writing or updating. Any timed |
| 39 | rewriting remains undisturbed |
| 40 | |
| 41 | config BUSYBOX_CONFIG_DHCPD_LEASES_FILE |
| 42 | string "Absolute path to lease file" |
| 43 | default "/var/run/udhcpd.leases" |
| 44 | depends on BUSYBOX_CONFIG_APP_UDHCPD |
| 45 | help |
| 46 | udhcpd stores addresses in a lease file. This is the absolute path |
| 47 | of the file. Normally it is safe to leave it untouched. |
| 48 | |
| 49 | config BUSYBOX_CONFIG_APP_UDHCPC |
| 50 | bool "udhcp client (udhcpc)" |
| 51 | default y |
| 52 | help |
| 53 | udhcpc is a DHCP client geared primarily toward embedded systems, |
| 54 | while striving to be fully functional and RFC compliant. |
| 55 | |
| 56 | The udhcp client negotiates a lease with the DHCP server and |
| 57 | runs a script when a lease is obtained or lost. |
| 58 | |
| 59 | config BUSYBOX_CONFIG_FEATURE_UDHCPC_ARPING |
| 60 | bool "Verify that the offered address is free, using ARP ping" |
| 61 | default n |
| 62 | depends on BUSYBOX_CONFIG_APP_UDHCPC |
| 63 | help |
| 64 | If selected, udhcpc will send ARP probes and make sure |
| 65 | the offered address is really not in use by anyone. The client |
| 66 | will DHCPDECLINE the offer if the address is in use, |
| 67 | and restart the discover process. |
| 68 | |
| 69 | config BUSYBOX_CONFIG_FEATURE_UDHCP_PORT |
| 70 | bool "Enable '-P port' option for udhcpd and udhcpc" |
| 71 | default n |
| 72 | depends on BUSYBOX_CONFIG_APP_UDHCPD || BUSYBOX_CONFIG_APP_UDHCPC |
| 73 | help |
| 74 | At the cost of ~300 bytes, enables -P port option. |
| 75 | This feature is typically not needed. |
| 76 | |
| 77 | config BUSYBOX_CONFIG_UDHCP_DEBUG |
| 78 | int "Maximum verbosity level for udhcp applets (0..9)" |
| 79 | default 0 |
| 80 | range 0 9 |
| 81 | depends on BUSYBOX_CONFIG_APP_UDHCPD || BUSYBOX_CONFIG_APP_UDHCPC || BUSYBOX_CONFIG_APP_DHCPRELAY |
| 82 | help |
| 83 | Verbosity can be increased with multiple -v options. |
| 84 | This options controls how high it can be cranked up. |
| 85 | |
| 86 | Bigger values result in bigger code. Levels above 1 |
| 87 | are very verbose and useful for debugging only. |
| 88 | |
| 89 | config BUSYBOX_CONFIG_FEATURE_UDHCP_RFC3397 |
| 90 | bool "Support for RFC3397 domain search (experimental)" |
| 91 | default y |
| 92 | depends on BUSYBOX_CONFIG_APP_UDHCPD || BUSYBOX_CONFIG_APP_UDHCPC |
| 93 | help |
| 94 | If selected, both client and server will support passing of domain |
| 95 | search lists via option 119, specified in RFC3397. |
| 96 | |
| 97 | config BUSYBOX_CONFIG_UDHCPC_DEFAULT_SCRIPT |
| 98 | string "Absolute path to config script" |
| 99 | default "/usr/share/udhcpc/default.script" |
| 100 | depends on BUSYBOX_CONFIG_APP_UDHCPC |
| 101 | help |
| 102 | This script is called after udhcpc receives an answer. See |
| 103 | examples/udhcp for a working example. Normally it is safe |
| 104 | to leave this untouched. |
| 105 | |
| 106 | config BUSYBOX_CONFIG_UDHCPC_SLACK_FOR_BUGGY_SERVERS |
| 107 | int "DHCP options slack buffer size" |
| 108 | default 80 |
| 109 | range 0 924 |
| 110 | depends on BUSYBOX_CONFIG_APP_UDHCPD || BUSYBOX_CONFIG_APP_UDHCPC |
| 111 | help |
| 112 | Some buggy DHCP servers send DHCP offer packets with option |
| 113 | field larger than we expect (which might also be considered a |
| 114 | buffer overflow attempt). These packets are normally discarded. |
| 115 | If circumstances beyond your control force you to support such |
| 116 | servers, this may help. The upper limit (924) makes dhcpc accept |
| 117 | even 1500 byte packets (maximum-sized ethernet packets). |
| 118 | |
| 119 | This option does not make dhcp[cd] emit non-standard |
| 120 | sized packets. |
| 121 | |
| 122 | Known buggy DHCP servers: |
| 123 | 3Com OfficeConnect Remote 812 ADSL Router: |
| 124 | seems to confuse maximum allowed UDP packet size with |
| 125 | maximum size of entire IP packet, and sends packets which are |
| 126 | 28 bytes too large. |
| 127 | Seednet (ISP) VDSL: sends packets 2 bytes too large. |
| 128 | |
