Return to BSD News archive
Path: euryale.cc.adfa.oz.au!newshost.carno.net.au!harbinger.cc.monash.edu.au!news.mel.connect.com.au!munnari.OZ.AU!news.Hawaii.Edu!news.uoregon.edu!cibnor!cortes!lmiller From: lmiller@cortes.cibnor.mx (Larry Miller [DT]) Newsgroups: comp.unix.bsd.freebsd.misc Subject: Re: ijppp crashing serial connection Date: 10 Dec 1996 15:58:57 GMT Organization: Centro de Investigaciones Biologicas Lines: 21 Message-ID: <58k1c1$qct@bermejo.cibnor.mx> References: <2153454606@f401.n711.z3.ftn> <587o2e$k83@bermejo.cibnor.mx> <58ir0c$a5p@anorak.coverform.lan> NNTP-Posting-Host: cet-1.cibnor.conacyt.mx X-Newsreader: TIN [version 1.2 PL2] Xref: euryale.cc.adfa.oz.au comp.unix.bsd.freebsd.misc:32544 Brian Somers (brian@anorak.coverform.lan) wrote: : : Actually, it was parity disagreement (problem solved this morning), but I : : *would* have liked my modem to tell me it was going on; how does one : : elicit that info? : I guess you've got a direct connection - no login? If you have wrong : parity, you shouldn't be able to login... you should just get garbage, : same as if you're talking with the wrong number of data or stop bits. No, we're dialup with login. It's unclear to me what actually happened; the guys that configured it had ppp.conf configured at 28800 even 7, which I wouldn't have thought would even *work* (nonstandard speed). They also had an rc.serial at 38400 even 7. Dialup worked. Login worked. PPP communications worked-- sort of-- but they would crash on what looked like an outgoing buffer overrun with big transmissions. I'm stumped. :> Saludos-- Larry Miller Administrador de Redes / Network Administrator Centro de Investigaciones Biologicas del Noroeste, La Paz, BCS Mexico