From owner-freebsd-hackers  Wed Dec 25 23:13:54 1996
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.4/8.8.4) id XAA11321
          for hackers-outgoing; Wed, 25 Dec 1996 23:13:54 -0800 (PST)
Received: from hamby1.lightside.net (hamby1.lightside.net [207.67.176.17])
          by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id XAA11316
          for <hackers@freebsd.org>; Wed, 25 Dec 1996 23:13:50 -0800 (PST)
Received: from localhost (jehamby@localhost) by hamby1.lightside.net (8.8.3/8.8.2) with SMTP id XAA00210 for <hackers@freebsd.org>; Wed, 25 Dec 1996 23:13:47 -0800 (PST)
X-Authentication-Warning: hamby1.lightside.net: jehamby owned process doing -bs
Date: Wed, 25 Dec 1996 23:13:46 -0800 (PST)
From: Jake Hamby <jehamby@lightside.com>
X-Sender: jehamby@hamby1
To: hackers@freebsd.org
Subject: URGENT:  2.2-BETA fails for PPP to COM3!
Message-ID: <Pine.BSF.3.95.961225231336.208A-100000@hamby1>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-hackers@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

Danger Will Robinson!  It appears that changes to sysinstall since the
last time I've actively used it (2.1.5) are preventing a PPP install from
working on other serial ports than COM1.  Here are the issues as I
understand them;  I'm sorry I don't have a patch:

I have three serial ports, COM1 and COM2, plus COM3 at port 0x3f8 IRQ 9. 
The modem (an internal Zoom 28.8) is on COM3.  All three serial ports are
correctly probed and recorded by the kernel and sysinstall (I had to
manually enable COM3 of course). 

The last version of sysinstall I remember using for PPP (2.1.5) manually
asked which COM port to use in a separate dialog box.  The latest version
shows all possible SLIP and PPP combinations in a single dialog box.  No
matter what you choose, however, user-mode PPP always tries /dev/cuaa0.  I
believe this is caused by a line in the ppp.conf file:

 set device cuaa0

that would be generated from the devp->devname variable in network.c.  I
believe that somehow the COM1 device struct is being stored for the ppp0
device, and not the serial port that the user chose.  I hope this is
enough information for you to figure out the problem before 2.2-RELEASE,
because I would consider this a quite serious flaw!  I was happy with the
old way that sysinstall worked, a separate dialog box asking for COM port,
and I'm curious why this was changed?

P.S.  A user mailed me personally about this problem (but with 2.1.6 I
believe) and I forwarded him to questions.  He eventually was able to
install, by changing his modem to COM1 (ick!).

-- Jake