
Received: from ietf.nri.reston.va.us by IETF.CNRI.Reston.VA.US id aa10342;
          13 May 94 14:54 EDT
Received: from CNRI.RESTON.VA.US by IETF.CNRI.Reston.VA.US id aa10338;
          13 May 94 14:54 EDT
Received: from sol.cs.bucknell.edu by CNRI.Reston.VA.US id aa15805;
          13 May 94 14:54 EDT
Received: from ftp.com (wd40.ftp.com) by sol (4.1/Bucknell-2.0)
	id <AA19965@sol>; Fri, 13 May 94 14:14:55 EDT
Received: from ftp.com by ftp.com  ; Fri, 13 May 1994 14:14:49 -0400
Received: from wco.ftp.com by ftp.com  ; Fri, 13 May 1994 14:14:49 -0400
Date: Fri, 13 May 94 11:12:18 PDT
Message-Id: <9405131812.AA19644@mailhost.wco.ftp.com>
Received: from zoi (zoi.wco.ftp.com) by mailhost.wco.ftp.com; Fri, 13 May 94 11:12:18 PDT
X-Sender: veizades@wco.ftp.com
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
To: host-conf@sol
Sender:ietf-archive-request@IETF.CNRI.Reston.VA.US
From: John Veizades <veizades@ftp.com>
Subject: DHCP and support from Routers
X-Mailer: <PC Eudora Version 2.0>

I just got off the phone with Cisco support I was trying to figure out how I 
could support multiple DHCP servers in a campus without having two on every 
subnet.  The Cisco manuals have a concept of helper addresses.  These are 
addresses to which BootP requests are forwarded to when they appear on the 
local net.  The Cisco support people tell me that they only support one such 
address per interface making implementing redundant DHCP server difficult 
for customers. 

Does anyone have any insights into this problem?

Does anyone have any suggestions on setting up such an infrastructure?

How do other router vendors implement this forwarding feature?

John...



Received: from ietf.nri.reston.va.us by IETF.CNRI.Reston.VA.US id aa13574;
          13 May 94 17:30 EDT
Received: from CNRI.RESTON.VA.US by IETF.CNRI.Reston.VA.US id aa13570;
          13 May 94 17:30 EDT
Received: from sol.cs.bucknell.edu by CNRI.Reston.VA.US id aa20119;
          13 May 94 17:30 EDT
Received: from FNAL.FNAL.GOV by sol (4.1/Bucknell-2.0)
	id <AA20306@sol>; Fri, 13 May 94 17:03:50 EDT
