*BSD News Article 74737


Return to BSD News archive

Path: euryale.cc.adfa.oz.au!newshost.anu.edu.au!harbinger.cc.monash.edu.au!munnari.OZ.AU!news.hawaii.edu!news.uoregon.edu!hunter.premier.net!news.cais.net!news.mathworks.com!tank.news.pipex.net!pipex!oleane!jussieu.fr!rain.fr!francenet.fr!itesec!not-for-mail
From: archer@hsc.fr (Vincent Archer)
Newsgroups: comp.mail.uucp,comp.unix.bsd.freebsd.misc
Subject: Strange Taylor UUCP problem on Freebsd 2.1.0
Date: 26 Jul 1996 11:57:47 +0200
Organization: Usenet Canal Historique
Lines: 27
Message-ID: <4ta4qr$80f@itesec.hsc.fr>
NNTP-Posting-Host: itesec.hsc.fr
Mime-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 8bit
Xref: euryale.cc.adfa.oz.au comp.mail.uucp:16598 comp.unix.bsd.freebsd.misc:24439

Got a strange problem using Taylor UUCP 1.06 (coming straight out of the
FreeBSD 2.1 cdrom). I'm supposed to call from a Solaris 2.4 (HDB UUCP),
so I'm stuck to protocol "g". The BSD machine reported all kind of checksum
errors, ending the transfer after 10mn (for a single remote command!).

I tried to recompile UUCP 1.06.1, and ended having two BSD machines, using
both the same uucico binary, and still gets the checksum errors on each
"g" protocol packet.

The link between the two machines is clear. It's a null modem of 3 meters.
I dropped the speed to 9600 to be sure that my 16550 would have zero pbms.
When I log in manually using cu, I have 0 problem. No characters lost,
no garbage, even at full blast (cat of large text files). So, the line is
clear.

So, in short:
	The line is OK
	The ports are OK (and cs8 while talking, I've checked)
	The binaries are the same
	yet, the 'g' protocol fails
		(same checksum errors reported from the Solaris machine)
(and yes, I've checked 'i'. Doesn't work either)

Any idea of what could go wrong? Pointer for future investigation?
-- 
Vincent ARCHER  -=-=-  Herve Schauer Consultants -=-=-   archer@hsc.fr
Tel: +33 1 46388990                                Fax: +33 1 46380505