🚀 go-pugleaf

RetroBBS NetNews Server

Inspired by RockSolid Light RIP Retro Guy

Thread View: comp.os.os2.misc
8 messages
8 total messages Started by Paul Vatta Thu, 26 Jan 1995 10:18
Help needed configuring OS/2 Warp SLIP dialer for Annex server...
#17030
Author: Paul Vatta
Date: Thu, 26 Jan 1995 10:18
33 lines
2461 bytes
I need some help configuring the Warp SLIP dialer to work with my Uni's
terminal server.  The included annex.cmd REXX script doesn't work as it 
doesn't do anything after the modem connects with the message CONNECT XXXXX.
Here is an example of how it appear/worked under Trumpet Winsock for Windows:

> Annex Command Line Interpreter   *   Copyright 1991 Xylogics, Inc.  
>
> Checking authorization, Please wait...
> Annex login: MYUSERNAME
> Password: MYPASSWORD
>
> Permission granted 
> ***WARNING************************WARNING***************************WARNING*** 
>   This service is for AUTHORIZED USERS ONLY.  It is a criminal offence to:  
>       i.  obtain access to data without permission,
>	ii. damage, delete, alter or insert data without permission.  
> ****************************************************************************** 
> Wed Jan 25 21:33:11 1995
> elara port 1 : slip
> Switching to SLIP.
> Annex address is XXX.XXX.XXX.XXX  Your address is XXX.XXX.XXX.XXX.

IP addresses are dynamically allocated.  Any help getting the existing 
script working or any other viable alternative would be appreciated.  
Please email any replies.

Thanks in advance.


-- 
        ---------------------------------------------------
Paul
ninja@deakin.edu.au
Re: Help needed configuring OS/2 Warp SLIP dialer for Annex server...
#17031
Author: Simon Pope
Date: Thu, 26 Jan 1995 11:02
30 lines
2494 bytes
In message <3g7su9$3ad@sol.ccs.deakin.edu.au> - ninja@Deakin.Edu.Au (Paul 
Vatta) writes:
>I need some help configuring the Warp SLIP dialer to work with my Uni's
>terminal server.  The included annex.cmd REXX script doesn't work as it 
>doesn't do anything after the modem connects with the message CONNECT XXXXX.

>IP addresses are dynamically allocated.  Any help getting the existing 
>script working or any other viable alternative would be appreciated.  
>Please email any replies.

I use PPP - which negotiates the IP parameters automatically.
I have found this to be much better than SLIP and somewhat more reliable
through UQ. Does Deakin Uni have PPP capability? If so, I suggest you
use it.

Otherewise, look under the Help for SLIP and it should provide you with
a script that will assist in resolving the IP addresses returned by
your provider.

Also, make sure you have the latest Warp SLIP and PPP drivers...

- Simon.

*******************************************************************
Simon Pope
Akashic Enterprises
PO Box 109              email: akashic.enterprises@mailbox.uq.oz.au
Kedron QLD 4031         Tel: (61-7) 266 9128
Australia
*******************************************************************
Re: Help needed configuring OS/2 Warp SLIP dialer for Annex server...
#17032
Author: synaptec
Date: Thu, 26 Jan 1995 14:54
16 lines
2187 bytes
In <3g7su9$3ad@sol.ccs.deakin.edu.au>, ninja@Deakin.Edu.Au (Paul Vatta) writes:
>I need some help configuring the Warp SLIP dialer to work with my Uni's
>terminal server.  The included annex.cmd REXX script doesn't work as it 
>doesn't do anything after the modem connects with the message CONNECT XXXXX.
>Here is an example of how it appear/worked under Trumpet Winsock for Windows:

I'm not using WARP anymore - downgraded to 2.11 plus TCP/IP 2.0 - but I too had a
similar problem with a REXX script for Annex connection. I think the scripts for WARP's
IAK are taken from the full TCP/IP kit in any case. And case appears to be the issue.

Check the CaSe of the "login" and "PaSSword" prompts from the Annex Server and
how they match with the script. I found that the script used "Login:" and "Password:"
while the Annex Server was issuing all lower case. Guess what? Changing the "L" to
a "l" and the "P" to a "p" in the script did the business.

