From owner-freebsd-current  Fri Dec 19 10:12:40 1997
Return-Path: <owner-freebsd-current>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.7/8.8.7) id KAA04770
          for current-outgoing; Fri, 19 Dec 1997 10:12:40 -0800 (PST)
          (envelope-from owner-freebsd-current)
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 KAA04746
          for <freebsd-current@freebsd.org>; Fri, 19 Dec 1997 10:12:30 -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 OAA25865;
	Fri, 19 Dec 1997 14:20:55 GMT
	(envelope-from brian@gate.lan.awfulhak.org)
Message-Id: <199712191420.OAA25865@awfulhak.demon.co.uk>
X-Mailer: exmh version 2.0zeta 7/24/97
To: Ron Bolin <rbolin@netchannel.net>
cc: FreeBSD Current Mailing List <freebsd-current@freebsd.org>
Subject: Re: PPP Broken? 
In-reply-to: Your message of "Fri, 19 Dec 1997 07:40:13 EST."
             <349A6B2D.516E0ABA@netchannel.net> 
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Fri, 19 Dec 1997 14:20:55 +0000
From: Brian Somers <brian@awfulhak.org>
Sender: owner-freebsd-current@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

> With the 12-17-97 current, PPP seems broken. I can no longer DHCP to my
> IAP.
> Did something change in the setup that I need to know about.  What is
> the "File exists"
> error shown below?
> 
> Thanks
> 
> Ron
> 
> 
> Dec 19 02:44:01 rlb ppp[187]: Phase: NewPhase: Dead
> Dec 19 07:00:00 rlb ppp[187]: Phase: Connected!
> Dec 19 07:00:00 rlb ppp[187]: Phase: Phone: 4046541350
> Dec 19 07:00:22 rlb ppp[187]: Phase: NewPhase: Authenticate
> Dec 19 07:00:22 rlb ppp[187]: Phase: NewPhase: Network
> Dec 19 07:00:23 rlb ppp[187]: Link:  myaddr = 207.69.129.204  hisaddr =
> 168.121.
> 1.1
> Dec 19 07:00:23 rlb ppp[187]: Link: OsLinkup: 168.121.1.1
> Dec 19 07:00:23 rlb ppp[187]: Warning: Add route failed: 0.0.0.0: errno:
> File ex
> ists

I think the only relevent change is that this error now gets logged as 
LogWARN rather than LogTCPIP.  Try enabling ``command'' logging and 
seeing what's actually occuring.

Cheers.

> 
> --
> -------------------------------------------------------------------------------
> Ron Bolin, Sr. Software Eng, NetChannel     Web: http://www.netchannel.net
> E-mail: rbolin@netchannel.net               Web: http://www.gsu.edu/~gs01rlb
> Ph: 770-729-2929 Ext 249 Hm: 770-992-6875   Web: http://www.mindspring.com/~rlb

-- 
Brian <brian@Awfulhak.org>, <brian@FreeBSD.org>, <brian@OpenBSD.org>
      <http://www.Awfulhak.org>
Don't _EVER_ lose your sense of humour....