Actions
Feature #8849
closedDHCP Custom configuration
Start date:
08/29/2018
Due date:
% Done:
0%
Estimated time:
Plus Target Version:
Release Notes:
Description
I would suggest a field so we can use additional settings. There is the possibility of making several subnet with use of virtual ip. follows an example.
Custom configuration lines
subnet 172.20.101.0 netmask 255.255.255.252 {
server-identifier 172.20.101.1;
option subnet-mask 255.255.255.252;
option broadcast-address 172.20.101.3;
option routers 172.20.101.1;
range 172.20.101.2 172.20.101.2;
}
subnet 172.20.102.0 netmask 255.255.255.252 {
server-identifier 172.20.102.1;
option subnet-mask 255.255.255.252;
option broadcast-address 172.20.102.3;
option routers 172.20.102.1;
range 172.20.102.2 172.20.102.2;
}
subnet 172.20.103.0 netmask 255.255.255.252 {
server-identifier 172.20.103.1;
option subnet-mask 255.255.255.252;
option broadcast-address 172.20.103.3;
option routers 172.20.103.1;
range 172.20.103.2 172.20.103.2;
}
subnet 172.20.104.0 netmask 255.255.255.252 {
server-identifier 172.20.104.1;
option subnet-mask 255.255.255.252;
option broadcast-address 172.20.104.3;
option routers 172.20.104.1;
range 172.20.104.2 172.20.104.2;
}
subnet 172.20.105.0 netmask 255.255.255.252 {
server-identifier 172.20.105.1;
option subnet-mask 255.255.255.252;
option broadcast-address 172.20.105.3;
option routers 172.20.105.1;
range 172.20.105.2 172.20.105.2;
}
Updated by Luiz Souza over 6 years ago
- Tracker changed from Bug to Feature
- Affected Architecture deleted (
amd64)
Actions