Re: Which servers support secondary network numbers?
Tim Peiffer <peiffer@nts.umn.edu> Fri, 16 August 1996 20:57 UTC
Received: from ietf.org by ietf.org id aa01061; 16 Aug 96 16:57 EDT
Received: from cnri by ietf.org id aa01057; 16 Aug 96 16:57 EDT
Received: from reef.bucknell.edu by CNRI.Reston.VA.US id aa14099;
16 Aug 96 16:57 EDT
Received: from localhost by reef.bucknell.edu with SMTP
(5.65/IDA-1.2.8) id AA27942; Fri, 16 Aug 1996 16:53:22 -0400
Date: Fri, 16 Aug 1996 16:53:22 -0400
Message-Id: <199608162020.AA23887@mome.unet.umn.edu>
Errors-To: droms@bucknell.edu
Reply-To: dhcp-v4@bucknell.edu
Originator: dhcp-v4@bucknell.edu
X-Orig-Sender: dhcp-v4@bucknell.edu
Precedence: bulk
Sender: ietf-archive-request@ietf.org
From: Tim Peiffer <peiffer@nts.umn.edu>
To: Multiple recipients of list <dhcp-v4@bucknell.edu>
Subject: Re: Which servers support secondary network numbers?
X-Listprocessor-Version: 6.0c -- ListProcessor by Anastasios Kotsikonas
X-Comment: Discussion of DHCP for IPv4
Mime-Version: 1.0
X-Mailer: ELM [version 2.4 PL21]
The Internet Software Consortium is developing a dhcp server as a reference standard. It can handle manual assignments and dynamic assigned addresses from pools on any of the networks (physical or logical) assigned to the interface.. ftp://ftp.fugue.com:/pub/DHCPD-BETA-4.7.tar.gz I have seen references to the server the wobus faq, but the FAQ is woefully out of date. Ted Lemon is doing good work on this package. Tim Peiffer peiffer@nts.umn.edu Networking and Telecommunications Services University of Minnesota +1 612 626 7884 desk 2221 University Ave +1 612 625 0006 problems Suite 145 +1 612 626 1002 fax Minneapolis MN 55455, USA excerpts from dhcpd.conf: shared-network FUGUE # option definitions common to this shared network. option subnet-mask 255.255.255.224 default-lease-time 600 max-lease-time 7200 # One of the two IP subnets that share this physical network # # Address ranges can be specified for each subnet attached to # a shared network. Since these subnets share the same physical # network, addresses are pooled together, and assignments are made # without regard to the actual subnet. If the optional dynamic-bootp # keyword is given in the address range declaration, then addresses # in that range can be assigned either with the DHCP protocol or the # BOOTP protocol; otherwise, only DHCP clients will have addresses # allocated from the address range. # # Note that each IP subnet can have its own options specific to that subnet. # options that aren't specified in the subnet are taken from the shared # network (if any) and then from the global option list. subnet 204.254.239.0 netmask 255.255.255.224 range 204.254.239.10 204.254.239.20 option broadcast-address 204.254.239.31 option routers prelude.fugue.com # The other subnet that shares this physical network subnet 204.254.239.32 netmask 255.255.255.224 range dynamic-bootp 204.254.239.10 204.254.239.20 option broadcast-address 204.254.239.31 option routers snarg.fugue.com;
- Which servers support secondary network numbers? John M. Wobus
- Re: Which servers support secondary network numbe… James E. Drews
- Re: Which servers support secondary network numbe… Allen Lung
- Re: Which servers support secondary network numbe… Hiroto Shibuya
- Re: Which servers support secondary network numbe… Michael J. Lewis
- Re: Which servers support secondary network numbe… James E. Drews
- Re: Which servers support secondary network numbe… Hiroto Shibuya
- Re: Which servers support secondary network numbe… Anurag Narula
- Re: Which servers support secondary network numbe… Tim Peiffer
- Re: Which servers support secondary network numbe… jacob.hall
- Re: Which servers support secondary network numbe… jacob.hall