The setup string above, at&f2, works for most Hayes modems. If you
have a USR modem try at&f1. If in doubt check your modem's manual
for a setup string that turns on data compression, error
correction, and hardware (RTS/CTS) flow control.


The next thing you need is a batch file to run ppp.exe. Edit the
sample batch filed called dial.bat to match your system
requirements.

First you need a login script. The login script must be in the
file called dial.ppp. Here is an example script:

DIAL.PPP:

send "at&f2\r" ;select factory default settings
recv 3000 "OK\r\n" ;wait 3 seconds for OK response from modem
send "atdt1234567\r" ;dial your provider; the \r is for RETURN
recv 60000 "login:" ;wait 60 seconds for login prompt
send "\r" ;send your username and RETURN
recv 10000 "Password:" ;wait 1 second for password prompt
send "\r" ;send your password and RETURN

Note: the login and password prompts much match those used by your
provider. If your host uses the prompt "Please login:" you can get
away with telling ppp to look for just "login:". Be very careful
that you use the EXACT same spelling, capitalization, and spacing
that your host's prompt uses. If your host uses "login :" and you
put "login:" in dial.ppp (notice the missing space) the script will
never complete. For the password prompt be sure to match the
host's password prompt (or at least the last word or last few
letters of the prompt). For example, if your host's password
prompt is "Enter you Password:", you could put "Password:" in
dial.ppp. Something shorter like "word:" would also work. If you
changed the capitalization to "password:" the script would not
work.

If the script appears to stop after a certain prompt, there is
probably something wrong with your script. Be patient if it seems
to stop after the password prompt since there is usually a delay of
about 5-30 seconds before the host reports your ip# and ppp returns
to the DOS prompt.

CSLIPPER com1 vec=0x60 baud=57600

where com1 is the serial port to which your modem is connected,
0x60 is the interrupt vector the packet driver should use, and
57600 is the DTE baud rate (the baud rate between the computer and
the modem, not necessarily the speed at which the modem has
connected to the remote system). The packet driver will display a
signon message and load itself into memory.

Your SLIP packet driver is now loaded and ready for testing.

Using Kali with a PPP account and Merit's etherppp

Step 1: Using your favorite serial communications package, dial in
to your service provider, log in, and issue whatever commands are
required to change their terminal server to SLIP mode. How this is
done varies from service provider to service provider and is beyond
the scope of this document. Check with your service provider for
more details.

Once you have logged on and enabled SLIP mode, exit your
telecommunications software WITHOUT HANGING UP THE MODEM - this is
VERY IMPORTANT! Any telecommunications package worth the floppy on
which it comes will have a "save without hangup" command, or will
prompt you when you exit to ask whether it should hang up or not.

Change to the directory where you have installed your packet driver
and load it. An example command line for CSLIPPER is

This procedure assumes that you are using the cslipper SLIP driver
mentioned earlier. If you are using a different driver, you'll need
to change the commands which follow accordingly.

Step 0: Obtain Internet access from a service provider who allows
SLIP connections on their terminal server. A "shell account" (where
you log in to a remote UNIX host and type commands such as "telnet"
and "ftp") will require a SLIP emulator called SLiRP (read the
SLiRP section below before continuing). How to obtain this type of
service from such a provider is beyond the scope of this document.
Also, if you are using a Microsoft Windows-based SLIP or PPP
driver, such as Trumpet Winsock, you MUST obtain and install a DOS
SLIP or PPP driver on your machine. Kali will NOT work with
Windows drivers such as Trumpet or Cameleon. It will NOT work with
Windows 95 drivers or even work with DOS drivers in a Windows 95
DOS session. You will have to reboot in DOS mode.

SMC_WD 0x60 0x7 0x300 0xd800

where 0x60 is the packet driver interrupt, 0x7 is the IRQ setting
on the card, 0x300 is the I/O port base address, and 0xd800 is the
memory base address (NOTE: all numbers are in C-style HEX
notation). Don't worry if you don't understand what all this stuff
means - as long as you use the correct numbers, your packet driver
should work. NOTE: If your PC is currently part of a Novell
network (e.g. Netware, Netware Lite, Personal Netware) the
parameters you need can be found in a file called NET.CFG, usually
located in your \NOVELL, \NWLITE or \NWCLIENT subdirectories (along
with all the other drivers needed by Novell). Add the proper
command line to the AUTOEXEC.BAT for your Kali configuration so
that the packet driver will be loaded automatically whenever you
boot using the Kali partition.

When successfully loaded, the packet driver should give a sign on
message and report the ethernet address of your NIC when you load
it. Chances are that if your NIC has been functioning properly for
other tasks (e.g. as a node on a Novell network) then you'll have
no problems here. If not, or if there are any error or warning
messages, something is wrong (D'OHH!). One possibility is that one
of the settings on your NIC is in conflict with those of another
expansion card in your system. No two cards can have the same IRQ,
I/O port, or memory address settings, nor can the memory areas of
two cards overlap. Whatever the cause, you'll need to find and
correct the problem before continuing.

SLIP Setup Procedure

Step 1: Set up the packet driver. If you do not already have a
suitable packet driver installed on your machine, now is the time
to install one. Start by determining your ethernet card's IRQ
setting, it's base I/O port setting, and it's memory address
setting (if any). You should be able to determine this by looking
at the card itself and consulting the user manual. You'll need
some if not all of this information, depending upon which packet
driver you use and/or type of hardware you have (for example, some
IBM computers with theMicroChannel bus can determine the settings
on the card automatically without you having to supply them on the
packet driver command line). Unzip the appropriate driver from
Crynwr Packet Driver collection archive. In our example, the
packet driver is called SMC_WD.COM. By looking at the jumpers on
the card and consulting the manual, I determined that the card has
been set to IRQ 7, Base I/O port address 300h, and the base memory
address is at segment d800h. For this example, I have chosen to
use interrupt 60h for the packet driver. Packet drivers typically
operate on an interrupt in the range of 60h to 80h inclusive; since
nothing else in my sample system happens to be using the first
available interrupt (INT 60h), I chose that. Thus, to load my
packet driver, I use the command line