Received: from munin.fnal.gov by FNAL.FNAL.GOV (PMDF V4.2-12 #3998) id
 <01HCAOIHTB4G0025ML@FNAL.FNAL.GOV>; Fri, 13 May 1994 16:03:30 CDT
Received: from LOCALHOST.fnal.gov by munin.fnal.gov (4.1/SMI-4.1) id AA16886;
 Fri, 13 May 94 16:02:32 CDT
Date: Fri, 13 May 1994 16:02:31 -0500
Sender:ietf-archive-request@IETF.CNRI.Reston.VA.US
From: Matt Crawford <crawdad@munin.fnal.gov>
Subject: Re: DHCP and support from Routers
In-Reply-To: Your message of Fri,
 13 May 94 11:12:18 PDT. <9405131812.AA19644@mailhost.wco.ftp.com>
To: John Veizades <veizades@ftp.com>
Cc: host-conf@sol
Message-Id: <9405132102.AA16886@munin.fnal.gov>
Content-Transfer-Encoding: 7BIT

Multicast!  Multicast-smart DHCP servers, with requests forwarded by
multicast-smart routers to a reserved multicast address seem like a
natural solution.  Not today, maybe, but soon.

For today, I think you could forward BOOTP requests as directed
broadcasts and have multiple servers on one central subnet.
_________________________________________________________
Matt Crawford          crawdad@fnal.gov          Fermilab


> I just got off the phone with Cisco support I was trying to figure out how I 
> could support multiple DHCP servers in a campus without having two on every 
> subnet.  The Cisco manuals have a concept of helper addresses.  These are 
> addresses to which BootP requests are forwarded to when they appear on the 
> local net.  The Cisco support people tell me that they only support one such 
> address per interface making implementing redundant DHCP server difficult 
> for customers. 
> 
> Does anyone have any insights into this problem?
> 
> Does anyone have any suggestions on setting up such an infrastructure?
> 
> How do other router vendors implement this forwarding feature?
> 
> John...
> 



Received: from ietf.nri.reston.va.us by IETF.CNRI.Reston.VA.US id aa00904;
          15 May 94 6:12 EDT
Received: from CNRI.RESTON.VA.US by IETF.CNRI.Reston.VA.US id aa00900;
          15 May 94 6:12 EDT
Received: from sol.cs.bucknell.edu by CNRI.Reston.VA.US id aa02342;
          15 May 94 6:12 EDT
Received: from dsb835.edvz.sbg.ac.at ([141.201.1.2]) by sol (4.1/Bucknell-2.0)
	id <AA29013@sol>; Sun, 15 May 94 05:42:27 EDT
Message-Id: <9405150942.AA29013@sol>
Received: from DUNI17.edvz.sbg.ac.at by dsb835.edvz.sbg.ac.at (MX V4.0-1 VAX)
          with SMTP; Sun, 15 May 1994 11:42:00 MEZ
Sender:ietf-archive-request@IETF.CNRI.Reston.VA.US
From: "Franz Maier EDVZ/Univ.Salzburg" <maier@edvz.sbg.ac.at>
To: host-conf@sol
Date: Sun, 15 May 1994 11:41:59 MET1WET
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7BIT
Subject: 
X-Pmrqc:       1
Return-Receipt-To: "Franz Maier EDVZ/Univ.Salzburg" <maier@edvz.sbg.ac.at>
Priority: normal
X-Mailer:     Pegasus Mail/Windows (v1.11a)

subscribe Franz Maier


Received: from ietf.nri.reston.va.us by IETF.CNRI.Reston.VA.US id aa11311;
          26 May 94 15:40 EDT
Received: from CNRI.RESTON.VA.US by IETF.CNRI.Reston.VA.US id aa11307;
          26 May 94 15:40 EDT
Received: from sol.cs.bucknell.edu by CNRI.Reston.VA.US id aa15720;
          26 May 94 15:40 EDT
Received: from hp.com by sol.cs.bucknell.edu (4.1/Bucknell-2.0)
	id <AA25470@sol.cs.bucknell.edu>; Thu, 26 May 94 15:00:14 EDT
Received: from hppadan.waterloo.hp.com by hp.com with SMTP
	(1.36.108.7/15.5+IOS 3.13) id AA07738; Thu, 26 May 1994 12:00:09 -0700
Received: by hppadan.waterloo.hp.com
	(1.37.109.4/15.5+IOS 3.22) id AA06852; Thu, 26 May 94 15:00:04 -0400
Sender:ietf-archive-request@IETF.CNRI.Reston.VA.US
From: David Lapp <lapp@waterloo.hp.com>
Message-Id: <9405261900.AA06852@hppadan.waterloo.hp.com>
Subject: Next DHCP bake-off ? 
To: host-conf@sol.cs.bucknell.edu
Date: Thu, 26 May 1994 15:00:04 -0500 (EDT)
Cc: David Lapp <lapp@waterloo.hp.com>
X-Mailer: ELM [version 2.4 PL21]
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Content-Length: 921       


Following the DHCP Bake-off hosted by Mike Carney and Sun in
Chelmsford several of us discussed what should happen next.
It was generally agreed that another bake-off was in order.
I realize that Microsoft hosted a TCP/IP bake-off in April
which included DHCP testing but I know that many of us working
on DHCP couldn't attend. I would still like to see a DHCP specific
event occur.

So I'd like to see a show of hands from those who might be
interested attending another DHCP Bake-off. My current plans
are:

Date:	either Thurs. July 21 or Fri. July 22, 1994
Place:	Sheraton Centre Toronto

This is in the same location as, and immediately before the 
July IETF meeting. 

If anyone would prefer a different date I'm open to suggestions
but keep in mind that working around other people's summer
schedules could be a problem.

Dave Lapp
Hewlett-Packard Co.
Panacom Automation Div.

lapp@waterloo.hp.com
(519)-883-3051



Received: from ietf.nri.reston.va.us by IETF.CNRI.Reston.VA.US id aa13029;
          26 May 94 17:37 EDT
Received: from CNRI.RESTON.VA.US by IETF.CNRI.Reston.VA.US id aa13025;
          26 May 94 17:37 EDT
Received: from sol.cs.bucknell.edu by CNRI.Reston.VA.US id aa21930;
          26 May 94 17:37 EDT
Received: from Sun.COM by sol.cs.bucknell.edu (4.1/Bucknell-2.0)
	id <AA25709@sol.cs.bucknell.edu>; Thu, 26 May 94 17:04:53 EDT
Received: from East.Sun.COM (east.East.Sun.COM) by Sun.COM (sun-barr.Sun.COM)
	id AA14582; Thu, 26 May 94 14:02:45 PDT
Received: from suneast.East.Sun.COM by East.Sun.COM (4.1/SMI-4.1)
	id AA10691; Thu, 26 May 94 17:02:33 EDT
Received: from canoepoint.East.Sun.COM by suneast.East.Sun.COM (5.0/SMI-4.1-900117)
	id AA18271; Thu, 26 May 1994 17:02:32 +0500
Received: by canoepoint.East.Sun.COM (5.0/SMI-SVR4)
	id AA18640; Thu, 26 May 1994 17:02:30 +0500
Date: Thu, 26 May 1994 17:02:30 +0500
Sender:ietf-archive-request@IETF.CNRI.Reston.VA.US
From: Mike Carney - SunSelect Engineering <Mike.Carney@east.sun.com>
Message-Id: <9405262102.AA18640@canoepoint.East.Sun.COM>
To: host-conf@sol.cs.bucknell.edu, lapp@waterloo.hp.com
Subject: Re: Next DHCP bake-off ?
X-Sun-Charset: US-ASCII
Content-Length: 378


I'm interested in attending this. However, I'd like to see us make progress
toward rev'ing the spec to contain the changes made at the last DHCP-only
bakeoff (hosted by SunSelect) prior to another bakeoff. If the IESG
accepts the changes, then this event could be used to demonstrate multi-
vendor interoperability, and satisfy this requirement for full standard
status.

Mike


Received: from ietf.nri.reston.va.us by IETF.CNRI.Reston.VA.US id aa13268;
          26 May 94 17:55 EDT
Received: from CNRI.RESTON.VA.US by IETF.CNRI.Reston.VA.US id aa13264;
          26 May 94 17:55 EDT
Received: from sol.cs.bucknell.edu by CNRI.Reston.VA.US id aa22226;
          26 May 94 17:55 EDT
Received: from hp.com by sol.cs.bucknell.edu (4.1/Bucknell-2.0)
	id <AA25757@sol.cs.bucknell.edu>; Thu, 26 May 94 17:29:26 EDT
Received: from hppadan.waterloo.hp.com by hp.com with SMTP
	(1.36.108.7/15.5+IOS 3.13) id AA16930; Thu, 26 May 1994 14:29:24 -0700
Received: by hppadan.waterloo.hp.com
	(1.37.109.4/15.5+IOS 3.22) id AA00273; Thu, 26 May 94 17:29:07 -0400
Sender:ietf-archive-request@IETF.CNRI.Reston.VA.US
From: David Lapp <lapp@waterloo.hp.com>
Message-Id: <9405262129.AA00273@hppadan.waterloo.hp.com>
Subject: Re: Next DHCP bake-off ?
To: Mike Carney - SunSelect Engineering <Mike.Carney@east.sun.com>
Date: Thu, 26 May 1994 17:29:06 -0500 (EDT)
Cc: host-conf@sol.cs.bucknell.edu, lapp@waterloo.hp.com
In-Reply-To: <9405262102.AA18640@canoepoint.East.Sun.COM> from "Mike Carney - SunSelect Engineering" at May 26, 94 05:02:30 pm
X-Mailer: ELM [version 2.4 PL21]
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Content-Length: 654       

> 
> 
> I'm interested in attending this. However, I'd like to see us make progress
> toward rev'ing the spec to contain the changes made at the last DHCP-only
> bakeoff (hosted by SunSelect) prior to another bakeoff. If the IESG
> accepts the changes, then this event could be used to demonstrate multi-
> vendor interoperability, and satisfy this requirement for full standard
> status.
> 
Yes. Any outstanding changes to the spec. should be made before
we have another bake-off.

Hopefully, the approximately 2 months between now and July 22
will give us enough time to rev the spec and (possibly) change the
code despite it being summer :-)

