-
Notifications
You must be signed in to change notification settings - Fork 6
/
dhcpd.conf
303 lines (274 loc) · 9.23 KB
/
dhcpd.conf
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
#
# Sample configuration file for ISC dhcpd for Debian
#
# Attention: If /etc/ltsp/dhcpd.conf exists, that will be used as
# configuration file instead of this file.
#
#
# The ddns-updates-style parameter controls whether or not the server will
# attempt to do a DNS update when a lease is confirmed. We default to the
# behavior of the version 2 packages ('none', since DHCP v2 didn't
# have support for DDNS.)
ddns-update-style none;
# option definitions common to all supported networks...
#option domain-name "example.org";
#option domain-name-servers ns1.example.org ns2.example.org;
# If this DHCP server is the official DHCP server for the local
# network, the authoritative directive should be uncommented.
#authoritative;
# Use this to send dhcp log messages to a different log file (you also
# have to hack syslog.conf to complete the redirection).
log-facility local7;
# No service will be given on this subnet, but declaring it helps the
# DHCP server to understand the network topology.
# Erstes Subnetz
subnet 10.200.40.0 netmask 255.255.248.0 {
range 10.200.40.10 10.200.40.240;
default-lease-time 600;
max-lease-time 7200;
interface tap0;
}
# Zweites Subnetz
#subnet 172.25.1.0 netmask 255.255.255.0 {
# range 172.25.1.10 172.25.1.240;
# default-lease-time 600;
# max-lease-time 7200;
# interface netbr1;
#}
### Fixed Dynamic Leases
## Fixed Lease for vagranthost already manually set
host vagranthost1 {
hardware ethernet 76:5e:06:6a:7e:87;
fixed-address 10.200.40.01;
}
# Pandaboard Section
host PandaboardES1 {
hardware ethernet 0a:02:00:00:00:00;
fixed-address 10.200.41.01;
option host-name "pandaboardES1";
filename "pandaboard/1/image.elf";
}
host PandaboardES2 {
hardware ethernet 0a:02:00:00:00:01;
fixed-address 10.200.41.02;
option host-name "pandaboardES2";
filename "pandaboard/2/image.elf";
}
host PandaboardES3 {
hardware ethernet 0a:02:00:00:00:02;
fixed-address 10.200.41.03;
option host-name "pandaboardES3";
filename "pandaboard/3/image.elf";
}
host PandaboardES4 {
hardware ethernet 0a:02:00:00:00:03;
fixed-address 10.200.41.04;
option host-name "pandaboardES4";
filename "pandaboard/4/image.elf";
}
host PandaboardES5 {
hardware ethernet 0a:02:00:00:00:04;
fixed-address 10.200.41.05;
option host-name "pandaboardES1";
filename "pandaboard/5/image.elf";
}
## Raspberry Section
host Raspberry-1 {
hardware ethernet 0a:03:00:00:00:00;
fixed-address 10.200.42.01;
option host-name "raspberry1";
filename "raspberry/1/image.elf";
}
host Raspberry-2 {
hardware ethernet 0a:03:00:00:00:01;
fixed-address 10.200.42.02;
option host-name "raspberry2";
filename "raspberry/2/image.elf";
}
host Raspberry-3 {
hardware ethernet 0a:03:00:00:00:02;
fixed-address 10.200.42.03;
option host-name "raspberry3";
filename "raspberry/3/image.elf";
}
host Raspberry-4 {
hardware ethernet 0a:03:00:00:00:03;
fixed-address 10.200.42.04;
option host-name "raspberry4";
filename "raspberry/4/image.elf";
}
host Raspberry-5 {
hardware ethernet 0a:03:00:00:00:04;
fixed-address 10.200.42.05;
option host-name "raspberry5";
filename "raspberry/5/image.elf";
}
## Odroid Section
host Odroid-1 {
hardware ethernet 0a:04:00:00:00:00;
fixed-address 10.200.43.01;
option host-name "odroid1";
filename "odroid/1/image.elf";
}
host Odroid-2 {
hardware ethernet 0a:04:00:00:00:01;
fixed-address 10.200.43.02;
option host-name "odroid2";
filename "odroid/2/image.elf";
}
host Odroid-3 {
hardware ethernet 0a:04:00:00:00:02;
fixed-address 10.200.43.03;
option host-name "odroid3";
filename "odroid/3/image.elf";
}
host Odroid-4 {
hardware ethernet 0a:04:00:00:00:03;
fixed-address 10.200.43.04;
option host-name "odroid4";
filename "odroid/4/image.elf";
}
host Odroid-5 {
hardware ethernet 0a:04:00:00:00:04;
fixed-address 10.200.43.05;
option host-name "odroid5";
filename "odroid/5/image.elf";
}
## Zedboard & Zybo Section
host zedzybo-1 {
hardware ethernet 0a:05:00:00:00:00;
fixed-address 10.200.44.01;
option host-name "zedzybo1";
filename "zedzybo/1/image.elf";
}
host zedzybo-2 {
hardware ethernet 0a:05:00:00:00:01;
fixed-address 10.200.44.02;
option host-name "zedzybo2";
filename "zedzybo/2/image.elf";
}
host zedzybo-3 {
hardware ethernet 0a:05:00:00:00:02;
fixed-address 10.200.44.03;
option host-name "zedzybo3";
filename "zedzybo/3/image.elf";
}
host zedzybo-4 {
hardware ethernet 0a:05:00:00:00:03;
fixed-address 10.200.44.04;
option host-name "zedzybo4";
filename "zedzybo/4/image.elf";
}
host zedzybo-5 {
hardware ethernet 0a:05:00:00:00:04;
fixed-address 10.200.44.05;
option host-name "zedzybo5";
filename "zedzybo/5/image.elf";
}
## QEMU PBXA9 and Zed Zybo Section
host qemuVM-1 {
hardware ethernet 0a:06:00:00:00:00;
fixed-address 10.200.45.01;
option host-name "qemuVM1";
filename "qemuvm/1/image.elf";
}
host qemuVM-2 {
hardware ethernet 0a:06:00:00:00:01;
fixed-address 10.200.45.02;
option host-name "qemuVM2";
filename "qemuvm/2/image.elf";
}
host qemuVM-3 {
hardware ethernet 0a:06:00:00:00:02;
fixed-address 10.200.45.03;
option host-name "qemuVM3";
filename "qemuvm/3/image.elf";
}
host qemuVM-4 {
hardware ethernet 0a:06:00:00:00:03;
fixed-address 10.200.45.04;
option host-name "qemuVM4";
filename "qemuvm/4/image.elf";
}
host qemuVM-5 {
hardware ethernet 0a:06:00:00:00:04;
fixed-address 10.200.45.05;
option host-name "qemuVM5";
filename "qemuvm/5/image.elf";
}
# this is the PXE-Boot for this subnet
next-server 10.200.40.1;
filename "/image.elf";
############################################
#
# No further configuration is needed until this point
#
############################################
#subnet 10.152.187.0 netmask 255.255.255.0 {
#}
# This is a very basic subnet declaration.
#subnet 10.254.239.0 netmask 255.255.255.224 {
# range 10.254.239.10 10.254.239.20;
# option routers rtr-239-0-1.example.org, rtr-239-0-2.example.org;
#}
# This declaration allows BOOTP clients to get dynamic addresses,
# which we don't really recommend.
#subnet 10.254.239.32 netmask 255.255.255.224 {
# range dynamic-bootp 10.254.239.40 10.254.239.60;
# option broadcast-address 10.254.239.31;
# option routers rtr-239-32-1.example.org;
#}
# A slightly different configuration for an internal subnet.
#subnet 10.5.5.0 netmask 255.255.255.224 {
# range 10.5.5.26 10.5.5.30;
# option domain-name-servers ns1.internal.example.org;
# option domain-name "internal.example.org";
# option subnet-mask 255.255.255.224;
# option routers 10.5.5.1;
# option broadcast-address 10.5.5.31;
# default-lease-time 600;
# max-lease-time 7200;
#}
# Hosts which require special configuration options can be listed in
# host statements. If no address is specified, the address will be
# allocated dynamically (if possible), but the host-specific information
# will still come from the host declaration.
#host passacaglia {
# hardware ethernet 0:0:c0:5d:bd:95;
# filename "vmunix.passacaglia";
# server-name "toccata.fugue.com";
#}
# Fixed IP addresses can also be specified for hosts. These addresses
# should not also be listed as being available for dynamic assignment.
# Hosts for which fixed IP addresses have been specified can boot using
# BOOTP or DHCP. Hosts for which no fixed address is specified can only
# be booted with DHCP, unless there is an address range on the subnet
# to which a BOOTP client is connected which has the dynamic-bootp flag
# set.
#host fantasia {
# hardware ethernet 08:00:07:26:c0:a5;
# fixed-address fantasia.fugue.com;
#}
# You can declare a class of clients and then do address allocation
# based on that. The example below shows a case where all clients
# in a certain class get addresses on the 10.17.224/24 subnet, and all
# other clients get addresses on the 10.0.29/24 subnet.
#class "foo" {
# match if substring (option vendor-class-identifier, 0, 4) = "SUNW";
#}
#shared-network 224-29 {
# subnet 10.17.224.0 netmask 255.255.255.0 {
# option routers rtr-224.example.org;
# }
# subnet 10.0.29.0 netmask 255.255.255.0 {
# option routers rtr-29.example.org;
# }
# pool {
# allow members of "foo";
# range 10.17.224.10 10.17.224.250;
# }
# pool {
# deny members of "foo";
# range 10.0.29.10 10.0.29.230;
# }
#}