Return to BSD News archive
Newsgroups: comp.os.386bsd.bugs Path: sserve!newshost.anu.edu.au!harbinger.cc.monash.edu.au!bunyip.cc.uq.oz.au!munnari.oz.au!news.hawaii.edu!ames!hookup!swrinde!sgiblab!rahul.net!a2i!raw!iverson From: iverson@lionheart.com (Tim Iverson) Subject: Re: [FreeBSD 2.0] UUCP problem with dialin? References: <D4ArtG.K1z@lionheart.com> <3ik8l7$ba7@bonnie.tcd-dresden.de> Organization: Lionheart Software Date: Mon, 27 Feb 1995 10:43:29 GMT Message-ID: <D4nn4I.3B@lionheart.com> Lines: 29 In article <3ik8l7$ba7@bonnie.tcd-dresden.de>, J Wunsch <joerg_wunsch@uriah.heep.sax.de> wrote: >>UUCP dials out and transfers just fine in either (or both) directions, but >>it has a real hard time with dial-ins ... > >Make sure that flow control is working properly. If necessary, use >the lock state and initial state devices in combination with >/etc/rc.serial to preset your port to ``crtscts'' (Xref sio(4)). FreeBSD 2.0 sio.c does not support RTS unless you apply my patches. Yes, I've applied them. >Try to log into the system manually, and look with stty if the >terminal settings are ok. Terminal settings are fine, authentication is fine (login, passwd, Shere=, protocol selection, etc.). Packets sent in either direction result in immediate NAKs. However, if FreeBSD does the dialing, all works fine. I was planning on looking at this in more detail this weekend, including fixing some minor bugs I added to sio.c while adding RTS support, but I seem to have run out of time. Hopefully it's just something stupid I've done and not an involved initial condition problem. I'll post details if they're not too embarrassing ... ;-) - Tim Iverson iverson@lionheart.com