红联Linux门户
Linux帮助

如何实现一台服务器为两个不同网段提供DHCP服务?

发布时间:2009-04-17 15:48:59来源:红联作者:jason_bourne
背景:我有一台DELL 1750服务器,双千兆网卡。公司的网络环境是:内外网物理隔离。即内网是10.98.*.*网段,外网是192.168.*.*网段。之前有两台 DHCP服务器分别为两个网段提供DHCP服务。并且,每个网段都下分很多小网段对应各个部门,举例来讲:10.98.*.*网段,又分成 10.98.140.*、10.98.155.*、10.98.151.*等等网段。而192.168.*.*网段,又分成192.168.16.*、 192.168.32.*、192.168.19.*等等网段。
问题:我现在可否将服务器的两块网卡分别配成两个网段的IP地址,然后分别为两个网段提供DHCP服务?如果可以的话,那随之而来的问题是,/etc /dhcpd.conf文件怎么写?把之前两台机器所有的配置全部粘贴进去吗?我觉得不太可能。如果全部放到一个配置文件里,两个网卡怎么区分哪个配置是对应它的呢?
谢谢大家!
文章评论

共有 12 条评论

  1. qq9293000079 于 2011-07-20 08:51:17发表:

    建两个作用域,然后再来一个DHCP中继代理就行,路过打打酱油

  2. qq9293000079 于 2011-07-20 08:51:03发表:

    建两个作用域,然后再来一个DHCP中继代理就行,路过打打酱油

  3. cnpliu 于 2011-07-19 21:03:51发表:

    写的挺清楚的奥

  4. n10th 于 2011-07-18 23:17:20发表:

    在dhcp服务的主配置文件中添加两个地址池可实现与windows中超级作用域相同的功能

  5. lcy1216 于 2011-07-15 19:50:51发表:

    路过 学习一下

  6. jhasheng 于 2011-06-30 21:09:02发表:

    Thanks for your share!

  7. zhenwei252 于 2009-07-03 10:28:27发表:

    以上内容摘自gary168的[RHEL5企业级Linux服务攻略]--DHCP服务全攻略
    http://www.linuxdiyf.com/bbs/thread-133747-1-1.html

  8. zhenwei252 于 2009-07-03 10:27:12发表:

    DHCP多作用域设置
    DHCP服务器使用单一的作用域,大部分时间能够满足网络的需求,但是有些特殊情况下,按照网络规划我们需要配置多作用域。
    网络中如果计算机和其他设备数量增加,IP地址需要进行扩容才能满足需求。小型网络可以对所有设备重新分配IP地址,其网络内部客户机和服务器数量较少,实现起来比较简单。但如果是一个大型网络,重新配置整个网络的IP地址是不明智的,如果操作不当,可能会造成通信暂时中断以及其他网络故障。我们可以通过多作用域的设置,即DHCP服务器发布多个作用域实现IP地址增容的目的。
    公司IP地址规划为192.168.2.0/24网段,可以容纳254台设备,使用DHCP服务器建立一个192.168.2.0网段的作用域,动态管理网络IP地址,但网络规模扩大到500台机器,显然一个C类网的地址无法满足要求了。这时,可以再为DHCP服务器添加一个新作用域,管理分配192.168.3.0/24网段的IP地址,为网络增加254个新的IP地址,这样既可以保持原有IP地址的规划,又可以扩容现有的网络IP地址。
    (1)简单实现DHCP多作用域
    对于多作用域的配置,必须保证DHCP服务器能够侦听所有子网客户机的请求信息,下面将讲解配置多作用域的基本方法,为DHCP添加多个网卡连接每个子网,并发布多个作用域的声明。
    注意:划分子网时,如果选择直接配置多作用域实现动态IP分配的任务,则必须要为DHCP服务器添加多块网卡,并配置多个IP地址,否则DHCP服务器只能分配与其现有网卡IP地址对应网段的作用域。
    采用双网卡实现两个作用域

    1)网卡配置IP地址
    DHCP服务器有多块网卡时,需要使用ifconfig命令为每块网卡配置独立的IP地址,但要注意,IP地址配置的网段要与DHCP服务器发布的作用域对应哈~
    ifconfig eth0 192.168.2.1 netmask 255.255.255.0
    ifconfig eth1 192.168.3.1 netmask 255.255.255.0

    2)编辑dhcpd.conf主配置文件
    当DHCP服务器网络环境搭建完毕后,我们可以编辑dhcpd.conf主配置文件完成多作用域的设置。
    ddns-update-style none;
    ignore client-updates;
    subnet 192.168.2.0 netmask 255.255.255.0 {
    # --- default gateway
    option routers 192.168.2.1;
    option subnet-mask 255.255.255.0;
    option nis-domain "domain.org";
    option domain-name "domain.org";
    option domain-name-servers 192.168.2.2;
    option time-offset -18000; # Eastern Standard Time
    # option ntp-servers 192.168.1.1;
    # option netbios-name-servers 192.168.1.1;
    # --- Selects point-to-point node (default is hybrid). Don't change this unless
    # -- you understand Netbios very well
    # option netbios-node-type 2;
    range dynamic-bootp 192.168.2.50 192.168.2.250;
    default-lease-time 21600;
    max-lease-time 43200;
    # we want the nameserver to appear at a fixed address
    host ns {
    next-server marvin.redhat.com;
    hardware ethernet 12:34:56:78:AB:CD;
    fixed-address 207.175.42.254;
    }
    }
    subnet 192.168.3.0 netmask 255.255.255.0 {
    # --- default gateway
    option routers 192.168.3.1;
    option subnet-mask 255.255.255.0;
    option nis-domain "domain.org";
    option domain-name "domain.org";
    option domain-name-servers 192.168.2.2;
    option time-offset -18000; # Eastern Standard Time
    # option ntp-servers 192.168.1.1;
    # option netbios-name-servers 192.168.1.1;
    # --- Selects point-to-point node (default is hybrid). Don't change this unless
    # -- you understand Netbios very well
    # option netbios-node-type 2;
    range dynamic-bootp 192.168.3.50 192.168.3.250;
    default-lease-time 21600;
    max-lease-time 43200;
    max-lease-time 43200;
    }

    保存退出哈~
    3)测试验证
    重启DHCP服务后检查系统日志,检测配置是否成功,使用tail命令动态显示日志信息。
    tail -F /etc/log/messages

    经过设置,对于DHCP服务器将通过eth0和eth1两块网卡侦听客户机的请求,并发送相应的回应。
    Jan 19 16:02:51 rhel5 dhcpd: DHCPDISCOVER from 00:19:21:bd:a3:da via eth1
    Jan 19 16:02:51 rhel5 dhcpd: DHCPDISCOVER from 00:19:21:bd:a3:da via eth0
    Jan 19 16:02:52 rhel5 dhcpd: DHCPOFFER . 192.168.3.250 to 00:19:21:bd:a3:da (mis) via eth1
    Jan 19 16:02:52 rhel5 dhcpd: DHCPOFFER . 192.168.2.250 to 00:19:21:bd:a3:da (mis) via eth0
    Jan 19 16:02:52 rhel5 dhcpd: DHCPREQUEST for 192.168.3.250 (192.168.3.1) from 00:19:21:bd:a3:da (mis) via eth1
    Jan 19 16:02:52 rhel5 dhcpd: DHCPACK . 192.168.3.250 to 00:19:21:bd:a3:da (mis) via eth1
    Jan 19 16:02:52 rhel5 dhcpd: DHCPREQUEST for 192.168.3.250 (192.168.3.1) from 00:19:21:bd:a3:da (mis) via eth0: ignored (not authoritative).
    Jan 19 16:02:53 rhel5 dhcpd: DHCPDISCOVER from 00:19:21:bd:a3:da (mis) via eth1
    Jan 19 16:02:53 rhel5 dhcpd: DHCPOFFER . 192.168.3.250 to 00:19:21:bd:a3:da (mis) via eth1
    Jan 19 16:02:53 rhel5 dhcpd: DHCPDISCOVER from 00:19:21:bd:a3:da (mis) via eth0
    Jan 19 16:02:53 rhel5 dhcpd: DHCPOFFER . 192.168.2.250 to 00:19:21:bd:a3:da (mis) via eth0
    Jan 19 16:02:53 rhel5 dhcpd: DHCPREQUEST for 192.168.3.250 (192.168.3.1) from 00:19:21:bd:a3:da (mis) via eth1
    Jan 19 16:02:53 rhel5 dhcpd: DHCPACK . 192.168.3.250 to 00:19:21:bd:a3:da (mis) via eth1
    Jan 19 16:02:53 rhel5 dhcpd: DHCPREQUEST for 192.168.3.250 (192.168.3.1) from 00:19:21:bd:a3:da (mis) via eth0: ignored (not authoritative).
    Jan 19 16:02:54 rhel5 dhcpd: DHCPDISCOVER from 00:19:21:bd:a3:da (mis) via eth1
    Jan 19 16:02:54 rhel5 dhcpd: DHCPOFFER . 192.168.3.250 to 00:19:21:bd:a3:da (mis) via eth1
    Jan 19 16:02:54 rhel5 dhcpd: DHCPDISCOVER from 00:19:21:bd:a3:da (mis) via eth0
    Jan 19 16:02:54 rhel5 dhcpd: DHCPOFFER . 192.168.2.250 to 00:19:21:bd:a3:da (mis) via eth0
    Jan 19 16:02:54 rhel5 dhcpd: DHCPREQUEST for 192.168.3.250 (192.168.3.1) from 00:19:21:bd:a3:da (mis) via eth1
    Jan 19 16:02:54 rhel5 dhcpd: DHCPACK . 192.168.3.250 to 00:19:21:bd:a3:da (mis) via eth1
    Jan 19 16:02:54 rhel5 dhcpd: DHCPREQUEST for 192.168.3.250 (192.168.3.1) from 00:19:21:bd:a3:da (mis) via eth0: ignored (not authoritative).
    Jan 19 16:02:55 rhel5 dhcpd: DHCPDISCOVER from 00:19:21:bd:a3:da (mis) via eth1
    Jan 19 16:02:55 rhel5 dhcpd: DHCPOFFER . 192.168.3.250 to 00:19:21:bd:a3:da (mis) via eth1
    Jan 19 16:02:55 rhel5 dhcpd: DHCPDISCOVER from 00:19:21:bd:a3:da (mis) via eth0
    Jan 19 16:02:55 rhel5 dhcpd: DHCPOFFER . 192.168.2.250 to 00:19:21:bd:a3:da (mis) via eth0
    Jan 19 16:02:55 rhel5 dhcpd: DHCPREQUEST for 192.168.3.250 (192.168.3.1) from 00:19:21:bd:a3:da (mis) via eth1
    Jan 19 16:02:55 rhel5 dhcpd: DHCPACK . 192.168.3.250 to 00:19:21:bd:a3:da (mis) via eth1
    Jan 19 16:02:55 rhel5 dhcpd: DHCPREQUEST for 192.168.3.250 (192.168.3.1) from 00:19:21:bd:a3:da (mis) via eth0: ignored (not authoritative).

  9. kinglisa 于 2009-06-24 09:32:55发表:

    想知道

  10. zrl2088 于 2009-06-18 08:28:40发表:

    我也想知道

  11. jason_bourne 于 2009-04-17 17:21:29发表:

    2# xylp
    LINUX里也有超级作用域的概念???能说的具体点吗?

  12. xylp 于 2009-04-17 17:01:11发表:

    配置超级作用域