gpz@bridge2.ESD.3Com.COM (G. Paul Ziemba) (08/24/89)
greg@moxie.UUCP (Greg Hackney) writes: >In article clewis@eci386 (Chris Lewis) writes: >>Has anyone out there tried running uucp through a modem (especially a >>Trailblazer Plus) on a Bridge box (or any other serial-to-Ethernet >>conversion box)? We are having problems in sending uucp >Our LAN is by Bridge Communications, and works well with uucp. The >major trick was to disable the flow control on all the associated network >ports and let uucp pace itself with it's own error protocol. >-- >Greg Last year, after plowing through the comserver manual and experimenting a lot, I succeeded in getting uucp to work through our comservers. In the course of that experimentation, I discovered a bug which caused the comserver to interpret the first NULL after disabling the ECM character as a break, but I believe that was fixed before the current release. Here is a sample L.sys entry which I use to communicate with another system via two 3com (nee Bridge) comservers (there are serial lines between the comservers and the hosts, and ethernet between the two comservers). remotehost Any,0 DIR 9600 ttyb "" BREAK \ login:~2-l\r\d\d\r-login:~3-BREAK\dl\d-login:~2 netuser rd:~3 netpwd \ >~3 c\s135.205.104.31\secm >~3 \ set\sfcf=n\sfct=n\smo=t\sbra=ig\sbra=edtm\sxb=on\secmc=d\sbrc=d \ >~3 res ed~3 "" in:~2--in:~2 uudfh rd:~3 lkjhsdf The fact that there is a comserver on the remote end is not particularly relevant to this discussion. What I do is disable all of the "special" characters on my serial connection; BREAK is then necessary to cause the comserver to return to command mode. Here's an explanation of each field I put in the L.sys entry: The first expect ("") just times out, causing the BREAK to be sent. The second expect-send-... (the one that starts "login:~2...") gets the comserver line into a known state. Our comservers are running with access control, so the "login:" prompt in the first field really refers to the prompt given by the comserver (which, in full, is something like "Network login:"). Note that "~2" means "wait only two seconds for the expected string". "netuser" is the network userid for comserver access control. "rd:~3" waits for the comserver password prompt. "netpwd" sends the password corresponding to "netuser". ">~3" waits for the comserver command prompt. "c\s135.205.104.31\secm" sends the command to connect to an ip address, but to immediately suspend the connection and remain in command mode. This is done because some parameters (to follow) can be set only after a connection has already been established. Note that the L.sys sequence "\s" means "send a space". "set\sfcf=n\sfct=n\smo=t\sbra=ig\sbra=edtm\sxb=on\secmc=d\sbrc=d" sets a whole bunch of comserver paramaters: fcf=n turn off flow control "from"; that is, disable any mechanism for the comserver to attempt to send XOFF/XON or use ENQ/ACK, or use hardware flow control. fct=n turn off any interpretation by the comserver of "special" flow-control characters like XON or XOFF. mo=t set mode to "transparent"; that is, send all data from the terminal line to the ethernet except for whatever "special" characters are defined as the ECM character and BREAK character. bra=ig reset the break-action parameter to "ignore". This "clears" the break-action vector, in preparation for the next command. bra=edtm specify that the comserver should return to command mode upon receipt of a break from the serial line. xb=on (TCP versions 20000 or later) specify that the comserver should use an 8-bit data path to the remote end of the connection instead of a 7-bit path. Note that if xb is off, carriage returns from the serial line will be padded with a null or a linefeed. ecmc=d disable the ECM character. That is, specify that no ascii character should be interpreted by the comserver as an "escape-to-command-mode" character. brc=d disable the Break character. That is, specify that no ascii character should be interpreted by the comserver as a BREAK. (in this case, only a real BREAK, which is not an ascii character, is interpreted as a break). ">~3" waits for the comserver command prompt. "res" causes the comserver to resume the connection. "ed~3" waits for the comserver "connected" message. "" sends nothing (maybe a CR). "in:~2--in:~2" waits for "login:" on the remote host. "uudfh" sends the userid to the remote host. "rd:~3" waits for "Password:" on the remote host. "lkjhsdf" transmits the password to the remote host. If you are using the comserver to connect to a modem, which will then dial the remote system, then everything up to and including "ed~3" should go in the chat script (in L-devices, I think) because it is necessary to perform it before uucico gives the modem commands. Of course, you will also need to customise things like userids, etc. to your particular installation, and omit the comserver access control stuff if you are not using access control. Good Luck! ~!paul -- ---- Paul Ziemba ...!pyramid!zapi!gpz gpz@bridge2.3com.com (415)940-7671 (w)