🚀 go-pugleaf

Greg Andrews (gerg@netcom.com) wrote:
: wolfgang@netcom.com (Wolfgang Henke) writes:
: >Greg Andrews (gerg@netcom.com) wrote:
: >: and the setup guide for SunOS 4.x provided by Telebit.
: >
: >It's available from telebit.whnet.com /pub/tech-support/modems:
: >
: >   ==========================================================================
: >   Telebit Corp.              Modem Setup Guide           Revised: 4/1/94 
: >   (Filenames) BBS & CompuServe: SUN4.msg  ftp: SUN4_msg
: >	       Applelink:  
: >   FAXBACK DOC #: 
: >   Author:                                          Revised by:  Jaime Sainez
: >   --------------------------------------------------------------------------
: >
: >     SETUP INSTRUCTIONS FOR TELEBIT MODEMS AND SUNOS 4.X WORKSTATIONS
: >
: >     The following examples should allow easy initialization of a TELEBIT 
: >     modem for use with dialin/dialout and UUCP on a SUN 3 or SUN 4 
: >     workstation with SUNOS 4.X.
: >
: >       NOTE:  These configuration instructions are meant for SUNOS 4.0.3 or
: >	      higher release versions.  It is highly recommended that the
: >	      operating system be upgraded to this release version or that
: >	      the TTY PATCH 5.4 (or higher) be installed before these set-ups
: >	      are attempted.  This patch is available from SUN.
: >


: That's the wrong setup guide.  Completely wrong.  Ask Jaime to stop
: using that one and start using the one I wrote.  It hasn't been necessary
: to reconfigure the kernel since version 4.1.0.


Greg,

well, the one posted earlier was for 4.x, which should have been 4.0.3
I guess. Here is the one for 4.1.x. How come you dont post in c.d.m any 
longer? Too busy?

Cheers,

Wolfgang