- andrew
Re: Help needed configuring OS/2 Warp SLIP dialer for Annex server...
#17033
Author: Larry Shurr CB7211
Date: Thu, 26 Jan 1995 18:31
278 lines
13748 bytes
In article <3g7su9$3ad@sol.ccs.deakin.edu.au> ninja@Deakin.Edu.Au (Paul Vatta) writes:
>I need some help configuring the Warp SLIP dialer to work with my Uni's
>terminal server.  The included annex.cmd REXX script doesn't work as it 
>doesn't do anything after the modem connects with the message CONNECT XXXXX.
>Here is an example of how it appear/worked under Trumpet Winsock for Windows:

>> [Annex connect session transcript omitted].

The sample annex.cmd doesn't work for you because it is written to
expect authentication AFTER you enter the SLIP command whereas yours
requires it before.  The basic thing you have to do is rearrange the
waitfor/send commands appropriately.  I include herewith, my
modifications to annex.cmd which support connecting to a Xylogics
Annex terminal server which is identical to the one portrayed in your
session script.  The script also has to negotiate access through an
AT&T Datakit dialup with authentication in order to get to the Annex,
so there's some extra stuff you won't need (basically, everything
related to dkusername, dkpassword, & dkdestination AND the waitfor
routine has a new argument telling it how long to wait).  A diff with
annex.cmd will illustrate the differences very clearly.

------------included------------included------------included------------included
/*--------------------------------------------------------------------------*/
/*                                                                          */
/*        OS/2 2.11 / WARP REX Driver for IBM TCP/IP version 2.0 / IAK      */
/*                                                                          */
/* Sample attachment script for dialing into an Internet access provider.   */
/* This script should be specified on page 1 in the Login Script field for  */
/* connections via SlipPM or using the -connect option if executing slip    */
/* directly.                                                                */
/*                                                                          */
/*        NOTE: This file is supplied as a sample connection script, and    */
/*              does not constitute the endorsement of a particular         */
/*              Internet provider on the part of IBM.                       */
/*              Internet providers periodically change their connection     */
/*              procedures; please refer to the latest information provided */
/*              by the service provider.                                    */
/*                                                                          */
/*              This script may be modified to suit the needs of the user   */
/*              and is written to process dialogs similar to those          */
/*              required by many Annex type service providers.              */
/*                                                                          */
/* When the script runs, it is automatically passed the interface name for  */
/* the interface it is running on as the first argument, followed by the    */
/* user arguments.                                                          */
/*                                                                          */
/* The script sends the dial string to the modem and then logs into the     */
/* terminal server using the username/password.  It then issues the SLIP    */
/* command to start SLIP, and parses the resulting output to determine the  */
/* appropriate addresses to use.  Lastly, it issues ifconfig and route      */
/* commands to configure the OS/2 system appropriately.  Note that the      */
/* configuration assumes a class C netmask for the SLIP interface.          */
/*                                                                          */
/*--------------------------------------------------------------------------*/

parse arg interface , dialcmd dkusername dkpassword dkdestination username password

/*--------------------------------------------------------------------------*/
/*                   Initialization and Main Script Code                    */
/*--------------------------------------------------------------------------*/

/* Set some definitions for easier COM strings */
cr='0d'x
crlf='0d0a'x

say ''
say 'ANNEX - SLIP ANNEX Cybernet Server Connection Script ',
    '(interface' interface')'

/* Flush any stuff left over from previous COM activity */
call flush_receive

/* Reset the modem here */
/* You may need to customize this for your modem make and model */
call lineout , 'Reset modem...'
call send 'AT&F' || cr
call waitfor 'OK', 5 ; call flush_receive 'echo'
 if RC = 1 then do
    call lineout , 'Modem not resetting... Trying again'
    call send '+++'
    call waitfor 'OK'
    call send 'ATHZ' || cr
    call waitfor 'OK', 3
  end

/* Dial the remote server */
call charout , 'Now Dialing...'

/* Wait for connection */
call send dialcmd || cr
call waitfor 'CONNECT' ; call waitfor crlf