Dave L.


Received: from ietf.nri.reston.va.us by IETF.CNRI.Reston.VA.US id aa01882;
          27 May 94 8:02 EDT
Received: from CNRI.RESTON.VA.US by IETF.CNRI.Reston.VA.US id aa01878;
          27 May 94 8:02 EDT
Received: from sol.cs.bucknell.edu by CNRI.Reston.VA.US id aa04195;
          27 May 94 8:02 EDT
Received: from mail.unigate1.unisys.com (sys1.unigate1.unisys.com) by sol.cs.bucknell.edu (4.1/Bucknell-2.0)
	id <AA00156@sol.cs.bucknell.edu>; Fri, 27 May 94 07:28:45 EDT
Received: from bb6k35.SIP.Unisys.COM ([192.63.20.35]) by mail.unigate1.unisys.com (4.1/SMI-4.1)
	id AA20465; Fri, 27 May 94 11:35:30 GMT
Received: by bb6k35.SIP.Unisys.COM (4.1/SMI-4.1)
	id AA05336; Fri, 27 May 94 07:28:12 EDT
Sender:ietf-archive-request@IETF.CNRI.Reston.VA.US
From: Mike Tehan - Enable <enmxt01@sip.unisys.com>
Message-Id: <9405271128.AA05336@bb6k35.SIP.Unisys.COM>
Subject: DHCP Implementations
To: Dynamic Host Configuration <host-conf@sol.cs.bucknell.edu>
Date: Fri, 27 May 1994 07:28:12 -0400 (EDT)
X-Mailer: ELM [version 2.4 PL21]
Content-Type: text
Content-Length: 552       

