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