source: MondoRescue/branches/2.2.9/mindi-busybox/networking/udhcp/Config.in@ 2725

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