From owner-freebsd-questions Wed Mar 19 13:44:27 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id NAA14888 for questions-outgoing; Wed, 19 Mar 1997 13:44:27 -0800 (PST) Received: from xmission.xmission.com (softweyr@xmission.xmission.com [198.60.22.2]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id NAA14878 for ; Wed, 19 Mar 1997 13:44:23 -0800 (PST) Received: (from softweyr@localhost) by xmission.xmission.com (8.8.5/8.7.5) id OAA08645; Wed, 19 Mar 1997 14:43:44 -0700 (MST) From: Softweyr LLC Message-Id: <199703192143.OAA08645@xmission.xmission.com> Subject: Re: ppp strangeness To: dlowe@sirius.com Date: Wed, 19 Mar 1997 14:43:43 -0700 (MST) Cc: questions@freebsd.org In-Reply-To: from "David Lowe" at Mar 18, 97 00:07:50 am X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-questions@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Davide Lowe recently lamented: > I'm running FreeBSD 2.2-970310-GAMMA on a 486-80 with 12MB ram. The modem > in question is a USRobotics 28.8 Sportster. > > I used to run user ppp without problems. Things that have changed since > then: upgraded from 14.4 Sportster. upgraded from 2.1.5-RELEASE. and > changed to an ISP with dynamic IP allocation :( > > The problems are as follows: > > 1 - The connection dies after some seemingly random interval. However, > the line doesn't get hung up, the routes stay in place, and the > interface stays marked as up. The ppp process starts going crazy > and slurps up memory; doesn't respond to keys. At this point I kill > -9 it from another shell, down the interface, delete the dead route, > and re-do (all manually, so far). Not much fun. This is most likely a modem problem; you need to tell your modem to hangup when carrier detect goes away. Also, be sure to use a cuax device to connect on in your configuration file. > 2 - A problem that seems more strange. 'ppp -auto foo' seems to behave > strangely. It claims to be working fine, but it ups the interface > with a bogus route immediately (i.e.: > # ifconfig tun0 > tun0: flags=8050 mtu 1006 > # ppp -auto foo > > # ifconfig tun0 > tun0: flags=8051 mtu 1006 > inet 10.255.255.254 --> 10.255.255.255 netmask 0xffffff00 When you run ppp -auto, it brings up the tun0 interface immediately so you can route packets to it. If it gets a packet and doesn't have the interface up, it will bring it up and fix the addresses and/or routes. If the interface wasn't up, you couldn't route packets to it! -- "Where am I, and what am I doing in this handbasket?" Wes Peters Softweyr LLC http://www.xmission.com/~softweyr softweyr@xmission.com