|
Sprache |
 |
|
|
Nfl | Basics maanke |
[Back]
[Content]
[Next]
If you want to understand how a network is working you have to look into the basics. The most
simple network consists of a 'server' and a 'client'. The 'client' fetches data that the
'server' provides, generally speaking. The internet too is nothing but a (big) accummulation
of 'clients' and 'servers', with the 'clients' being our computers at home, used for 'going
internet'.
You should think over which machine will be server and which client before building up your
network. There are different programs to be installed on your machines, as the distinction applies
to the programs as well. There are always "server programs" and "client programs". You can
install both, client and server programs, on any of your machines, admittedly. This allows for
accesses in both directions. In the beginning you should install server programs on one machine and
client programs on the other. Most of the client programs are well known from internet access, like
CAB, aFTP, aMail, Fiffi and lots more.
Small example:
You have two computers, an Atari and a linux PC. You configure the linux PC as server and the Atari
as client. Now you can access the linux PC from your Atari by ftp for example. That is you run aFTP
on your Atari and fetch data from the linux PC. The other way round it is not possible to access your
Atari from the linux PC.
|
|
Nfl | Basics maanke | A so called protocol is needed for transfering data at all. It provides rules about how, when and
where a machine has to transfer data. The most widespread protocol is is the so called PPP (Point
to Point Protocol). It is available on almost any computer system, including Atari computers. There
are more protocols, but these are not widespread or obsolete or specific for certain computer systems,
like IPX/SPX for MS Windows or AppleTalk for Macintosh.
|
|
Nfl | Basics maanke | IP addresses are given in the notation xxx.xxx.xxx.xxx. Single computers attached to the network
(or internet) can directly be accessed by these addresses. Assigning of IP addresses to each computer in the
network often is an obstacle for network newbies - they can be assigned statically or dynamically.
I am considering static assignment only, as I do not know if dynamic assignment is possible on the Atari.
If you know more about this, please tell me.
In local networks (those that are not connected to the internet) IP addresses typically are chosen
from the 192.168 set, i.e. any IP address we use starts with these two numbers.
The following two numbers are arbitraryly chosen between 1 and 255. They specify the network and
the computer in that network.
Example:
192.168.1.1 is computer 1 in network 1, a second machine in the same network would be 192.168.1.2 f.ex.
With these two IP addresses one could uniquely direct communication to one of those two machines. Assume
the computer with the IP 192.168.1.1 runs an FTP server. You could access this computer from the second
one (IP 192.168.1.2) with the help of a FTP (client) application by connecting to IP 192.168.1.1.
Assume now that the second machine was assigned the IP 192.168. 2.2 (instead of 192.168. 1.2
as before). Accessing the first computer will not be possible without auxiliary means, since it is assigned
to another network now. In this case you would need a router to mediate between the
two networks (1 and 2).
|
|
Nfl | Basics maanke | There are several services, that you can "teach" your server. This is a small list of the most relevant
and best known server programs:
| Service |
Program |
Function |
MiNT port |
| http |
apache |
provides a web server |
yes |
| ftp |
in.ftpd |
provides an FTP (File Transfer Protocol) server |
yes |
| telnet |
in.telnetd |
allows for working on/controlling your computer from a remote computer. |
yes |
| nfs |
rpc.mountd, rpc.nfsd |
allows for including parts of your computers file system into remote computers file systems. |
yes |
There are many more, but these are enough for the beginning.
|
|
Nfl | Basics maanke | Well, it depends... :) You have a network interface card? Then you need a driver for this card. There is
some freeware and some is not for free. If you received your network card from the friendly Atari dealer
(are there any left at all? :-)) the corresponding driver should be included. The driver must be copied
into the MiNT folder. Do you want to connect via serial interface? Then you need a zero-modem cable. You can
buy it from a PC dealer or tinker it by yourself. Now you need the so called ppp daemon. This program is
included in EasyMiNT, you have to install the NET.TAR.
To use your Atari as a server you need some additional rpm packets, which are not included in EasyMiNT. Just
choose what you need:
- inetd-0.17-5.m68kmint.rpm
- ftp-server-0.4-1.m68kmint.rpm
- telnet-server-0.1-1.m68kmint.rpm
- apache-1.3.14-1.m68kmint.rpm
- nfs-server-2.2beta47-1.m68kmint.rpm
[Back]
[Content]
[Next]
|
|
|
|
All pictures made with
Best viewed with
|
