From owner-freebsd-current  Tue Oct  6 07:39:04 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id HAA27962
          for freebsd-current-outgoing; Tue, 6 Oct 1998 07:39:04 -0700 (PDT)
          (envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from goliath.camtech.net.au (goliath.camtech.net.au [203.5.73.2])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA27851;
          Tue, 6 Oct 1998 07:38:43 -0700 (PDT)
          (envelope-from thyerm@camtech.net.au)
Received: from camtech.net.au (dialup-ad-10-31.camtech.net.au [203.28.1.159]) by goliath.camtech.net.au (8.8.5/8.8.2) with ESMTP id AAA17727; Wed, 7 Oct 1998 00:08:02 +0930 (CST)
Message-ID: <361A2B55.AE47C1A0@camtech.net.au>
Date: Wed, 07 Oct 1998 00:08:13 +0930
From: Matthew Thyer <thyerm@camtech.net.au>
X-Mailer: Mozilla 4.06 [en] (X11; U; FreeBSD 3.0-BETA i386)
MIME-Version: 1.0
To: freebsd-questions@FreeBSD.ORG, freebsd-current@FreeBSD.ORG
Subject: 2.2.7 sysinstall failure to configure network interface
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

I have had to install two 2.2.7 systems recently over the net and
sysinstall failed to configure the network interface in both cases.

I think it was either an ed0 or an ep0 device.

The workaround that worked in both cases was to run an emergency
shell and to configure the interface and add the default route
manually.  Then sysinstall worked perfectly.  (maybe the route add
was not required - I didn't have time to experiment).

This was after solving all other problems such as BIOSes that reserve
interrupts for PCI or PnP cards (when I wanted irq 10 for an ISA card).
Also we made sure the cards were set to the settings that the GENERIC
kernel wanted.

I cannot give further information as these were other peoples
machines that I was just advising on.  (And I'm not meant to 'play'
with FBSD at work since I do far too much of that already :)

I just find it odd that the same work around was required for two
entirely different machines.

Maybe it is something to do with my work network ??.... a switched
network (CISCO equip).  Also our routers do not provide RIP updates
(intentionally).  I am not allowed to provide anymore info on the
network.

Everything worked fine with the workaround.

I just wanted to report this as a possible problem although I realise
the report is useless without information on hardware etc.

Perhaps others have had the same experience ?

-- 
/=====================================================================\
|Work: Matthew.Thyer@dsto.defence.gov.au | Home: thyerm@camtech.net.au|
\=====================================================================/
"If it is true that our Universe has a zero net value for all conserved
quantities, then it may simply be a fluctuation of the vacuum of some
larger space in which our Universe is imbedded. In answer to the
question of why it happened, I offer the modest proposal that our
Universe is simply one of those things which happen from time to time."
 E. P. Tryon   from "Nature" Vol.246 Dec.14, 1973

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message