mack@kurz-ai.UUCP (Ed Mackenty) (06/27/90)
I'm posting this for a friend since he (obviously) cannot connect to the net himself: ==================== I am having problems with setting up a bi-directional uucp link. I am using a 68000 based machine running AT&T Sys 5.3 with some Berkeley stuff. I put a uugetty on my port with a modem set up in a standard way. This works fine for dialing in. When cu or uucp tries to dial out it cannot open the /dev file since the carrier detect is not on. If I force CD on with a modem switch then uucp works, but uugetty and the AT echos have a fun time talking to each other. (login: echos, trying to login as "login:") It seems that I can only have one or the other. Has anybody else seen this problem? Is there a fix or a work-around? Please respond to mack@kurz-ai.com since I cannot get mail yet. Neil Swartz <ATIsys1!nms@kurz-ai.com> Applied Telematics, Inc. ==================== Some more info: his machine is a Counterpoint, and I can't help him because I solved this problem by putting two modems on different ports and running getty on only one of them. We must be missing something obvious here, since I imagine that many systems use one modem for both dial-in and dial-out operation. Isn't that what uugetty is for? - MacK. -- _ __ _ _ ___ _____ _ _ ___ _ _ ___ _ ------------------ | |/ /| | || . \|__ /| | | || __|| || | | . | | | Edmund R. MacKenty | < | | || / / /_| |^| || _| | || |_ | | | | | mack@kurz-ai.com |_|\_\|___||_|\\/___||_/ \_||___||_||___| |_|_| |_| ------------------
heiby@mcdchg.chg.mcd.mot.com (Ron Heiby) (06/28/90)
Well, your friend certainly has a problem. You didn't mention what brand of modem is being used, but you mention AT, so it sounds like a Hayes of Hayes clone. You say "AT&T Sys 5.3", which is a version of UNIX for the AT&T 3B5 computer, so I assume that you mean System V Release 3. If your friend had Release 3.1 or later, you could use the feature of ignoring the modem control signals (or lack thereof) during the dialing sequence and stop ignoring them after you got the CONNECT message. That's probably not enough, though. What you want a modem to do is the following: A) Provide DCD signal except for a very brief time when a call is dropped. B) Provide friendly ASCII messages to tell you what's going on when the modem is placing an outgoing call. C) Provide *NO* friendly ASCII messages while accepting an incoming call. Point A allows you to talk to the modem to tell it to dial, even with older UUCP software. It also provides the drop of DCD to get a SIGHUP sent to the attached process. This is an important security consideration. Point B lets you dial out and know what's happening. It lets you construct a Dialer script. Point C prevents an incoming call from being announced to the uugetty with the string "RING". Many modems cheerfully say "RING" to the uugetty, causing the attached UNIX box to think that a user named "ring" is trying to log on from an uppercase-only terminal. You should be using the "-r" option to uugetty, which should help eliminate the modem/uugetty chatter. Another thing that may help is to configure the modem not to echo command input characters. I've used a lot of different kinds of modems on various UNIX systems. The closest to ideal true Hayes that I used was the 2400. However, to get it to work, I had to configure it with "Q1", send it a "Q0" in my dialing string, and configure it to reset from saved parameters (restoring the Q1) when the call drops. Unfortunately, doing the last caused the modem to ignore DTR and answer the phone even when the computer was turned off. Most of the modems that attempt to be Hayes "compatible" do much worse. The absolutely best modems I've used for UNIX systems are made by Telebit. I've successfully used the T1000, TrailBlazer Plus, and T2500. Great stuff! UUNET Communications Services seems to have the best prices around. Good luck! -- Ron Heiby, heiby@chg.mcd.mot.com Moderator: comp.newprod "Mandatory Drug Testing? Just Say NO!!!"
gsn@sclcig.uucp (Georg Nikodym) (06/29/90)
In article <331@kurz-ai.UUCP> mack@kurz-ai.UUCP (Ed Mackenty) writes: >I'm posting this for a friend since he (obviously) cannot connect to the >net himself: >==================== >I am having problems with setting up a bi-directional uucp link. I am using >a 68000 based machine running AT&T Sys 5.3 with some Berkeley stuff. I put a >uugetty on my port with a modem set up in a standard way. This works fine for >dialing in. When cu or uucp tries to dial out it cannot open the /dev file >since the carrier detect is not on. If I force CD on with a modem switch then >uucp works, but uugetty and the AT echos have a fun time talking to each >other. (login: echos, trying to login as "login:") It seems that I can only >have one or the other. Has anybody else seen this problem? Is there a fix or >a work-around? First of all, set your modem back to the way you had, so that it does not supply a carrier detect (CD) signal. In the Dialers file you should read some of the commentary and you'll probably find that you can put a "M," at the beggining of your dialing script. What this does is tell cu or uucico to open the port with O_NDELAY set (do not wait for CD). uugetty should not interfere. For those of the that know this already, allow me to share one of the more ridiulous solutions to this problem that I've seen recommended, which is to have the uugetty defined in /etc/inittab as only running in INIT 3. So if you wanted to dial out or receive a call you had to switch run levels! Yes, I do know of someone who actually does it that way. Weird. -- | Georg S. Nikodym - (416) 442-2238 | | Southam Business Information and Communications Group, Don Mills, Ontario | | gsn@sclcig.UUCP -or- ...!uunet!attcan!telly!moore!sclcig!gsn | | "The floggings will continue until morale improves" -Josi Castel-Branco |