From owner-freebsd-questions Sat Dec 13 20:11:29 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id UAA06106 for questions-outgoing; Sat, 13 Dec 1997 20:11:29 -0800 (PST) (envelope-from owner-freebsd-questions) Received: from awfulhak.demon.co.uk (awfulhak.demon.co.uk [158.152.17.1]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id UAA06101 for ; Sat, 13 Dec 1997 20:11:24 -0800 (PST) (envelope-from brian@awfulhak.org) Received: from gate.lan.awfulhak.org (localhost [127.0.0.1]) by awfulhak.demon.co.uk (8.8.7/8.8.7) with ESMTP id EAA23167; Sun, 14 Dec 1997 04:09:51 GMT (envelope-from brian@gate.lan.awfulhak.org) Message-Id: <199712140409.EAA23167@awfulhak.demon.co.uk> X-Mailer: exmh version 2.0zeta 7/24/97 To: "Joe \"Marcus\" Clarke" cc: freebsd-questions@freebsd.org Subject: Re: User ppp version 1.6 In-reply-to: Your message of "Sat, 13 Dec 1997 20:38:22 EST." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 14 Dec 1997 04:09:50 +0000 From: Brian Somers Sender: owner-freebsd-questions@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > I just installed user ppp 1.6 (from 12/12/97), and it now gives me a > strange warning each time it connects. It reports that it cannot delete a > route because no such process exists. Below are portions of my ppp.conf > and ppp.linkup files. The command I use to start ppp is `ppp -auto -alias > demand`. All IP addresses (local and remote) are static. Thanks. I'm > using ppp version 1.6 compiled on FreeBSD 2.2.2-RELEASE. > > Joe Clarke > > # ppp.conf file > demand: > . > . > . > . > set ifaddr 206.228.135.32 206.228.135.1 255.255.255.0 > delete ALL > add 0 0 HISADDR > ################################################################ > # end of /etc/ppp/ppp.conf > > > # ppp.linkup file > demand: > # remove any IP routing information that the PPP program has created > delete ALL > # add a default route the remote end's actual address > add 0 0 HISADDR > > # End of /etc/ppp/ppp.linkup Hmm. I've changed the warning so that it's logged using LogWARN (always output in some way) rather than LogTCPIP. It looks like the deletion is failing for temporary routes only ! It's nothing to worry about for the moment. I'll fix it ASAP (I've gotta go to bed now!) and follow up this mail. Cheers. -- Brian , , Don't _EVER_ lose your sense of humour....