home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
OS/2 Shareware BBS: 35 Internet
/
35-Internet.zip
/
PPP0727.txt
< prev
next >
Wrap
Text File
|
1995-08-03
|
8KB
|
180 lines
READ ME for the OS/2 PPP/Dialer update:
Abstract for OS/2 PPP/Dialer update:
This update for OS/2 PPP fixes several problems reported over the past
3-4 months. Most notably a fix to allow SLIP and PPP to operate over
LAN shared modems (LAN Requester) was implemented and code changes to
allow OS/2 PPP to interoperate with Microsoft NT servers was added.
Limited user level debugging support has been added to the SlipPM dialer
and several dialer fields have been made longer to accommodate international
phone numbers, etc. See below for a complete list of problem fixes covered
in this update.
NOTICE: The versions of slippm, slip, ppp, and slattach delivered in this
package are NOT compatible with previous releases (i.e. an older version
of slattach will not function properly with the new version of slip and
slippm). When upgrading ensure that all componets are replaced as a
group.
Contents:
Executable files:
ppp.exe OS/2 TCP/IP 2.0 PPP driver.
pppterm.exe Dumb terminal emulation over a PPP link.
slippm.exe Dialer code for SLIP and PPP connections. Provides dial-up
access to the Internet via access provider networks.
slattach.exe Modem set-up and connection processor.
slip.exe OS/2 TCP/IP 2.0 SLIP driver.
slipterm.exe Dumb terminal emulation over SLIP link.
slipmsg.exe Processes error messages for the PPP and SLIP drivers.
Optional configuration files:
ppp.cfg File of configurable options. This file is searched for
using the $ETC environment variable.
ppprc File of configurable options. This files is searched for
using the $HOME environment variable. Options in this
file override options in the ppp.cfg file. Command line options override both ppprc and ppp.cfg options.
Authentication files:
pap.sct Contains client names, server names, pap passwords and valid
IP addresses for the client.
chap.sct Contains client names, server names, chap passwords and valid
IP addresses for the client.
Problems fixed in this update:
+ If a Dial Prefix is entered for the 1st defined machine to dial and
you double click to dial that entry, the Dial Prefix is blanked out.
If the DIAL Icon is selected, the Prefix is not deleted. Double
clicking on other entries in the list work fine.
+ When Adding an Entry (Dial Other Internet Providers folder),
the 5th field, phone number, allows 32 numbers to be entered.
However, it only saves 24 of these digits. Therefore, a user
needing 32 digits assumes he has set up correctly but then
finds he is unable to place his call.
+ Users are able to toggle the Enable Debug checkbox when SLIPPM is dialing
and/or has a connection established. The checkbox has no function at this
time and users should not be allowed to change the status.
+ The DESCRIPTION field in the dial other internet providers according to the
doc is a required field. It is not marked with an '*'.
+ After setting the baud rate for a provider to 115200 and saving
those settings, the baud rate is improperly set to 49664.
Note: The complete fix to this problem requires a new version of
the TCP/IP stack and the use of the SIO.SYS com drivers.
+ SLIPPM and PPP do not work with PEER (LAN requested modems).
+ slattach -f options does not accept absolute path.
+ PPP Null modem connection gets established and then fails with msg:
notice: DCD lost, exiting.
+ When VJ compression is enabled, compressed packets are not decompressed
correctly by the 8235 box. Additionally the MTU size set during
IPCP negotiation exceeds 4096, causing FCS errors to be generated
when packets are received.
+ Connection fails during LCP stage for providers that hang-up after receiving
a reject on an unknown authentication protocol.
SlipPM Login Sequences:
Many Internet providers that support the slip protocol will assign you a
unique pair of IP addresses after you register for their service. Each
time you login to the service you will connect with this same set of
IP addresses. This is often called "static" IP address assignment. Other
Internet providers supporting slip connections will assigned you an IP
address pair at the time the connection is established. This is often
referred to as "dynamic" IP address assignment. Each time you connect you
may receive a different IP address pair.
On page one of the SlipPM Provider Dialog, the field "Login Sequence:" defines
the login sequence used to connect to a given access provider. To
accommodate a variety of connection sequences, this field may contain:
(1) The reserved word "NONE". This indicates no login sequence
is required beyond the physical modem connection.
(2) Blank, or no entry. If this field is left blank, and the
Login ID and Password fields are filled in, then the dialer
will wait for the login sequence:
login:
password:
The content of the Login ID and passwords will be sent in response.
(3) The name of a REXX connection script or ".cmd" file, for example,
Login Sequence: annex.cmd
This script is executed at connection time to negotiate the
modem setup, dial the access provider, and login.
(4) A login sequence consisting of a series of send-expect verbs,
for example, if the "Login Sequence:" contains the text:
\r
sername:
[LOGINID]
ssword:
[PASSWORD]
annex:
slip
address\sis\s[$IPDEST]\sYour\saddress\sis\[$IPADDR]
then after the modem dials and connects, line 1 sends a newline to
request the Username prompt. Line 2, waits for this prompt, and
line 3 sends the contents of the Login ID field. Line 4 waits for
a Password prompt, and line 5 sends the password entered in the
Password field. Line 6 waits for the "annex:" prompt, and line 7
sends the request to start the SLIP protocol. Line 8 is used
to retrieve the remote and local IP addresses that are "dynamically"
assigned when the connection is made. The "\s" (Escape s) represents
1 or more white-space characters.
If your IP addresses are "statically" assigned then you can enter
them on page 2 of the provider information dialog.
Each provider uses a slightly different sequence for establishing a
connection, and you must tailor your Login Sequence to match
each Internet provider.
For Internet providers supporting PPP the situation is slightly
more uniform, however there are still many differences. Most
providers fall into two categories, those that require a
traditional style login id and password transaction before
the PPP protocol is started, and those that negotiate PPP
immediately upon connection. For the first type you will
need to setup a Login Sequence similar to that used for a
slip connection, in the second type, enter the verb "NONE"
in the Login Sequence field.
In most cases, PPP Internet providers supporting PPP will
use the PPP protocol itself to assign you an IP address
pair, so once a connection is established and the two
machines have successfully engaged in the link control protocol
(LCP) stage of a PPP link, IP addresses will be assigned and
the ppp interface will be configured. In some rare cases
the provider may supply only one of the required IP addresses
(usually the local address). In this case the Remote or
Destination IP address can be entered in the "Destination IP
Address" field on page 2 of the provider dialog.