From owner-freebsd-bugs  Sun Jul  2 13:04:19 1995
Return-Path: bugs-owner
Received: (from majordom@localhost)
          by freefall.cdrom.com (8.6.10/8.6.6) id NAA08868
          for bugs-outgoing; Sun, 2 Jul 1995 13:04:19 -0700
Received: from Root.COM (implode.Root.COM [198.145.90.1])
          by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id NAA08862
          for <freebsd-bugs@freefall.cdrom.com>; Sun, 2 Jul 1995 13:04:17 -0700
Received: from corbin.Root.COM (corbin [198.145.90.18]) by Root.COM (8.6.11/8.6.5) with ESMTP id NAA03662; Sun, 2 Jul 1995 13:04:08 -0700
Received: from localhost (localhost [127.0.0.1]) by corbin.Root.COM (8.6.11/8.6.5) with SMTP id NAA05768; Sun, 2 Jul 1995 13:04:41 -0700
Message-Id: <199507022004.NAA05768@corbin.Root.COM>
To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch)
cc: freebsd-bugs@freefall.cdrom.com
Subject: Re: kern/577: SLIP requires `ifconfig up' now 
In-reply-to: Your message of "Sun, 02 Jul 95 18:35:23 +0200."
             <199507021635.SAA00308@uriah.heep.sax.de> 
From: David Greenman <davidg@Root.COM>
Reply-To: davidg@Root.COM
Date: Sun, 02 Jul 1995 13:04:41 -0700
Sender: bugs-owner@FreeBSD.org
Precedence: bulk

>The line ``ifconfig sl$6 ...'' was supposed to set the interface
>address and mark the interface automatically `up' (as it's also the
>case for other interfaces e.g. ethernet).  After your modification, it
>didn't work anymore.  Sticking another ``ifconfig sl$6 up'' in the
>next line worked around this, but i thought it's not a good idea to
>break with the previous behaviour.

   Actually, you probably do want the "ifconfig up", as this has the effect
of immediately propagating the new routing information to down-stream hosts
(assuming there are any).

>Apparently, the interface isn't marked automatically `up' by slattach.

   Actually, the process of converting the interface to a SLIP device should
set it up. I really don't like the 'up' flag not tracking the state of the
interface. Perhaps if it was set 'up' only if the interface was a SLIP device,
would this be okay?

>It works now as one would expect: it's up right after the first
>ifconfig, and i can put it down or up later if i want.

   Ethernet is special - it's not okay to extrapolate this about other network
devices.

-DG