Has anyone developed a list of commercial and/or PD DHCP implementations?
If such a thing exists I would appreciate a copy or a pointer to its 
location.  If not, please e-mail information on any that you know of.

TIA, Mike T.
----------------------------------------------------------------------------
Mike Tehan                       | mtehan@enable.unisys.com
Unisys Network Enable            | Sorry, I seem to have left my clever .sig
Network Design Consultant        | in my other mail server.
Albany, NY                       | (518) 452-6240


Received: from ietf.nri.reston.va.us by IETF.CNRI.Reston.VA.US id aa07283;
          30 May 94 22:18 EDT
Received: from CNRI.RESTON.VA.US by IETF.CNRI.Reston.VA.US id aa07279;
          30 May 94 22:18 EDT
Received: from sol.cs.bucknell.edu by CNRI.Reston.VA.US id aa05993;
          30 May 94 22:18 EDT
Received: from REDIRECTEUR.ULAVAL.CA by sol.cs.bucknell.edu (4.1/Bucknell-2.0)
	id <AA14371@sol.cs.bucknell.edu>; Mon, 30 May 94 22:00:52 EDT
Received: by REDIRECTEUR.ULAVAL.CA; Mon, 30 May 94 13:18:56 EDT
Date: Mon, 30 May 94 13:18:53 EDT
Message-Id: <IvW7+gzVuha@REDIRECTEUR.ULAVAL.CA>
Sender:ietf-archive-request@IETF.CNRI.Reston.VA.US
From: DUMONT_ONEIL%CTI%ULAVAL@redirecteur.ulaval.ca
To: host-conf@sol.cs.bucknell.edu
Subject: macintosh DHCP client?
X-Incognito-Sn: 104
X-Incognito-Format: VERSION=1.70a ENCRYPTED=NO

I am currently looking for ways to dynamically allocate IP addresses on the 
Laval University campus (Quebec city, Canada). SOLARNET, the SUN Microsystems 
DHCP implementetion, seems to be just what we need except for the fact that it 
does not support the macintosh platform (as a client), which counts for about 
50% of the total number of potential DHCP clients. Can anybody recommend DHCP 
client software for the macintosh?


Received: from ietf.nri.reston.va.us by IETF.CNRI.Reston.VA.US id aa10456;
          30 May 94 23:22 EDT
Received: from CNRI.RESTON.VA.US by IETF.CNRI.Reston.VA.US id aa10452;
          30 May 94 23:22 EDT
Received: from sol.cs.bucknell.edu by CNRI.Reston.VA.US id aa11351;
          30 May 94 23:22 EDT
Received: from ftp.com (wd40.ftp.com) by sol.cs.bucknell.edu (4.1/Bucknell-2.0)
	id <AA14660@sol.cs.bucknell.edu>; Mon, 30 May 94 23:03:20 EDT
