kak@hico2.UUCP (Kris A. Kugel) (09/05/90)
I've just installed the HDB uucp (STORE release).
Problem is, my uucp babbles to itself before it
gets out a successful call. The first try always
fails as the modem mumbles "AT^M^M^MOK^M^M^M^MAT^M^M^MOK"
to itself. I know I sound like that late at night, but
that's no excuse. Anyhow, the first call dials,
then the relays on the telebit start riccoshaying, and
it hangs up just as it's getting a connection.
The second attempt always seems to connect with no trouble.
cu to external locations exibits similar behavior; cu to
the modem device ( cu -l tty000 ) connects, then hangs
up immediately.
/etc/inittab:
000:2:respawn:/usr/lib/uucp/uugetty -r -t60 tty000 T19200
/etc/gettydefs: (was originally a single long line)
T19200# B19200 CLOCAL BRKINT IGNPAR ISTRIP ECHO OPOST ONLCR # HUPCL
BRKINT ISTRIP ICRNL OPOST ONLCR B19200 CS8 CREAD ISIG ICANON ECHO ECHOE
ECHOK TAB3 #login: #T19200
uucp completely broke when I removed the CLOCAL, as somebody suggested.
/usr/lib/uucp/Devices:
ACUTB tty000,M - 19200 tbfast \D
ACU tty000,M - 19200 tbslow \D
hico3 tty001 - 19200 direct
STARLAN starlan - Any STARLAN
/usr/lib/uucp/Dialers:
tbfast =W "" A\pA\pA "" \M\dAT\r OK ATS50=255 OK ATDT\T CONNECT-\c-CONNECT \m\c
tbslow =W "" A\pA\pA "" \M\dAT\r OK ATS50=0 OK ATDT\T CONNECT-\c-CONNECT \m\c
Note that the telebit port is locked at 19200, the beginning A's are for
sentimental value only. Maybe that's the problem?
Anyhow, this has me stumped for the moment. Any ideas? I can always
try to install one of the packaged suggestions later, but I'm curious
about why I can't get this setup to work.
Kris A. Kugel
(201) 842-2707
{uunet,att,rutgers}!westmark!hico2!kak <--well-connected
{tsdiag,ka2qhd}!hico2!kak <--frequent
{ssbn,zorch,zinn,ditka,daver,attdso}!hico2!kak <--every two days
Actually, all my uucp connections
are going to be just a little irregular
for a while.michael@yonder.UUCP (Michael E. Haws) (09/07/90)
In article <270@hico2.UUCP>, kak@hico2.UUCP (Kris A. Kugel) writes: > I've just installed the HDB uucp (STORE release). > Problem is, my uucp babbles to itself before it > gets out a successful call. The first try always > fails as the modem mumbles "AT^M^M^MOK^M^M^M^MAT^M^M^MOK" > to itself. I know I sound like that late at night, but > that's no excuse. Anyhow, the first call dials, > then the relays on the telebit start riccoshaying, and > it hangs up just as it's getting a connection. > > The second attempt always seems to connect with no trouble. > I had/have a similar problem on my machine. My theory is that uugetty is not getting out of the way fast enough and is echoing characters back out the port and this screws up the initial dial or login attempt to the site being called. By the time the second dial comes around uugetty has given up and the dial and login are successful. What I ended up doing, and what appears to have cleaned up __MY__ uucp/cu problems was to remove the ECHO from the first set of flags in the gettydef entry. I recently posted this to the net and asked if anyone knew for sure whether or not ECHO should or should not be in the first set of flags, but alas there was no response. In any case it seemed to clean up my connections and I hope this helps in your case. -- Michael E. Haws "Keep the blue side up" w - (303) 986-2370 boulder!yonder!michael h - (303) 232-0628
wilkes@mips.COM (John Wilkes) (09/08/90)
In article <418@yonder.UUCP> michael@yonder.UUCP (Michael E. Haws) writes: >In article <270@hico2.UUCP>, kak@hico2.UUCP (Kris A. Kugel) writes: >> >> Problem is, my uucp babbles to itself before it >> gets out a successful call. The first try always >> fails as the modem mumbles "AT^M^M^MOK^M^M^M^MAT^M^M^MOK" >> to itself. > >gettydef entry. I recently posted this to the net and asked if >anyone knew for sure whether or not ECHO should or should not be >in the first set of flags, but alas there was no response. i am not qualified to answer for sure if ECHO should or should or should not be in the first set of flags. what i do know is that the gettydefs file on my system does, in fact, have ECHO in the first set of flags. i am running a telebit trailblazer plus, and i am not using hardware flow control. i do not lock the interface speed. i use the HDB uucp package that i originally got from the STORE! (when it was alive.) i am currently running version 3.51m of the operating system, and previously ran version 3.51 with no problems. this setup has worked reliably for over two years or so, with a fair amount of dial-out activity using the cu program, a moderate amount of uucp traffic, and until just recently virtually no dial-ins. since having a second line (a data line) installed about two months ago, i've had some dialins, and still no problems. every couple of days, the telebit leaves for iraq and must be slapped upside the head (read power-cycled) to get it to behave. this is, however, a problem with the early telebits, not the unix-pc. we used to have the same problem with the telebits in the computer center at mips (on computers we manufacture) before we upgraded to the newer model modem. from my /etc/gettydefs: H19200# EXTA BRKINT IGNPAR ISTRIP ECHO OPOST ONLCR # HUPCL BRKINT ISTRIP ICRNL O POST ONLCR EXTA CS8 CREAD ISIG ICANON ECHO ECHOE ECHOK TAB3 #\nlogin: #H2400 from my /etc/inittab: 000:2:respawn:/usr/lib/uucp/uugetty -r -t60 tty000 H19200 i have a collection of files for setting up a trailblazer, from which i obtained the gettydefs entry, and i'll cheerfully make them available to anyone who wants 'em. if the interest is high, i can make it available via anon uucp. better yet, maybe something like this belongs in the osu-cis archives. (robert j. granvin, you listening? maybe you should send this stuff off to lenny so he can put it in the archives?) "works for me; your mileage may (and probably will) vary." john wilkes <wilkes@mips.com>
vern@zebra.UUCP (Vernon C. Hoxie) (09/08/90)
In article <270@hico2.UUCP> kak@hico2.UUCP (Kris A. Kugel) writes: >I've just installed the HDB uucp (STORE release). >Problem is, my uucp babbles to itself before it >gets out a successful call. As Michael Haws suggested, you might try removing the ECHO from the 'gettydefs'. Also, I think that HDB does not understand B19200 but needs EXTA to run at 19200 baud. Check the response from '/usr/lib/uucp/uugetty -c /etc/gettydefs' against the entries in termio(7). I run my T19200 with T2400 as the next speed. This allows the modem/computer to autobaud down when incoming calls are at slower speeds. Another entry in you 'gettydefs' which I question is the ISTRIP. My thinking is that if this truly works, you would not be able to receive compressed, eight bit files. I leave it out of my 'gettydefs'. >/etc/gettydefs: (was originally a single long line) >T19200# B19200 CLOCAL BRKINT IGNPAR ISTRIP ECHO OPOST ONLCR # HUPCL >BRKINT ISTRIP ICRNL OPOST ONLCR B19200 CS8 CREAD ISIG ICANON ECHO ECHOE >ECHOK TAB3 #login: #T19200 I haven't got the ,M\M\m stuff to work here. Everything seems to operate okay without them but with CLOCAL set in the second filed of the 'gettydefs'. >/usr/lib/uucp/Devices: >ACUTB tty000,M - 19200 tbfast \D >ACU tty000,M - 19200 tbslow \D >hico3 tty001 - 19200 direct >STARLAN starlan - Any STARLAN > >/usr/lib/uucp/Dialers: >tbfast =W "" A\pA\pA "" \M\dAT\r OK ATS50=255 OK ATDT\T CONNECT-\c-CONNECT \m\c >tbslow =W "" A\pA\pA "" \M\dAT\r OK ATS50=0 OK ATDT\T CONNECT-\c-CONNECT \m\c > >Note that the telebit port is locked at 19200, the beginning A's are for >sentimental value only. Maybe that's the problem? These are signals from the computer to the modem which allow the modem to autobaud to the speed the computer is sending. With T19200 set in 'inittab' and S51=254 in the modem, both machine will sleep at 19200. If a call comes in, the modem will autobaud to match the speed of the incoming call then send breaks to the computer until it gets responses at the correct speed. For outgoing calls, your T2400 or whatever, will set the computer to 2400 baud. The "A\pA\pA\pAT" sequence is to allow the modem to match the computer speed. In several recent responses, I have suggested that users get the tstmdm.cpio.Z routine from osu-cis. This has been there for a year or so and I have yet to hear if anyone considers it worthwhile or not. Included in the package are suggestion from a number of users which should be of benefit when setting up TrailBlazers. It will need updating for T2500's and for other brand of modems but I need your input as to what should be included. If there is no one using this, I will ask Lenny to remove it and free up the disk space at osu. vern -- Vernon C. Hoxie {ncar,nbires,boulder,isis}!scicom!zebra!vern 3975 W. 29th Ave. voice: 303-477-1780 Denver, Colo., 80212 TB+ uucp: 303-455-2670