From owner-freebsd-questions Thu Mar 20 06:33:34 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id GAA16571 for questions-outgoing; Thu, 20 Mar 1997 06:33:34 -0800 (PST) Received: from cs.iastate.edu (cs.iastate.edu [129.186.3.1]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id GAA16566 for ; Thu, 20 Mar 1997 06:33:32 -0800 (PST) Received: from sunfire.cs.iastate.edu (sunfire.cs.iastate.edu [129.186.3.46]) by cs.iastate.edu (8.7.4/8.7.1) with ESMTP id IAA17447 for ; Thu, 20 Mar 1997 08:33:23 -0600 (CST) Received: from localhost (ghelmer@localhost) by sunfire.cs.iastate.edu (8.7.4/8.7.1) with SMTP id IAA05529 for ; Thu, 20 Mar 1997 08:32:42 -0600 (CST) X-Authentication-Warning: sunfire.cs.iastate.edu: ghelmer owned process doing -bs Date: Thu, 20 Mar 1997 08:32:41 -0600 (CST) From: Guy Helmer To: freebsd-questions@freebsd.org Subject: "ppp -background" broke in 2.2-RELEASE? Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-questions@freebsd.org X-Loop: FreeBSD.org Precedence: bulk For the past couple of months I've been using "ppp -background -alias isu-cs" to start up my PPP link from one of my home FreeBSD systems to the university (under FreeBSD 2.2-BETA and 2.2-GAMMA-970310); however, since I did my "make world" to install 2.2-RELEASE on that system, ppp with the above options doesn't connect properly. I have a dial chat script and a login chat script specified in the config file, and by logging to the ppp.log file, I see that ppp successfully dials, logs in, and executes the command to start ppp on the remote system. However, after it does that, it seems to run the dial chat script again (it sends the modem initialization string and waits for "OK"!). Meanwhile, the remote is sending ppp handshake information... Using "ppp -alias isu-cs" works, but I have to enter the system's ppp password and manually give the "dial" command. From CVS it looks like there were last-minute changes to ppp before 2.2-RELEASE that might have broken -background -- has anyone else noticed this and written a patch? Thanks for any advice, Guy Helmer Guy Helmer, Computer Science Grad Student, Iowa State - ghelmer@cs.iastate.edu http://www.cs.iastate.edu/~ghelmer