AmiTCP is available commercially from NSDi, a demonstration version (4.0) is available for free. Unfortunately, setup is quite different between version 4.0 and 4.3.
AmiTCP is also one of the more expensive TCP/IP programs for the Amiga. Miami and Termite are cheaper alternatives, in particular, Miami is shareware. Initial versions of Miami and Termite did not support server programs (such as POP and SMTP servers). This feature was promised for Miami, and I have heard that people have used Miami succesfully to communicate with their Newton.
AmiTCP needs to started with the SRV option. This starts up the 'super server' program inetd, which then allows other server programs to be run. It also sets up the loopback device, which then allows the Amiga to 'find' itself.
For example, my file "Amitcp:Start AmiTCP" looks like this...
Then you need to setup AmiTCP. This means altering the AmiTCP:db/provider.conf file. Unfortunately, AmiTCP is rather inflexible in that it does not support multiple configurations particularly easily. At the end of the day, I have several provider.conf files (provider.conf.onaustralia, provider.conf.newton) which I copy to provider.conf when I want to connect either to my Internet Service Provider (onaustralia) or Newton.
Here is the contents of my provider.conf.newton...
/* Provider Configuration Follows: Name Other DialUp 0 Interface ppp InterfaceConfig "BROKENHDLC" NeedSerial 1 IPDynamic 0 IPAddr 192.168.1.65 DestIP Gateway Netmask NSDynamic 0 UseBootP 0 MTU 576 Phone */
I might as well discuss the above file...
The following line must be in amitcp:db/autointerfaces...AmiTCP 4.3's own setup program does not create the ppp line properly...not when I tried anyway! By the way, the following line must be all one line in the autointerfaces file. I only use a serial line speed of 19200 bps. I am told 34000 (or thereabouts) works as well. I have not tested that speed.
NEW - version 2.0 of Newton Internet Enabler (NIE) allows you to set the bps rate of the Newton. NIE's default is 9600, but 19200 works well for me!
ppp DEV=DEVS:Networks/ppp.device UNIT=0 DoOffline ConfigFileName=ENV:Sana2/ppp0.config ConfigFileContents="serial.device 0 19200 0.0.0.0 7Wire BADXONXOFF MTU=576"
New note...a previous version of this documentation said that only 9600 bps works. Then Markus Lamers reported only having success with 19200 bps. Looking at my autointerfaces file, I noticed I had also set the speed at 19200 bps, although the speed listed in my envarc:sana2/ppp0.config file was 9600 bps. However, once I had started AmiTCP, env:sana2/ppp0.config contained...
serial.device 0 19200 0.0.0.0 7Wire BADXONXOFF MTU=576 BROKENHDLC
The amitcp:db/hosts file must be altered. This file is used by AmiTCP's own nameserver. Here are the two lines I added. As you can see, I let the Amiga call itself by many names, including localhost...
192.168.1.65 amiga.home.org.au mail.home.org.au news.home.org.au localhost 192.168.1.66 newton.home.org.au
You must also make sure that a Newton user will have access to the inetd
host. Check the file amitcp:db/inet.access. By default, inet.access has a line
which allows anyone to access anything.
LOG requests that all
attempted accesses should be reported (it will be displayed in a window)
* *.*.*.* allow LOG
Some lines need to be added to amitcp:db/inetd.conf for UMS's benefit. I think these lines might be added by UMSrfc's installer, but I am not sure. Please note that I assigned UMS: to UMS's directory, none of the installer programs actually did this for me (or I did not run the right ones!). The smtp/pop3/nntp programs mentioned below are servers, they store and serve mail.
ums stream tcp nowait root AmiTCP:serv/umsd umsd default umstest stream tcp nowait root AmiTCP:serv/umsd umsd test smtp stream tcp nowait root UMS:Bin/umssmtpd umssmtpd pop3 stream tcp nowait root UMS:Bin/umspop3d umspop3d nntp stream tcp nowait root UMS:Bin/umsnntpd umsnntpdIf you use the popper/InternetUtils combination, you only need to add the following line...
pop stream tcp nowait root AmiTCP:serv/popper popper
As far as I know, AmiTCP 4.3 shouldn't really require a ppp1_45 definition in AmiTCP:db/interfaces. Anyway, I have these lines in 'interfaces'. The line starting with 'ppp0' should all be one line.
# # PPP device by Holger Kruse # ppp0 DEV=DEVS:Networks/ppp.device UNIT=0 IPTYPE=33 NOARP P2P IPREQ=8 WRITEREQ=8
The nameserver which the Newton will access (not the one the Amiga will use itself) needs a file amitcp:db/named.hosts. Here are the lines which I added...
localhost. IN A 127.1 amiga IN A 192.168.1.65 newton IN A 192.168.1.66
Here is my amitcp:db/resolv.conf file. 'tmns.net.au' and the first two NAMESERVER entries are related to my internet service provider (ISP). 'home.org.au' is the domain name of my 'two machine network', the two computers being amiga.home.org.au and newton.home.org.au. Nameserver 127.0.0.1 is the localhost, i.e. the amiga.
; This file is built dynamically - do not edit ; Name Servers ; Search Domain DOMAIN tmns.net.au DOMAIN home.org.au ; NAMESERVER 22.214.171.124 NAMESERVER 126.96.36.199 NAMESERVER 127.0.0.1 ;
amitcp:db/services must contain references to pop/pop3 and smtp. This should be in 'services' by default. One of the UMS set-up programs modified my amitcp:db/services. The following lines were added AFTER the EOF marker. It might not be necessary at all...but if you are using UMS (rather than popper/InternetUtils)...
# ums 5555/tcp umstest 5556/tcp #
Here is what I have in amitcp:db/User-Startnet. It runs the nameserver which is available to the Newton. Running 'named' without re-direction results in the first window openned by AmiTCP will not close. Redirecting both to and from nil: results in an inability to exit 'named', and so AmiTCP will refuse to stop!
run >"con://320/100/NameServer Report/AUTO/CLOSE/WAIT" AmiTCP:serv/named
If use use InternetUtils, you may want to add a line to automatically run the SMTP server, since it is NOT automatically started by inetd. The example script was called `StartSMTPd', and documentation is provided with InternetUtils.
If you use popper/InternetUtils, you will need to set the user password through the AmiTCP setup program. Popper will use AmiTCP's amitcp:db/passwd file, which stores the password in encrypted format. By the way, the password needs to be of a reasonable length, longer than `taco' - try `Tacobill' for example!
Back to homepage
Last modified 21st June 2000.