From owner-freebsd-questions Sun Feb 18 8:10:35 2001 Delivered-To: freebsd-questions@freebsd.org Received: from speedbuggy.telerama.com (speedbuggy.telerama.com [205.201.1.216]) by hub.freebsd.org (Postfix) with SMTP id 1456F37B69C for ; Sun, 18 Feb 2001 08:10:32 -0800 (PST) Received: (qmail 13943 invoked from network); 18 Feb 2001 16:10:30 -0000 Received: from d7-17.dyn.telerama.com (HELO bigdaddy.localdomain) (205.201.40.17) by speedbuggy.telerama.com with SMTP; 18 Feb 2001 16:10:30 -0000 Received: from localhost (cwaiken@localhost) by bigdaddy.localdomain (8.11.1/8.11.1) with ESMTP id f1IGCxc00224 for ; Sun, 18 Feb 2001 11:13:01 -0500 (EST) (envelope-from cwaiken@telerama.com) X-Authentication-Warning: bigdaddy.localdomain: cwaiken owned process doing -bs Date: Sun, 18 Feb 2001 11:12:59 -0500 (EST) From: "Christopher W. Aiken" X-X-Sender: To: FreeBSD Questions Subject: [cwa] kernel ppp question Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I seem to missing something basic with kernel ppp. I set up my /etc/ppp/options file: # options file for PPPD defaultroute crtscts modem deflate 12,12 user cwaiken lock I set up my /etc/ppp/chat script: # Abort the chat script is modem replies # BUSY or NO CARRIER ABORT BUSY ABORT 'NO CARRIER' # Wait up to 5 seconds for a reply to each of these TIMEOUT 5 '' ATZ OK ATM0 OK ATDTxxxxxxxxxx # Wait 40 seconds for connection TIMEOUT 40 CONNECT TIMEOUT 5 I set up /etc/ppp/pap-secrets. I then run: pppd /dev/cuaa1 115200 connect chat -f /etc/ppp/chat user cwaiken I do indeed get connected. When I'm finished I do a: kill -9 `cat /var/run/ppp0.pid` to finish my connection. The problem is the second, and subsequent times, that I run: pppd /dev/cuaa1 115200 connect chat -f /etc/ppp/chat user cwaiken I get this error: pppd[520]: Couldn't add default route: File exists I also get that same error if I try using user ppp. and I can't do anything. I can't ping any sites, fetchmail doesn't run, etc. The only way I could figure out how to get this going again was to re-boot my system. What am I doing wrong? What am I missing? -- Christopher W. Aiken, Scenery Hill, Pa, USA chris at cwaiken dot com, www.cwaiken.com Debian GNU/Linux 2.2_r2 & FreeBSD 4.2 RELEASE To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message