From owner-freebsd-questions Sat Sep 20 00:24:14 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id AAA22574 for questions-outgoing; Sat, 20 Sep 1997 00:24:14 -0700 (PDT) Received: from Bayou.UH.EDU (jef53313@Bayou.UH.EDU [129.7.1.7]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id AAA22541 for ; Sat, 20 Sep 1997 00:24:08 -0700 (PDT) Received: from localhost (jef53313@localhost) by Bayou.UH.EDU (8.8.7/8.8.7) with SMTP id CAA16747; Sat, 20 Sep 1997 02:24:03 -0500 (CDT) Date: Sat, 20 Sep 1997 02:24:03 -0500 (CDT) From: Jonathan Fosburgh To: Doug White cc: freebsd-questions@FreeBSD.ORG Subject: Re: EtherExpress 16 In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-questions@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Fri, 19 Sep 1997, Doug White wrote: > On Thu, 18 Sep 1997, Jonathan Fosburgh wrote: > > > > ``dynamic'' in what sense? Does your network use DHCP, BOOTP or what? > > > > > > Have you considered applying to your network admin to have a static > > > address for your computer? We have spare space in our subnets here at the > > > UO to allocate some static addresses. The rest are done by DHCP. > > > > > I talked to one of the sysadmins here and he said that the IP is assigned > > everytime the computer tries to connect to the net. There is no way to get > > a static address at least that he knew of. I will be talking to someone > > else about this later so hopefully I can get some good news in that > > respect, but the guy I talked to said he thinks it is using DHCP. > > Well, I would think that they have network equipment that depends on a > static IP (like a router interface) and left some extra space for > expansion. > > The DHCP server doesn't have to know about these statics. You just pick > one and get a nameserver entry added that points to that IP. Saves a lot > of headaches. :) > > If they don't want to budge that way, and based on what you say I assume > you're on DHCP, then look into the wide-dhcp port (in ports/net). > I looked through the old postings to this list and eventually got together enough info to run the dhcp client and now my net card works like a charm. :) Thanks for the help.