Return to BSD News archive
Path: sserve!newshost.anu.edu.au!munnari.oz.au!news.Hawaii.Edu!ames!haven.umd.edu!darwin.sura.net!news-feed-2.peachnet.edu!concert!rutgers!utcsri!newsflash.concordia.ca!sifon!clouso.crim.ca!sobeco!zap!fortin From: fortin@zap.uniforum.qc.ca (Denis Fortin) Newsgroups: comp.os.386bsd.bugs Subject: Re: dial in (0.2.4) Message-ID: <CA7FKC.MIo@zap.uniforum.qc.ca> Date: 15 Jul 93 11:50:21 GMT References: <21p7es$jf6@urmel.informatik.rwth-aachen.de> Organization: zap, Montreal, QC, Canada Lines: 34 In article <21p7es$jf6@urmel.informatik.rwth-aachen.de> kuku@acds.physik.rwth-aachen.de writes: >Recently I switched all my 386bsd systems to 0.2.3/0.2.4 patchkit versions >hoping that I got rid of all troubles I had solved up to then by individually > >My dial in site no longer works. That site previously had a com cgd driver >from mid summer 92 and it always worked fine. > >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 sort of modem configuration are you using? Have you changed the speed of the getty? (I changed the speed of the getty on my machine to 38400 bps and I almost forgot to set the saved "interface speed" in my modem to that speed (otherwise, dialouts work fine at 38400 bps, but logins always appear as gibberish since the modem is attempting to log in at 19200).) The problem I'm having these days is that sometimes when uucico dials out and can't get a connection, I do a "ps -wax" and I notice that there is a "login" process running for user "login:", which seems to indicate that the BIDIR stuff might have a small flaw somewhere. (i.e. the uucico fails and goes away, but the DTR isn't dropped right away or the buffer isn't flushed or something so that the getty gets woken up and receives the login: prompt from the remote system and then attempts to negociate a login with it (so both systems end up with users called "login:" trying to log on with a password "Password:" :-(. Has anybody else seen this? -- Denis, fortin@zap.uniforum.qc.ca "