From owner-freebsd-isp  Wed May  7 11:13:15 1997
Return-Path: <owner-isp>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.5/8.8.5) id LAA05792
          for isp-outgoing; Wed, 7 May 1997 11:13:15 -0700 (PDT)
Received: from time.cdrom.com (root@time.cdrom.com [204.216.27.226])
          by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id LAA05787;
          Wed, 7 May 1997 11:13:13 -0700 (PDT)
Received: from time.cdrom.com (jkh@localhost [127.0.0.1]) by time.cdrom.com (8.8.5/8.6.9) with ESMTP id LAA09987; Wed, 7 May 1997 11:13:09 -0700 (PDT)
To: Stephen Roome <steve@visint.co.uk>
cc: freebsd-current@FreeBSD.ORG, freebsd-isp@FreeBSD.ORG
Subject: Re: tun0 problem in 3.0-970209-SNAP 
In-reply-to: Your message of "Wed, 07 May 1997 15:07:06 BST."
             <Pine.BSF.3.91.970507144915.6423H-100000@bagpuss.visint.co.uk> 
Date: Wed, 07 May 1997 11:13:09 -0700
Message-ID: <9983.863028789@time.cdrom.com>
From: "Jordan K. Hubbard" <jkh@time.cdrom.com>
Sender: owner-isp@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

> Anyway, it's fairly simple:
> 
> here's a snip from ifconfig
> tun0: flags=8051<UP,POINTOPOINT,RUNNING,MULTICAST> mtu 1524
>         inet 194.222.196.174 --> 158.152.1.222 netmask 0xffffff00 

Don't do that.  ppp should be managing the tun0 device *exclusively*
and you shouldn't be ifconfig'ing it at all.

> So, I type ifconfig tun0 down, and I can _STILL_ ping the other end of
> the line ? really that doesn't make a lot of sense to me.

Because you're not supposed to be frobbing tun0 at all, that's why. :)
Control its state entirely through ppp, please.

					Jordan