iakpaket.txt
Point @ Click Packet Radio by using your Internet Access Kit.

This can be the start of a new era in packet networking. Imagine making packet 
connections with ftp, telnet, etc.in graphics mode by clicking an icon. 
It's possible now! If you are familiar with tcpip networking it's not difficult
at all. Start using your Internet access kit for packet radio, that's what this
is all about.

The July 1995 issue of QST tells all about the setup of a Linux WWW server on
packet. Also it describes the setup of WWW client software with Windows 3.1. 
I bet the ETHRAX25 driver may do wonders with Windows 95.  Who can find this 
out and let us all know?

Following is my description of different setups, completely integrating the
OS/2 or Windows desktop for packet. It will allow you to use all the features
of your desktop for point & click packet radio. You will be able to make
connections clicking an icon, print or save at any time what you see on screen,
read text files on line, etc. You will use your Internet Access Kit for packet.
You will be able to connect to any WWW server on packet, if available.
NOS will remain your gateway to the packet radio network, running in the 
background. You can still use it any time you wish.
(To install your own WWW server on packet, please see wwwpaket.txt).

Various ways are possible, with one or two PC's, or in an existing tcpip LAN. 

Requirements.
- 1 PC          OS/2 Warp Connect and NOS (Preferably PMNOS), or
                Windows 3.11 with TCPIP or Windows 95 and NOS
                2 com ports available or two LAN cards
- 2 PC's        OS/2 Warp Connect on one and NOS on the other, or
                WfW 3.11 with tcpip or Windows 95 on one and NOS on the other.
                1 com port available in each PC or 1 LAN card each.
- LAN           OS/2 Warp Connect on 2 PC's and optional WfW3.11 or Windows 95 
                on other PC's in the LAN 
                (PM)NOS installed on your OS/2 workstation
                VModem in both OS/2 PC's. (No additional hardware required).

If you are not familiar with tcpip networking, a book like NOSintro from Ian 
Wade may help you start. If you are familiar with tcpip, please continue.

NOS is a network program, so is OS/2 Warp Connect, WfW 3.11 and Windows 95. 
TCPIP has to be the network protocol in all of them. 

If you have one PC (see above), you have here in fact two networks in 1 PC! 
OS/2 or Windows and NOS. You can integrate these 2 networks either by slip over
the 2 com ports (the most cost effective way) or the 2 LAN cards (the fastest 
way).

(NOTE: Windows 3.11 will need an extra driver to setup a slip interface on the
com port. The also needed Internet Access Kit should have the necessary slip
driver or use the LAN cards instead. OS/2 Warp Connect and Windows 95 have the 
slip interface and the Internet access kit included. A TCPIP kit for Windows 
3.11 is available for download from Microsoft's BBS. A Windows 3.11 add-on for
Windows 3.1 is readily available in stores only)

If you use currently a PC with OS/2 Warp Connect or Windows 3.11 or 95 and you
have an old 286 or 386 available you can network NOS also from the 286/386.
Again you can integrate the two network programs by slip over the com ports or
the LAN cards. This is probably the easiest and most visible way to handle your
setup. (I would use a 286-20MHz or a 386SX-25MHz or better).

In a LAN with OS/2 Warp Connect the possible configurations are endless. The 
bottom line is however, regardless your configuration, VModem will allow you 
to slip from OS/2 to NOS over the LAN and integrate the OS/2 desktop in tcpip 
packet networking. (VModem runs only one time in a PC, so you need a minimum 
of two. VModem is part of Ray Gwinn's SIO package). Other workstations in this 
LAN with WfW3.11 or Windows 95 will be automatically integrated too!

(NOTE: In a LAN with only Windows 3.11 or 95 you can do it too, using com ports
or adding LAN cards in 2 PC's. The equivalent of VMODEM doesn't exist for the
Windows platform).

To setup either one of these configurations requires a perfect working setup 
from your NOS software as a starting point. To setup all the connections 
requires at least an overall basic knowledge of tcpip networking. Setting up 
the routing was the most difficult part for me. Use ping and write down the 
routes that work. Ping will help you through this routing process.

I have a setup in a LAN with OS/2, VModem and PMNOS1.3 and auto-sense connect 
1200 and 9600 bd. OS/2 has a multitude of client software available. I still 
use PMNOS for all incoming connects and mail handling. For all outgoing 
connects I use PMTelnet and the included WEB browser for ftp connects. I have 
icons for my favorite tcpip packet stations. Connecting to your favorite 
packet station with the WEB browser in ftp mode will hold your breath. I make 
any connect by clicking an icon. Also in my LAN I have a WfW workstation that 
allows me to use Windows' version of telnet and ftp client from the desktop. 
(I am not familiar with the availability of other client software for WfW or 
Windows 95, or the use of Windows 95 in general).

In all outgoing connects from your desktop the ipaddress of that PC will show 
up on the airwaves. The encap interface of NOS should allow you to hide this 
originating ip address and show it's amp.org ip address instead. I haven't been 
able to setup this encap interface properly. Therefore you may need at least 
one more tcpip packet address for your desktop. I use a second now: WWW.<call>.

When you have any questions, let me know and I may be able to help. Bear in 
mind however that hardly ever two network setups will be the same, so outside 
help may be difficult to get in general. When it works for you, let me know! 
I'm curious if you share my opinion that this will be the future of packet 
radio. Maybe this will be an incentive for a more widespread use of 9600 bd 
packet, however in 1200 bd it works exactly as fast as in any other setup.

May the force be with you!
73's de ke4hsa / Erik

AX.25  hbbs       KE4HSA@N4CNW.#TPA.FL.US.NOAM
TCP/IP email      ke4hsa@n4cnw [44.98.24.20]
E-mail            eprins@ibm.net

9/24/1995

* newpaket.zip contains iakpaket.txt and wwwpaket.txt
* All trademarks are owned by their respective owners.
* Try at your own risk. If your brain melts during setup it's your problem.
* Many issues and security setup of your system are not addressed in this file.
* The file newpaket.zip can be freely distributed, but unchanged only.