/* Handle login.  We wait for standard strings, and then flush anything */
/* else to take care of trailing spaces, etc..                          */
/* call send cr */
call waitfor 'USERID:'         ; call flush_receive 'echo'
call send dkusername || cr
call waitfor 'Password:'       ; call flush_receive 'echo'
call send dkpassword || cr
call waitfor 'DESTINATION:'    ; call flush_receive 'echo'
call send dkdestination || cr
call waitfor 'username:'       ; call flush_receive 'echo' , 2000
call send username || cr
call waitfor 'password:'       ; call flush_receive 'echo' , 2000
call send password || cr
call waitfor 'annex:'          ; call flush_receive 'echo'
call send 'SLIP' || cr

/* Parse the results of the SLIP command to determine our address. */
/* We use the "waitfor_buffer" variable from the waitfor routine   */
/* to parse the stuff we get from the Annex after waiting for an   */
/* appropriate point in the data stream.                           */
call waitfor 'Your address is' 
parse var waitfor_buffer . 'Annex address is' a '.' b '.' c '.' d '.' .
annex_address = a||'.'||b||'.'||c||'.'||d

call waitfor crlf 
parse var waitfor_buffer  a '.' b '.' c '.' d '.' .
os2_address = a||'.'||b||'.'||c||'.'||d

/* Flush anything else */
call flush_receive 'echo'

/* Now configure this host for the appropriate address, */
/* and for a default route through the Annex.           */

say 'SLIP Connection Established'
say 'Configuring local address =' os2_address ', Annex =' annex_address

'ifconfig sl0' os2_address annex_address 'netmask 255.255.255.0'
'route add default' annex_address '1'

/* All done */
exit 0


/*--------------------------------------------------------------------------*/
/*                            send ( sendstring)                            */
/*..........................................................................*/
/*                                                                          */
/* Routine to send a character string off to the modem.                     */
/*                                                                          */
/*--------------------------------------------------------------------------*/

send:

   parse arg sendstring
   call slip_com_output interface , sendstring

   return


/*--------------------------------------------------------------------------*/
/*                    waitfor ( waitstring , [timeout] )                    */
/*..........................................................................*/
/*                                                                          */
/* Waits for the supplied string to show up in the COM input.  All input    */
/* from the time this function is called until the string shows up in the   */
/* input is accumulated in the "waitfor_buffer" variable.                   */
/*                                                                          */
/* If timeout is specified, it says how long to wait if data stops showing  */
/* up on the COM port (in seconds).                                         */
/*                                                                          */
/*--------------------------------------------------------------------------*/

waitfor:

   parse arg waitstring , timeout

   if timeout = '' then
     timeout = 5000    /* L O N G   delay if not specified */
   waitfor_buffer = '' ; done = -1; curpos = 1
   ORI_TIME=TIME('E')

   if (remain_buffer = 'REMAIN_BUFFER') then do
      remain_buffer = ''
   end

   do while (done = -1)
      if (remain_buffer \= '') then do
         line = remain_buffer
         remain_buffer = ''
       end
       else do
         line = slip_com_input(interface,,10)
      end
      waitfor_buffer = waitfor_buffer || line
      index = pos(waitstring,waitfor_buffer)
      if (index > 0) then do
         remain_buffer = substr(waitfor_buffer,index+length(waitstring))
         waitfor_buffer = delstr(waitfor_buffer,index+length(waitstring))
         done = 0
      end
      call charout , substr(waitfor_buffer,curpos)
      curpos = length(waitfor_buffer)+1
      if ((done \= 0) & (TIME('E')>timeout)) then do
        call lineout , ' WAITFOR: timed out '
        done = 1
       end
   end
   timeout=0
   RC=done
 return RC



/*--------------------------------------------------------------------------*/
/*                               readpass ()                                */
/*..........................................................................*/
/*                                                                          */
/* Routine used to read a password from the user without echoing the        */
/* password to the screen.                                                  */
/*                                                                          */
/*--------------------------------------------------------------------------*/

readpass:

  answer = ''
  do until key = cr
    key = slip_getch()
    if key \= cr then do
      answer = answer || key
    end
  end
  say ''
  return answer


