Return to BSD News archive
Path: sserve!newshost.anu.edu.au!munnari.oz.au!metro!sequoia!ultima!kralizec.zeta.org.au!kralizec.zeta.org.au!not-for-mail From: bde@kralizec.zeta.org.au (Bruce Evans) Newsgroups: comp.os.386bsd.bugs Subject: Re: dial in (0.2.4) Date: 15 Jul 1993 17:27:09 +1000 Organization: Kralizec Dialup Unix Sydney: +61-2-837-1183 V.32bis Lines: 25 Message-ID: <2230sdINNf80@kralizec.zeta.org.au> References: <21p7es$jf6@urmel.informatik.rwth-aachen.de> NNTP-Posting-Host: kralizec.zeta.org.au In <21p7es$jf6@urmel.informatik.rwth-aachen.de> kuku@acds.physik.rwth-aachen.de (Christoph Kukulies) writes: >Now, with 0.2.4, dialing in via modem no longer works. I see some looping >between the tty line and the modem and dialing in from outside results >in a non functioning connection build up. >What has happened to the sio/com driver under the patchkit? sio handles the carrier detect (CD) line correctly while com ignored it (pretended it was on). The change may cause problems. the first things to check are: 1. CD correctly wired on all serial cables. 2. clocal off for dialin lines. sio starts up with clocal on. This can lead to infinite echoes when getty starts up. getty turns clocal off but it has to open the port to turn it off, and the open does not clock waiting for carrier. Fix this by putting "stty -clocal </dev/sioNN" for all dialin ports in /etc/rc before getty starts. 3. clocal on for dialout lines (so that CD doesn't matter). If you use then bidirectional ports then 2) and 3) are inconsistent. I'm not sure how to fix this. -- Bruce Evans bde@kralizec.zeta.org.au