wwwpaket.txt
How to setup your WWW server in tcpip packet radio.

This text file "wwwpaket.txt" will tell you how to setup your own WWW server on
packet after you have implemented the contents of "iakpaket.txt". By that time
you are an expert in tcpip networking and you can do this in minutes. This file
will include some general tips how to setup this whole system.

Before you can setup your WWW server, your Internet Access Kit has to work on
packet. Obtain a WWW server for your platform, either Windows or OS/2 Warp
Connect. It shouldn't be to difficult to find a free one for non commercial 
use. I use GOSERVE for OS/2. Install and start the WWW server and you are on 
air! It's that simple.

There is however one last problem you will have to solve. Anyone who wants to 
connect to your WWW server will have to add it's route in HIS/HER autoexec.nos,
using YOUR NOS address as a gateway. Something like the following examples:
route add <your-www-ipaddress> <their-radio-interface> <your-nos-ipaddress>
route add 44.98.24.57 tnc 44.98.24.52
route add www.ke4hsa 2m ke4hsa    (Their domain.txt should be up to date here).

You can test your WWW server setup as follows. First internally, you can use 
your own WWW browser and connect to your own server. (You should have some 
index.htm sample file in your WWWDATA directory to get something on screen). If 
this doesn't work you should check if your WWW host address is included in your
"hosts" file and your routing. 

If this works you ask a nearby tcpip packet station to add the route and 
gateway and make a telnet 80 connect as follows: 
telnet <your-www-ipaddress> 80. For example telnet 44.98.24.57 80 (The 80 will 
allow telnet to connect to the socket of WWW)

He should get a connect confirmation and further nothing. Ask him to type for 
example a ? and enter, wait about one minute and enter again. At that point his
station should receive an error message in html format, which is proof that it
works. (Different WWW servers on different platforms may work different in this
testing procedure. As long as you get the connect you are pretty safe it works).

From this point on you are on air with your WWW server, available for any NOS 
station within reach after it has added your route. Now you can propose them to
do some work setting up their system using the Internet Access Kit on packet.
In the meantime you can learn about HTML programming and create a nice WWW home 
page. You may add any available server to your desktop, however for security 
reasons I would advise to stick to the ones already available in your NOS 
software.

Following are some considerations and help.

To set this all up my only reference was NOSintro by Ian Wade, help files and
reference libraries already available on my desktop. I have no technical back 
ground. So if I can do it everybody can do it. But buy a good book first.

Some notes about the setup:

Your starting point must be a perfect working copy of NOS software.
When you start to built your network check and double check any and all 
interfaces: LAN cards, com ports or slip drivers. Be always 100% sure that all 
connections work, before going to the next step. When you have your network up,
start trace in NOS and if needed in OS/2 or Windows 95. Ping will be your guide
from this point on setting up your routing. Packets from your desktop have to 
go out your radio port in NOS and vice versa. Trace will actually show those 
packets as well as the ping command.

Every setup needs its unique routing so you are very much alone now setting 
this up. Don't forget to include any and all hosts that you want to allow 
connections in both your "hosts" file and your routing setup, including 
yourself. If one station can connect and another can't, that's where you have
to look.

Your routing and your network will work if you successfully can do the 
following:
- Ping from your desktop to your slip or LAN port address in NOS and 
- ping from NOS to your desktop.
(In NOS itself all radio packets must be routed by default over the radio port,
all others are routed over your slip or lan port)
- and ping to and from a nearby NOS station to and from your NOS and your 
  desktop.

Ultimately you can check it all on your own by asking permission to a nearby 
NOS station to use it as a gateway for telnet connections from your NOS and/or
desktop to them and back to your WWW server address. This way you have 
everything in your own hands at any time.

Some considerations about the setup you choose and the hardware you need.

For starters I would recommend to use slip over com ports. The only hardware
you may have to buy is a 0-modem cable. Later you can always upgrade to LAN 
cards. If you can use fast UARTS for your com ports.

To login to a WWW server and use your desktop features for packet, the setup as
described in QST of July 1995 will do with Windows 3.1. I bet that Windows 95 
will allow an even easier setup by just adding the ETHRAX25 package. Who can 
find this out and let us all know? This setup uses freeware only.

If you want to have your own WWW server you may have no choice but start 
networking. Especially NOS BBS sysops have an opportunity here to add a 
WWW server to their existing NOS BBS. 

If you want to start networking you may demand a high CPU speed and lots of
memory. If you will actually use a networked PC with OS/2 Warp Connect or 
Windows 95 I recommend a minimum of 486-50 MHz and 12 megs of RAM. More
of both will make you probably even happier. If you use a PC as a server only
you may do with less and the desktop will hardly move. The server may work
however.

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/95 

* 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.