ftp.whnet.com /pub/tech-support/modems/setup-guides/SUN_Workstations...

   ==========================================================================
   Telebit Corp.        NetBlazer Application Note          Revised: 5/17/94 
   (Filenames) BBS & CompuServe: SUN.msg
               ftp: SUN_Workstations_SUNOS_41X_msg
               Applelink:  
   FAXBACK DOC #: 
                                                   Revised by:  Jaime Sainez
   --------------------------------------------------------------------------

  SETUP INSTRUCTIONS FOR TELEBIT MODEMS AND SUN WORKSTATIONS WITH SUNOS 4.1.x

     The following examples should allow easy initialization of a TELEBIT 
     modem on a Sun workstation running SunOS 4.1.x.  This guide describes 
     the steps for installing any Telebit modem except for the QBlazer 
     transportable modem.  QBlazer installations are described in another 
     guide.

     Most installations use the modem for both dial-in and dial-out, so this
     guide describes how to configure the computer and modem for combined 
     dial-in and dial-out operation.  If you're not going to use the modem 
     for both types of operations, skip the section that doesn't apply to 
     your installation.

     These examples assume the modem will be attached to the computer's 
     "ttya", port, which is one of the on-board ports in most Sun 
     workstations.  If the modem is on a different port, substitute the other 
     port name in your setup.

     Although the WorldBlazer, T3000, and T1600 modems can support RS232 port
     speeds higher than 19200 bps, this guide configures them for 19200 bps 
     on dial-in.  38400 bps operation may not be reliable on some 
     workstations or serial port boards, so it's wise to start with the 
     slower speed first.  Later, when you're sure everything else works, you 
     can try boosting the speed up to 38400 bps.

     ---[ Section 1 - Pre-Installation ]-------------------------------------

     Before performing any other installation steps, the computer and modem 
     need to be prepared for each other.


     1.1  Turn off any getty processes that might be running on the modem 
          port by editing the /etc/ttytab file and re-starting init.

          Edit the /etc/ttytab file with a text editor.  Find the entry for 
          the modem port and change that entry's status field to "off".  It 
          should look like this:

         # name   getty                        type      status  comments
         #
         ttya     "/usr/etc/getty std.9600"    unknown   off   local secure

         Save the changes and exit the editor.

         Enter this command:

                 kill -HUP 1


     1.2  Reset the modem to its factory default settings as documented in 
          the Reference Manual or User's Guide.

          WorldBlazer/T3000/T1600 modems:  Reset modem to TTY defaults (&F0).

          T2500/TrailBlazer Plus/T2000/T1000 modems:  Reset modem to Enhanced
          Command Mode (ECM) Asynchronous defaults.


     1.3  Connect the modem to the computer through the RS232 serial cable,
          and plug the telephone line into the modem's LINE jack.


     ---[ Section 2 - Modem Configuration ]----------------------------------

     2.1  Change directories to /dev and enter the following command to 
          create the dial-out device file for the ttya port:

            mknod cua0 c 12 128      (for ttyb enter:  mknod cub0 c 12 129)

      If the mknod command returns a "file exists" error, skip to Step 2.2.
      Otherwise, enter the following command:

            chmod 666 cua0           (for ttyb enter:  chmod 666 cub0)


      2.2  Change directories to /etc and edit the /etc/remote file with a 
           text editor.  Create the following entries:

            tb38400:dv=/dev/cua0:br#38400:el=^C^S^Q^U^D:ie=%$:oe=^D:

            tb19200:dv=/dev/cua0:br#19200:el=^C^S^Q^U^D:ie=%$:oe=^D:

            tb9600:dv=/dev/cua0:br#9600:el=^C^S^Q^U^D:ie=%$:oe=^D:

      Save the changes and exit the editor.


     2.3  Enter this command to connect to the modem:

              tip tb9600

       NOTE:  If tipping through the SUN Open Windows environment, use a 
              SHELL tool, *not* a COMMAND tool.

     2.4  Type the following commands to the modem.  Use only the commands 
          for your particular modem:

            WorldBlazer, T3000, or T1600 modem:
                    AT &F3 E1 X0 &S0 S2=255 S45=255 S48=0 S58=2 &W
                    AT S59=15 S68=255 S111=255 S180=2 &C1 &W

            T2500, TrailBlazer Plus, T2000 or T1000 modem:
                    AT &F X0 Q4 S45=255 S48=1 S51=254 S52=2 S54=3 &W
                    AT S58=2 S64=1 S66=1 S95=2 S97=1 S106=1 S131=1 &W

      When you press Return at the end of a command, the modem should respond 
      with "OK".  If you get disconnected on the first command, repeat steps 
      2.3 and 2.4.  You can review the modem's settings by typing "AT&V" or 
      "ATN?".

      Exit tip by pressing Return, Tilde (~), and then Period (.).

     ------------------------------------------------------------------------
       NOTE:  Check your modem reference manual for descriptions of each 
              register and the meanings for each of the above settings.

        In the TrailBlazer Plus, T2500, T2000 and T1000 settings, the S97 and 
        S106 registers control V.42/LAP-M error correction.  If your modem 
        doesn't have V.42 support, you can omit S97 and S106 from the modem 
        commands.  The S131 register controls the modem's DCD signal.  Older 
        modems used the S53 register to control DCD instead of S131.  If your 
        modem doesn't support S131, then set S53=1 instead.


     ---[ Section 3 - Setup for Dial-Out Operation ]-------------------------

     3.1  Edit the /etc/remote file with a text editor and add the following
          entry:

               TELEBIT|Telebit autodialing parameters:\
                      :el=^D^U^C^S^Q^O^@:du:at=hayes:ie=#$%:oe=^D:\
                      :dv=/dev/cua0:

          Save the changes and exit the editor.

          The entry above describes to tip how to talk to the Telebit modem.
          You can add entries for dialing other computers and have them
          reference the Telebit info using the "tc" parameter.  For example:

               home|call my computer at home:\
                      :pn=5551212:br#19200:tc=TELEBIT:


     3.2  Change directories to /etc/uucp and edit the Dialers file with a
          text editor.  Create the following lines:

     # tbnorm: for 'normal' calls with modem error control
     # tbplain: for 'plain' calls without error control
     # tbuumnp: for selecting UUCP protocol support in MNP mode
     # tbuupep: for selecting UUCP protocol support in PEP mode
     tbnorm    =W-, "" ATE0X1 OK ATDT\T CONNECT
     tbplain   =W-, "" ATE0X1S180=0S95=0S97=0S106=0 "" \dATDT\T CONNECT
     tbuumnp   =W-, "" ATE0X1S111=30S180=3 OK ATDT\T CONNECT
     tbuupep   =W-, "" ATE0X1S7=60S50=255S111=30 OK ATDT\T CONNECT-\c-CONNECT

      Save the changes and exit the editor.


     3.3  Edit the Devices file with a text editor.  If there are any lines
          that reference the modem dial-in port (ttya) or dial-out port 
          (cua0), comment them out by inserting a "#" at the beginning of 
          each line.

          If you have a WorldBlazer, T3000, or T1600, create these entries:

               ACUNORM  cua0 - 300-38400 tbnorm
               ACUPLAIN cua0 - 300-38400 tbplain
               ACUUMNP  cua0 - 300-38400 tbuumnp

          If you have a WorldBlazer, also add this entry:

               ACUUPEP  cua0 - 300-38400 tbuupep

          If you have a T2500, TrailBlazer Plus, T2000 or T1000 create these 
          entries instead of the ones above:

               ACUNORM  cua0 - 300-19200 tbnorm
               ACUPLAIN cua0 - 300-19200 tbplain
               ACUUPEP  cua0 - 300-19200 tbuupep

          Note the highest RS232 port speed for these modems is 19200.

          Save the changes and exit the editor.


     ---[ Section 4 - Setup for Dial-In Operation ]--------------------------

     4.1  Change directories to /etc and edit the gettytab file with a text
          editor.  Look for the entry named "std.19200".  Modify the entry to 
          match the following example.  If the entry doesn't exist, create it 
          as a new entry:

               std.19200|19200-baud:\
                       :sp#19200:ms=crtscts:

          Save the changes and exit the editor.


     4.2  If the modem is not connected to one of the on-board serial ports 
          (ttya or ttyb), then skip this step.  Go to Step 4.3.

          Before getty is started, the computer must have its "software" 
          carrier detection disabled.  Without software carrier detection the 
          computer will respond to the modem's DCD signal.  This is critical 
          for correct operation with a modem.  The computer must respond to 
          DCD.  Enter the following command:

               ttysoftcar -n ttya

         You can confirm the kernel's handling of the modem port by entering:

               ttysoftcar ttya

         The system should report "ttya is n".


     4.3  Edit the ttytab file with a text editor.  If there are any lines 
          that reference the dial-out port (cua0), delete them.  The system
          must NOT run getty on the dial-out port device.  Getty should only
          be run on the dial-in port device (ttya).  Modify the dial-in port
          line to look like this:

               ttya     "/usr/etc/getty std.19200"    dialup   on

          You may add other status keywords after the "on" keyword, but be 
          sure you do NOT add the "local" keyword.  "Local" defeats the 
          hardware carrier detect configuration we did in Step 4.2.  If you
          are installing the modem on a multiport board, follow the setup
          instructions for your multiport board to create the ttytab entry.

          Save the changes and exit the editor.


     4.4  Start getty running on the dial-in port by entering this command:

                 kill -HUP 1



     ---[ Section 5 - Configuration Notes ]----------------------------------

     Some users turn the speaker off (M0) and disable remote access (S45=0) 
     when the modem installation is finished and everything is working 
     properly.


     Dial-In configuration:
     ----------------------
     The dial-in configuration uses a "fixed speed" getty, and the modem is
     configured to always communicate with the computer at 19200 bps.  Even 
     if someone calls in at a different speed (e.g. 2400 bps), the modem will
     manage the difference in speeds.

     The modem is configured to use RTS/CTS flow control, also known as 
     "hardware handshaking".  The computer must also use RTS/CTS flow 
     control, or data could be lost in some situations.  The "ms=crtscts" 
     code in gettytab turns on the computer's RTS/CTS flow control, however 
     this code may not work on all Sun workstations.  Multiport boards may 
     use other methods for enabling RTS/CTS flow control on the computer's 
     serial port.  Contact your Sun support group for more information on 
     whether your computer can support RTS/CTS flow control.  If your 
     computer cannot handle RTS/CTS flow control, configure the modem for 
     'compromise' XON/XOFF flow control (S58=0 S68=3) in Step 2.4, and remove 
     the "ms=crtscts" code in the /etc/gettytab entry.

     If you want your dial-in configuration to use a different port speed 
     (for example, 9600 bps), adjust the modem's S51 register accordingly and 
     use the correct speed entry in /etc/gettytab.


     Dial-Out Configuration:
     -----------------------
     Tip's dial-out configuration is controlled by the /etc/remote file.  
     Check the man page for tip and remote, or contact your Sun support group 
     if you need more information about configuring tip (e.g. turning on 
     RTS/CTS flow control).  The uucp dial-out configuration supports port 
     speeds from 300 bps to 38400 bps for the WorldBlazer/T3000/T1600 modem 
     family, and speeds from 300 bps to 19200 bps for the T2500/TrailBlazer 
     Plus/T2000/T1000 modem family (see note above).  The dial-out scripts in 
     the Dialers file are used to configure the modem for the most common 
     types of calls.  Note that the "tbplain" script takes advantage of 
     certain capabilities among the older and newer families of Telebit 
     modems, where the modems can accept commands intended for the other 
     modem family.

     Example Systems file entries to access the different dialers:

       mysystem Any ACUNORM 19200 5551212  ogin: hello ssword: itsme
       mysystem Any ACUPLAIN 19200 5551212  ogin: hello ssword: itsme
       mysystem Any ACUUPEP 19200 5551212  ogin: hello ssword: itsme
       mysystem Any ACUUMNP 19200 5551212  ogin: hello ssword: itsme

     The third field in each Systems file entry declares the 'device type' to 
     be used for the call.  This field is matched to the first field in the 
     Devices file entry to select the dialer.  The different device types in 
     these examples will select the appropriate features in the modem.

       NOTE:  The "ACUPEP" device type is not appropriate for T3000 or T1600
              modems (they don't support PEP).  The "ACUMNP" device type is
              not appropriate for the T2500/TrailBlazer Plus/T2000/T1000 
              family of modems (they don't have UUCP protocol support in MNP 
              modes).

     ====================[ End of Setup Guide ]==============================
-- 
WH Networks  .................  file://ftp.whnet.com/pub/wolfgang/home.html
2672 Bayshore Parkway Suite 503  ..........................  (415) 390-9316
Mountain View CA 94043  ...............................  fax (415) 390-9317