/*--------------------------------------------------------------------------*/
/*                             flush_receive ()                             */
/*..........................................................................*/
/*                                                                          */
/* Routine to flush any pending characters to be read from the COM port.    */
/* Reads everything it can until nothing new shows up for specified time-   */
/* interval, at which point it returns.                                     */
/*                                                                          */
/* The optional echo argument, if non-empty, means echo flushed info.       */
/*                                                                          */
/* The optional timeout argument, specifies a timeout interval in milli-    */
/* seconds.  The default is 100.  Unfortunately, I do not know enough       */
/* about Rexx to make the first argument, echo, optional if you want to     */
/* specify a timeout, so if you want to specify a timeout and no echo, I    */
/* guess you'll just have to say "flush_receive '',<timeout>".  Sorry.      */
/*                                                                          */
/*--------------------------------------------------------------------------*/

flush_receive:

   parse arg echo , timout

   if timout = '' then
     timout = 100

   /* If echoing the flush - take care of waitfor remaining buffer */
   if (echo \= '') & (length(remain_buffer) > 0) then do
      call charout , remain_buffer
      remain_buffer = ''
   end

   /* Eat anything left in the modem or COM buffers */
   /* Stop when nothing new appears for 100ms.      */

   do until line = ''
     line = slip_com_input(interface,,timout)
     if echo \= '' then
        call charout , line
   end

   return
------------included------------included------------included------------included

Regards,
Larry
--
Larry A. Shurr (las@cbnmva.cb.att.com or lshurr@freenet.columbus.oh.us)
Norman, listen carefully.  I am lying.  Are you sure your circuits are
registering?  Your ears are green.  Logic is a little bird singing in a
meadow.  Logic is a wreath of pretty flowers which smell bad! - Mr. Spock
Re: Help needed configuring OS/2 Warp SLIP dialer for Annex server...
#17034
Author: Paul Vatta
Date: Fri, 27 Jan 1995 09:33
20 lines
2025 bytes
Thanks for all replies to my problem.  I suppose I should have mentioned
that I had already modified the script for our server.  What the problem
was is that the connection 'hung' after it connected ie with the CONNECT
XXXXXX message.  Apparently this is a common problem.  The fault lies with
the COM.SYS driver.  The replacement is available via ftp, which when
installed solved the problem.

Just out of curiousity, I tried the SIO.SYS drivers to see if they would
solve the problem as well - they didn't.

Aside, has anyone experienced problems with the PPP (gamma version) dialer?
I tried have multiple entries but after entering a second entry, the first
one would be deleted.  Guess I'll have to wait for the next version.

Thanks in advance,
Paul.
-- 
        ---------------------------------------------------
Paul
ninja@deakin.edu.au
Re: Help needed configuring OS/2 Warp SLIP dialer for Annex server...
#17035
Author: mount
Date: Fri, 27 Jan 1995 16:06
28 lines
2257 bytes
In <3gaekm$t91@sol.ccs.deakin.edu.au>, ninja@Deakin.Edu.Au (Paul Vatta) writes:
>Thanks for all replies to my problem.  I suppose I should have mentioned
>that I had already modified the script for our server.  What the problem
>was is that the connection 'hung' after it connected ie with the CONNECT
>XXXXXX message.  Apparently this is a common problem.  The fault lies with
>the COM.SYS driver.  The replacement is available via ftp, which when
>installed solved the problem.
>
>Just out of curiousity, I tried the SIO.SYS drivers to see if they would
>solve the problem as well - they didn't.
>

[snip]

I have had the same problems. Have you tried setting the port to 19.2Kbps
or slower? That's the only way that I could get os/2's new dial-up slip to
work (the one in the tcp/ip package works fine).

>Thanks in advance,
>Paul.
>-- 
>        ---------------------------------------------------
>Paul
>ninja@deakin.edu.au