Received: from ftp.com by ftp.com  ; Mon, 30 May 1994 23:03:17 -0400
Received: from wco.ftp.com by ftp.com  ; Mon, 30 May 1994 23:03:17 -0400
Date: Mon, 30 May 94 20:00:31 PDT
Message-Id: <9405310300.AA29258@mailhost.wco.ftp.com>
Received: from vida230 (vida202.wco.ftp.com) by mailhost.wco.ftp.com; Mon, 30 May 94 20:00:32 PDT
X-Sender: veizades@wco.ftp.com
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
To: DUMONT_ONEIL%CTI%ULAVAL@redirecteur.ulaval.ca, 
    host-conf@sol.cs.bucknell.edu
Sender:ietf-archive-request@IETF.CNRI.Reston.VA.US
From: John Veizades <veizades@ftp.com>
Subject: Re: macintosh DHCP client?
X-Mailer: <PC Eudora Version 2.0>

At 01:18 PM 5/30/94 EDT, DUMONT_ONEIL%CTI%ULAVAL@redirecteur.ulaval.ca wrote:
>I am currently looking for ways to dynamically allocate IP addresses on the 
>Laval University campus (Quebec city, Canada). SOLARNET, the SUN Microsystems 
>DHCP implementetion, seems to be just what we need except for the fact that it 
>does not support the macintosh platform (as a client), which counts for about 
>50% of the total number of potential DHCP clients. Can anybody recommend DHCP 
>client software for the macintosh?

Currently MacTCP 2.0.4 does not support DHCP and I believe that there are no 
plans to add DHCP functionality to MacTCP 2.0.4.  MacTCP 3.0 which I believe 
Apple is working on currently will support DHCP and we (FTP Software, Inc) 
are working with Apple to test their implementation of DHCP.

You can support the dynamic configuration of Macs using BootP, MacIP or the 
Dynamic opptions that MacTCP supports.  The MacIP protocol supports a type 
of IP address and stack configuration that is very similar to DHCP the only 
draw back is that you have to encapsulate IP datagrams in AppleTalk 
datagrams.  The dynamic options was designed for networks that can allocate 
a range of IP addresses for use by the Macs.  The Macs choose an address in 
that range at random and then ARP for its presence to check if it is in use 
and eventually choose and unused address to use.  The draw back he is that 
the rest of the stack configuration parameters are not configured.

The DHCP server product from FTP Software supports Macintoshes using BootP 
configuration and will support MacTCP 3.0 using DHCP.

John Veizades...
Former MacTCP Lead Engineer
Manager DHCP Client and Servers for Windows, DOS and Windows NT
FTP Software, Inc.



Received: from ietf.nri.reston.va.us by IETF.CNRI.Reston.VA.US id aa03168;
          31 May 94 9:16 EDT
Received: from CNRI.RESTON.VA.US by IETF.CNRI.Reston.VA.US id aa03164;
          31 May 94 9:16 EDT
Received: from sol.cs.bucknell.edu by CNRI.Reston.VA.US id aa00341;
          31 May 94 9:16 EDT
Received: from dpnstr.dukepower.com by sol.cs.bucknell.edu (4.1/Bucknell-2.0)
	id <AA18774@sol.cs.bucknell.edu>; Tue, 31 May 94 08:56:48 EDT
Received: from dpcmail.dukepower.com by dpnstr.dukepower.com (AIX 3.2/UCB 5.64/4.03)
          id AA12095; Tue, 31 May 1994 08:57:55 -0400
Received: from ccMail by DPCMAIL.DUKEPOWER.COM
	id AA770399466 Tue, 31 May 94 08:51:06 EST
Date: Tue, 31 May 94 08:51:06 EST
Sender:ietf-archive-request@IETF.CNRI.Reston.VA.US
From: "Goodman, Randy F" <RGOODMAN@dpcmail.dukepower.com>
Encoding: 294 Text
Message-Id: <9404317703.AA770399466@DPCMAIL.DUKEPOWER.COM>
To: host-conf@sol.cs.bucknell.edu
Cc: RGOODMAN@dpcmail.dukepower.com
Subject: dhcp client and server


     i am looking for a workable dhcp client and server that i can bring in 
     house to help with the addressing requirements of my mobile customers.
     does anyone have a recommendation?
     
     my customers are windows 3.1 running FTP's PC\TCP 2.2+ or Novell's IP 
     kernal.

