From owner-freebsd-hackers  Wed Jan 17 09:21:09 1996
Return-Path: owner-hackers
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.3/8.7.3) id JAA23009
          for hackers-outgoing; Wed, 17 Jan 1996 09:21:09 -0800 (PST)
Received: from dg-rtp.dg.com (dg-rtp.rtp.dg.com [128.222.1.2])
          by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id JAA23003
          for <freebsd-hackers@freefall.FreeBSD.org>; Wed, 17 Jan 1996 09:21:01 -0800 (PST)
Received: by dg-rtp.dg.com (5.4R3.10/dg-rtp-v02)
	id AA11651; Wed, 17 Jan 1996 12:20:21 -0500
Received: from ponds by dg-rtp.dg.com.rtp.dg.com; Wed, 17 Jan 1996 12:20 EST
Received: from lakes (lakes [192.96.3.39]) by ponds.UUCP (8.6.12/8.6.5) with ESMTP id HAA20802; Wed, 17 Jan 1996 07:02:24 -0500
Received: (from rivers@localhost) by lakes (8.6.12/8.6.9) id HAA23899; Wed, 17 Jan 1996 07:11:27 -0500
Date: Wed, 17 Jan 1996 07:11:27 -0500
From: Thomas David Rivers <ponds!rivers@dg-rtp.dg.com>
Message-Id: <199601171211.HAA23899@lakes>
To: uriah.heep.sax.de!joerg_wunsch@dg-rtp.dg.com
Subject: Re: Another problem with sysinstall with SL/IP.
Cc: freebsd-hackers@freefall.FreeBSD.org
Content-Type: text
Sender: owner-hackers@FreeBSD.ORG
Precedence: bulk

> > 
> > However, I just noticed in the sysinstall generated /etc/sysconfig,
> > it produced:
> > 
> > network_interfaces="cuaa0 lo0"
> > ifconfig_cuaa0="inet ..."
> > 
> > 
> > which, of course, doesn't work - these should be:
> > 
> > network_interfaces="sl0 lo0"
> > ifconfig_slo="inet ..."
> 
> No, it must be
> 
> network_interfaces="lo0"
> 
> sl0 cannot be initialized at boot time, since the initialization can
> only be done after slattach has turned the port into something that
> can speak IP.  This case is not handled by the current /etc/rc and
> /etc/sysconfig scheme (and i doubt somebody could come up with a true
> generic method to do it).
> 
> -- 
> cheers, J"org
> 

 
 I know this is ancient news, but I'm behind again.

 Anyway, I'd like to consider the following scenario:

	1) slattach
	2) ifconfig
	3) modem goes down
	4) restart slattach to reconnect

 does that mean I have to re-ifconfig the sl0 device after slattach
restabilishes the line?  I don't think so...

 Thus, there is a state in which no slattach is running, and the
ifconfig on sl0 is valid.

 What that says to me is that you can, in fact, ifconfig sl0 before
doing a slattach.  I've been doing it for a few years now with great
success.

 This way, I can ifconfig the sl0 device in /etc/rc, assigning its
IP address there - and the network isn't available until someone
does the  slattach.  This is really handy..

 In fact, I've changed my /etc/rc to do exactly what I implied
in the original note:

> > network_interfaces="sl0 lo0"
> > ifconfig_slo="inet ..."

 it appears to be working just fine (as it always has.)

[although, there is some route weirdness that got introduced in 2.1]

	- Dave Rivers -