Good luck,
George Mount
mount@leland.stanford.edu
Re: Help needed configuring OS/2 Warp SLIP dialer for Annex server...
#17036
Author: Anon
Date: Sun, 29 Jan 1995 15:28
40 lines
2917 bytes
In <3g7su9$3ad@sol.ccs.deakin.edu.au>, ninja@Deakin.Edu.Au (Paul Vatta) writes:
>I need some help configuring the Warp SLIP dialer to work with my Uni's
>terminal server.  The included annex.cmd REXX script doesn't work as it 
>doesn't do anything after the modem connects with the message CONNECT XXXXX.
>Here is an example of how it appear/worked under Trumpet Winsock for Windows:
>
>> Annex Command Line Interpreter   *   Copyright 1991 Xylogics, Inc.  
>>
>> Checking authorization, Please wait...
>> Annex login: MYUSERNAME
>> Password: MYPASSWORD
>>
>> Permission granted 
>> ***WARNING************************WARNING***************************WARNING*** 
>>   This service is for AUTHORIZED USERS ONLY.  It is a criminal offence to:  
>>       i.  obtain access to data without permission,
>>	ii. damage, delete, alter or insert data without permission.  
>> ****************************************************************************** 
>> Wed Jan 25 21:33:11 1995
>> elara port 1 : slip
>> Switching to SLIP.
>> Annex address is XXX.XXX.XXX.XXX  Your address is XXX.XXX.XXX.XXX.
>
>IP addresses are dynamically allocated.  Any help getting the existing 
>script working or any other viable alternative would be appreciated.  
>Please email any replies.
>
>Thanks in advance.
>
>
>-- 
>        ---------------------------------------------------
>Paul
>ninja@deakin.edu.au


Had a similar problem - turned out that the quoted text (i.e. "Annex:") in the script did
did not exactly match what the server was sending - this is a alpha pattern matching
comparing two text strings - the must match exactly and are case sensitive.  I simply changed
"Annex:" to "annex:" and everything worked fine.
Re: Help needed configuring OS/2 Warp SLIP dialer for Annex server...
#17037
Author: Dragon Slayer
Date: Thu, 30 Mar 1995 00:00
47 lines
2854 bytes
In <3g7su9$3ad@sol.ccs.deakin.edu.au>, ninja@Deakin.Edu.Au (Paul Vatta) writes:
>I need some help configuring the Warp SLIP dialer to work with my Uni's
>terminal server.  The included annex.cmd REXX script doesn't work as it 
>doesn't do anything after the modem connects with the message CONNECT XXXXX.
>Here is an example of how it appear/worked under Trumpet Winsock for Windows:
>
>> Annex Command Line Interpreter   *   Copyright 1991 Xylogics, Inc.  
>>
>> Checking authorization, Please wait...
>> Annex login: MYUSERNAME
>> Password: MYPASSWORD
>>
>> Permission granted 
>> ***WARNING************************WARNING***************************WARNING*** 
>>   This service is for AUTHORIZED USERS ONLY.  It is a criminal offence to:  
>>       i.  obtain access to data without permission,
>>	ii. damage, delete, alter or insert data without permission.  
>> ****************************************************************************** 
>> Wed Jan 25 21:33:11 1995
>> elara port 1 : slip
>> Switching to SLIP.
>> Annex address is XXX.XXX.XXX.XXX  Your address is XXX.XXX.XXX.XXX.
>
>IP addresses are dynamically allocated.  Any help getting the existing 
>script working or any other viable alternative would be appreciated.  
>Please email any replies.
>
>Thanks in advance.
>
>
>-- 
>        ---------------------------------------------------
>Paul
>ninja@deakin.edu.au
>
OK....
Well I have it setup, I had all the same probs as you did by the sounds of things.
OK.
In the other internet dialler section, page 1 of modify provider. You need to specify your script. Also on this line you need to specify the dial command and the login name and the password.
So it should look something like this.
c:\tcpip\bin\annex.cmd atd271000 <loginname> <password>

Well this is what I found was the biggest prob... After that I had no worries...
If you have anymore questions forward them to 
tanga@deakin.edu.au

Cya later.
Thread Navigation

This is a paginated view of messages in the thread with full content displayed inline.

Messages are displayed in chronological order, with the original post highlighted in green.

Use pagination controls to navigate through all messages in large threads.

Back to All Threads