Ubuntu LTS 18.04 配置DHCP Server
1. 安装DHCP服务
apt install isc-dhcp-server
2. 修改网络规划
vim /etc/netplan/50-cloud-init.yaml
/etc/netplan/50-cloud-init.yaml
-双网卡设备
- enpls0 作为DHCP Client
- enx000ec6b88013 作为DHCP Server , dhcp4: false.配置IP地址为[192.168.143.1/24]，子网掩码24位
# This file is generated from information provided by
# the datasource. Changes to it will not persist across an instance.
# To disable cloud-init's network configuration capabilities, write a file
# /etc/cloud/cloud.cfg.d/99-disable-network-config.cfg with the following:
# network: {config: disabled}
network:
ethernets:
enp1s0:
dhcp4: true
enx000ec6b88013:
dhcp4: false
addresses: [192.168.143.1/24]
version: 2
2.1 启用网络规划
netplan apply
3. 查看网络信息
ifconfig
显示内容如下
enp1s0: flags=4163 mtu 1500
inet 192.168.2.49 netmask 255.255.255.0 broadcast 192.168.2.255
inet6 fe80::2e1:5cff:fe68:184b prefixlen 64 scopeid 0x20
ether 00:e1:5c:68:18:4b txqueuelen 1000 (Ethernet)
RX packets 327840 bytes 135839626 (135.8 MB)
RX errors 0 dropped 6736 overruns 0 frame 0
TX packets 266509 bytes 118556637 (118.5 MB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
enx000ec6b88013: flags=4163 mtu 1500
inet 192.168.143.1 netmask 255.255.255.0 broadcast 192.168.143.255
inet6 fe80::20e:c6ff:feb8:8013 prefixlen 64 scopeid 0x20
ether 00:0e:c6:b8:80:13 txqueuelen 1000 (Ethernet)
RX packets 275936 bytes 115383452 (115.3 MB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 251287 bytes 136094852 (136.0 MB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
lo: flags=73 mtu 65536
inet 127.0.0.1 netmask 255.0.0.0
inet6 ::1 prefixlen 128 scopeid 0x10
loop txqueuelen 1000 (Local Loopback)
RX packets 164 bytes 20569 (20.5 KB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 164 bytes 20569 (20.5 KB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
4. 配置DHCP Server
4.1 修改 /etc/default/isc-dhcp-serve
vim /etc/default/isc-dhcp-server
配置ifconfig中的目标主机网卡网卡地址，该网卡必须是手动获取IP的方式不能是DHCP Client
INTERFACESv4="enx000ec6b88013"
- /etc/default/isc-dhcp-server
# Defaults for isc-dhcp-server (sourced by /etc/init.d/isc-dhcp-server)
# Path to dhcpd's config file (default: /etc/dhcp/dhcpd.conf).
#DHCPDv4_CONF=/etc/dhcp/dhcpd.conf
#DHCPDv6_CONF=/etc/dhcp/dhcpd6.conf
# Path to dhcpd's PID file (default: /var/run/dhcpd.pid).
#DHCPDv4_PID=/var/run/dhcpd.pid
#DHCPDv6_PID=/var/run/dhcpd6.pid
# Additional options to start dhcpd with.
# Don't use options -cf or -pf here; use DHCPD_CONF/ DHCPD_PID instead
#OPTIONS=""
# On what interfaces should the DHCP server (dhcpd) serve DHCP requests?
# Separate multiple interfaces with spaces, e.g. "eth0 eth1".
INTERFACESv4="enx000ec6b88013"
INTERFACESv6=""
4.2 设置DHCP租期
vim /etc/dhcp/dhcpd.conf
default-lease-time 86400;
max-lease-time 86400;
4.3 配置DHCP信息
subnet 192.168.143.0 netmask 255.255.255.0 {
# Specify the default gateway address
option routers 192.168.143.1;
# Specify the subnet-mask
option subnet-mask 255.255.255.0;
# Specify the range of leased IP addresses
range 192.168.143.50 192.168.143.200;
}
4.4 修改 domain-name && domain-name-servers
option domain-name "www.baidu.com";
option domain-name-servers 8.8.8.8, 114.114.114.114;
5. 启动服务
systemctl enable isc-dhcp-server #开机自启动
systemctl restart isc-dhcp-server # 重启服务
- /etc/dhcp/dhcpd.conf
# dhcpd.conf
#
# Sample configuration file for ISC dhcpd
#
# Attention: If /etc/ltsp/dhcpd.conf exists, that will be used as
# configuration file instead of this file.
#
# option definitions common to all supported networks...
option domain-name "www.baidu.com";
option domain-name-servers 8.8.8.8, 114.114.114.114;
default-lease-time 86400;
max-lease-time 86400;
# 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;
# 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.
#subnet 10.152.187.0 netmask 255.255.255.0 {
#}
# This is a very basic subnet declaration.
subnet 192.168.143.0 netmask 255.255.255.0 {
# Specify the default gateway address
option routers 192.168.143.1;
# Specify the subnet-mask
option subnet-mask 255.255.255.0;
# Specify the range of leased IP addresses
range 192.168.143.50 192.168.143.200;
}
# 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.example.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.example.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;
# }
#}