From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from pony.its.uwo.ca([129.100.2.63]) (1496 bytes) by braille.uwo.ca via smail with P:esmtp/D:aliases/T:pipe (sender: ) id for ; Tue, 10 Apr 2001 21:02:00 -0400 (EDT) (Smail-3.2.0.102 1998-Aug-2 #2 built 1999-Sep-5) Received: from ignatious (c716099-a.rchdsn1.tx.home.com [24.7.105.70]) by pony.its.uwo.ca (8.10.2/8.10.2) with ESMTP id f3B12Am17040 for ; Tue, 10 Apr 2001 21:02:10 -0400 (EDT) Received: from cpt.kirk (helo=localhost) by ignatious with local-esmtp (Exim 3.12 #1 (Debian)) id 14n9JZ-0000LX-00 for ; Tue, 10 Apr 2001 20:20:57 -0500 Date: Tue, 10 Apr 2001 20:20:57 -0500 (CDT) From: Kirk Wood X-Sender: cpt.kirk@ignatious To: speakup@braille.uwo.ca Subject: Re: specifying an ip In-Reply-To: <20010410175901.A3903@uark.edu> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII List-Id: I doubt it is an all or nothing situation with dhcp. If so, then we have just found an area that microslop is better. I just really doubt this. But having said that, I am wondering why you can't get gateway and dns information from dhcp. The only thing I can come up with is that your network admin people are goobers. Not that this would make them unique, but this is basic dhcp stuff here. In fact, it is the primary reason dhcp was implimented. The mere assigning of an ip address is easily handled by bootp protocol. ======= Kirk Wood Cpt.Kirk@1tree.net Nothing is hard if you know the answer or are used to doing it.