Ascend Archive
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
(ASCEND) Problems using an 1800's K56 modems with uucp
I have configured our uucp system (Taylor uucp v 1.06.1) to use the
k56 modems in our 1800.
cu works great.
uucp does not. I see every checksum packet fail.
If I were to guess, I would say I don't have an 8 bit clean data path
through these modems. Either that or the modem - modem handshaking is
not working. The remote modems are all Telebit Worldblazer.
This same uucp has been working great for the last few years through a
livingston pm2e with Telebit Worldblazers on both ends.
I have tried two methods of connecting to the modems.
The first (very ugly) way is to use uucp's 'dialer-sequence' feature
to have uucp telnet to the 1800's port 5000.
The second much prettier method is to use Ross Cartlidge's
(rossc@extro.ucc.su.oz) nd/tcpcon package to tie /dev/pty devices to
a tcp host&port. This is similiar to Livingston's in.pmd mechanism,
though, not quite a slick.
The dial strings I use assume the defaults for the K56 are okay. In
otherwords, I do not modify the operating parameters at all.
The initial uucp setup, login, command exchange sequence seems to work
okay. The file transfer starts, then I get a bunch of bad checksums
and the connection is eventually dropped. This is an example of the
failure...
DEBUG: fiwait_for_packet: Need 74 bytes
DEBUG: fconn_read: Read 157 "\000\210\324\"\343\300\003\000 30\200\220\000\001\002\200\000\004\001\000\000\000@\000\000 00@\000\"h\234#\240 @\000\177\376\001\000\000\000@\000\177\
DEBUG: fiprocess_data: Bad checksum; data 2447691496, frame 4287751374
DEBUG: finak: Sending NAK 3
DEBUG: fconn_io: Writing 6 "\007\030\020p\000x"
DEBUG: fconn_io: Wrote 6 of 6, read 0 of 15813
++ Ascend Users Mailing List ++
To unsubscribe: send unsubscribe to ascend-users-request@bungi.com
To get FAQ'd: <http://www.nealis.net/ascend/faq>
Follow-Ups: