Subject: Amiga Networking Frequently Asked Questions (FAQ) Part 2/2
Date: 24 Dec 96 12:32:31 +0200
X-GateSoftware: AmiGate 1.6b (28.1.96)

Summary: Answers to both generic and Amiga specific networking questions.
  It covers both hardware and software questions. It should be read by anyone
  that has a network related question before posting it to 
  comp.sys.amiga.datacomm or comp.sys.amiga.hardware  news groups.

Archive-name: amiga/networking-faq/part2
Posting-Frequency: monthly
Version: 2.1

Document Amiga Networking FAQ


=======< start second part >=====


  AmiTCP   is a shareware product and a demo version is available on Aminet. AmiTCP
can be a bear to install, but now there are install scripts on Aminet, and I've
added a section to try to help demystify the process. AmiTCP will provide full
TCP/IP connectivity.

  DNET  may be more useful if you are connecting to a UNIX host, but I have no
direct experience with DNET.

IF all you can get is a shell account on the UNIX host, then    TIA    or   MLINK  
will be of interest.

Of course there are other options as well such as AmigaNOS.

 AM2 
--------------------

Is there a way to print from AMosaic using arexx?

Thanks to a Quick and Dirty Hack by Mike Meyer there is!

Although I tried to type it in correctly,  I cannot guarantee that it will work
since I have no way to test it.


 / *
 * A QAD hack to print from Mosaic via the Rexx interface
 */
 arg style
 if ~show('Libraries', 'rexxarplib.library') then
 if ~addlib('rexxarplib.library', 0, -30) then do
 say "No rexxarplib, so no posting!"
 exit
 end

 options results

 select
 when style = "TEXT" then 'get text'
 when style = "FORMATTED" then 'get formatted'
 when style = "POSTSCRIPT" then do
 call request 0, 0, "Postscript doesn't work yet!"
 exit
 end

 otherwise call request 0, 0, "Invalid argument" style
 end

 if ~open(printer, "prt:", "Write")  then do
 call request 0, 0, "Can't open printer!"
 exit
 end

 call writech printer, result
 exit

 AM3 
-------------------

Having problems with "service looping" with http?

There is a version of the AmiTCP 3.0 Beta 2 inetd which is better behaved. It is
available via anonymous FTP at remarque.berkeley.edu  as /pub/mwm/inetd_for_httpd

 AM4 
--------------------

How do I connect to a news server with AMosaic?

You specify the NNTPSERVER environment variable. This can be  done at user-startup
or from a shell.  Use the setenv command:

  SETENV NNTPSERVER a.news.server.youre.allowed.on

 AM5 
-------------------

How do I access docs in AMosaic NoNet mode?

The Amosaic NoNet version  can run in stand alone mode ( i.e. NO NETwork). This is
for testing purposes before you get your network connection.  In v1.2 or earlier
you are greeted with an error message instead of a document in this NoNet mode.

To see the local html files you must use the Open Local menu item and then choose
volumes.  You must go all the way to the list of volumes because this allows you
to build the file pointer from scratch. Choose the volume where Amosaic is stored
and then work your way  down to the docs/html directory. There should be a file
called index.html. Choose it and it should open. Once you open the index.html file
it has hypertext links to many of the other local html documents. It also has
remote links which obviously won't work in NoNet mode.

To make index.html your default or "home page" you can edit the
envarc:mosaic/prefs and set the HomeDocument variable. For example:

 HomeDocument file://localhost/SYS:Comms/Mosaic/HTML/index.html


The change will be active the next time you boot or To make it active copy the
envarc:mosaic/prefs to env:mosaic/prefs.

 AM6 
-------------------

How do I make AMosaic appear on a custom screen?

You can make AMosaic appear on a custom screen by using the MUI Prefs, BUT don't
do it while Amosaic is running!!!

If AMosaic is running when you change the MUI prefs to a custom screen, it will
crash your machine! ( At least V1.2 of Amosaic did this, other versions may be
fixed)

Simple fix: Run MUI prefs and change the screen, and THEN run AMosaic.

 AM7 
--------------------

How do I change AMosaic's preferences?

In order to change AMosaic's preferences such as which page is the default home
page you can edit one of the files in the envarc:mosaic  directory, or you can get
AMprefs which is available on the AMosaic home page.

For more help get the   Amosaic-FAQ  

 AM8 
------------

AM8  How to route past FireWalls? (proxies)


Version 1.3 of AMosaic and higher supports proxies so that you can talk through a
firewall router. To do so you must set some environment variables on the Amiga.
Here is a list that Stefan posted:

open a shell window and type:

 Setenv HTTP_PROXY   http://proxy.domain.foo.bar/

 Setenv ftp_PROXY    http://proxy.domain.foo.bar/

 Setenv gopher_PROXY http://proxy.domain.foo.bar/

 Setenv wais_PROXY   http://proxy.domain.foo.bar/


where proxy.domain.foo.bar should be replaced by the domain name of your WWW proxy
gateway.

See the AMosaic FAQ for more help hints and up to date info. It is located at
http://www.phone.net/atcpfaq/amosaic.html

 AmiTCP(AT) 
--------------------------


The first two questions were triggered by 3.0b2 which should no longer be used.
Version 4.0 demo of AmiTCP has been officially released to   Aminet  . Although it
is a "demo", it is fully functional. There will be a commercial version of AmiTCP
available with new features.

NOTE:  Do not install v4.0 over a non-working version of 3.0b2. Delete all the
3.0b2 files off the system (i.e. wipe the slate clean).



Questions about AmiTCP

   AT01   Telnet in 3.0b2 locks up my shell when I exit. Is this a bug?

   AT02   Startnet in 3.0b2 says there is "no such interface"  why?

   AT03   My provider assigns SLIP addresses dynamically. Now What?

   AT04   Where are the docs? How do I install and use AmitcP?

 AT01 
--------------------

Telnet in 3.0b2 locks up my shell when I exit. Is this a bug?

Yes, and is quite typical of BETA software. Remember beta software is still under
construction and has not been extensively tested. Bug reports and patches can be
found on kampi.hut.fi

Amitcp 3.0b2 telnet when used with AmigaDOS 3.0 or 3.1 uncovered a  bug in the
console software. 

Solution is to either 

A) use the telnet from 2.3 of AmiTCP or 

B) use a console handler like KingCON which is available on   Aminet  

C) get a "fixed" version of telnet from kampi.hut.fi

 AT02 
--------------------

Startnet in 3.0b2 says there is "no such interface"  why?

Because you failed to read the NOTE to BETA testers. This is BETA software; so you
ARE a Beta tester. BETA software is still under construction and therefore so are
the manuals and the install script.

There are some postscript manuals available for AmiTCP 2.x   The 3.0 stuff hasn't
been added to the postscript manuals yet, so the postscript docs aren't in the 3.0
archive, but they are available online at kampi.hut.fi and other places.

To fix the "no such interface" problem you must edit two files:
amitcp:db/interfaces and amitcp:bin/startnet.

In amitcp:bin/startnet you must change the ifconfig commands so that instead of
file name/interface number

  devs:network/a2065.device/0

you have 

  alias0   

where alias is defined by you in the interfaces file.

Some predefined aliases are already in the interfaces file. In fact the
a2065.device is defined as ether.  Therefore you could have changed  the above to
ether0 in startnet and not had to change the interface file.

Also, you must change the lo/0 to lo0 in the startnet file because the slash
between the name and the unit number has been dropped and  will generate an error
if you include it.

 AT03 
--------------------

My provider assigns SLIP addresses dynamically. Now What?

Now you have an excuse to learn arexx or shell scripts.  ;-)

Actually some have already been written and posted.  Here is one way to do it.
(NOTE: I HAVE NO WAY TO TEST THIS  PROGRAM SO USE IT AT YOUR OWN RISK ) In fact,
it will NOT work as is. You MUST modify it for your system.

 /*REXX*/
 /* go slip! a program to create slip scripts with dynamic address */
 /* usage   rx goslip.rexx <dynamic ip address> */

 option results

 trace off

 If = '0a'x
 address REQUESTSTRING 'rtitle="GoSlip" text="Please enter your IP 
 address." '
 direccion = result
 /* changed from 19200 */
 outdriver = 'baudbandit.device 0 57600 ' || direccion ' CD 7WIRE'
 say outdriver
 foo = open('outfile','ENV:sana2/rhslip0.config','Write')
 foo = writeln('outfile',outdriver)
 call close 'outfile'
 address REQUESTSTRING 'rtitle="GoSlip" text="Please enter your 
 host name.(slip#, w/ out amiga.com)" '
 trob = result
 gene = 'HOST 128.200.142.228 ' || trob || lf || 'DOMAIN amiga.com' || lf

 ||'NAMESERVER 128.200.192.202' || lf || 
 'NAMESERVER128.200.1.201'
 foo = open('outfile','amitcp:db/netdb-myhost','Write')
 foo = writeln('outfile',gene)
 call close 'outfile'

 address command
 'run >NIL: AmiTCP:AmiTCP'
 WaitForPort AMITCP
 'AmiTCP:bin/ifconfig lo0 localhost'
 'AmiTCP:bin/ifconfig slip0' direccion '128.200.1.201'
 'AmiTCP:bin/route add' direccion 'localhost'
 'AmiTCP:bin/route add default 128.200.1.201'
 'Assign TCP: Exists > NIL:'
 /* 'if warn' */
 'Mount TCP: from AmiTCP:devs/inet-mountlist'
 /* 'endif' */
 'run >NIL: amitcp:bin/inetd'
 /*----------end of script ---------------*/

 AT04 
-------------------------

Where are the AmiTCP Docs? How do I install and use AmiTCP?

The quality and lack of docs is a weakness in the demo version, but hey it is
free. There are docs included with the registered version.

The most important doc is "Howtoinstall". It is in the Amitcp: drawer. PRINT IT,
and MEMORIZE IT ;-} Seriously though, do read it and gather the necessary info.

If your network provider is using SLIP, then you have all software you need to get
AmiTCP up and running. If your provider uses PPP, then you will need to get a copy
of PPP.device which is shareware and is available on Aminet.

Also there are some docs in the amitcp:doc and amitcp:help drawers. There isn't
any real organization to them, but look at them anyway. Some of the terms are
described in the generic section of this FAQ, and it is good background if you
know little or nothing about networks.

To get started you do NOT need a dialing script. Just use a standard modem program
such as jrcomm, Termite, term, handshake, etc. A dialing script is a form of
automation. It assumes you've got things working and merely want to automate the
process. So wait until you get AmiTCP to work before attempting to set up a
dialing script.

Even if you have dynamic addresses from your provider (i.e. the address for your
machine changes each time you log in) you still do NOT have to have an automated
dialing script for testing AmiTCP. Save that for later.

So here is how installation goes in a nutshell:

  * print and read the amitcp:HowToInstall document
  * gather the info about your connection
  * install AmiTCP using the installer script

Now that AmiTCP is installed here is how to test and use it:

 ----------<!! IMPORTANT STEP Follows !!>-------------------

*Setup your terminal program to use the same baud rate as AmiTCP. If the baud rate
is different AmiTCP will NOT work!  This is an easy step to overlook so watch
out.

   Hint: You can change the baud rate AmiTCP uses by editing the
         amitcp:bin/startnet script.

 -----------------------------------------------------------

*start your terminal program such as term, ncomm, or Termite or you can use a
dialing script. Some of the dialing scripts require programming others have user
interfaces. Go with what is easiest for you. I say for testing purposes that a
term program is the easiest.

*Setup your terminal program's modem predial string to be ATZAT&D0/r (this will
reset the modem and force it to ignore DTR) If your terminal program does not use
a predial string, then simply enter the command AT&D0 so that the modem will
ignore DTR. 

*Use your terminal program to make the connection to your provider

*Manually log in and take note of the prompts and messages. When you write the
automated dialing script it will use these prompts as cues.


*Some providers will automatically start SLIP others require you to issue a
command. You'll have to follow their instructions here.

*if you have a dynamic address the host should provide it to you at this point.
Since we are doing things manually, you will need to write the address down for
use in a later step.

*Once SLIP mode is entered, QUIT the term program. (this is where ignore DTR is
critical. You don't want the modem to hang up because we are going to turn the
serial port over to AmiTCP next).

*In a shell window type "startnet" for static addresses or "startnet
your.dynamic.address" if you have a dynamic address (hint: use the one you wrote
down in the previous step)

*if everything goes right you should get a banner which makes you click on OK
after a period of a few seconds. Then you should be returned to the shell prompt.
Do NOT close the shell. Shrink it and move it out of the way. AmiTCP is now
running. Having fun yet?

Not very exciting Huh? Well AmiTCP doesn't do anything for you directly. You must
run an application which uses AmiTCP in order to accomplish anything. The great
thing about AmiTCP and your multitasking Amiga is that you can run a bunch of
these applications at the same time over one modem connection all talking to
_different_ hosts if you wish. Now it is beginning to get interesting, huh?

So what are these applications? and how can you tell if AmiTCP is working?
Patience, we are almost there. Remember those amitcp:doc files I asked you to look
at? These describe some of the applications. Among them is a tool called PING
which allows you to test your connection. Try it against your dial up host. Should
work pretty fast, and instantly verifies your connection and setup.  Now try it
against a remote host such as www.microsoft.com. If it works, this verifies your
name server lookup is functioning as well as proves you are on the internet. If it
doesn't, don't panic. Check for typos in your config files. Things like a
transposed number in the default gateway address would cause the network to be
invisible. Also, check that baud rate!

If ping works you can move on to more fun things like ncftp for file transfers or
telnet for terminal access to your shell account (gotta check that mail).

If all this is working for you, It is time to dive into automating that dial up
process. Then it is on to Amosaic (provided you have WB3.x and MUI), news readers,
mail, etc., etc.

See, now that wasn't so bad was it. ;-}

 Software-bycat 
------------


Software by Category (some items include both hardware and software) (some items
are discontinued but listed for those buying used stuff)

 -----------

 Protocols:

  Appletalk

    AMAX
    EMPlant
    DoubleTalk

  Decnet

      DECnet  

  TCP-IP

      AmigaNOS  
      AmiTCP  
      AS225  
      INet 225  
      Miami  
      TermiteTCP  

  Novell

      Oxxi  

  Other

      AmigaUUCP  
      DNET  
      ENLAN DFS  
      ENVOY  
      Link-It  
      Parnet/Parbench  
      SAMBA  

 -------------

 Disk Utils:

    CrossMac  
    MaxDOS  


 ------------


 TCP-IP Utils:

    MLINK  
    TELser  
    TorqueWare  
    netser.device  


 SANA II device drivers:

    PPP.device  
    PLIP  
  SanaUtil
  SanaMon

 X-windows:

    Amiwin  
    X11  


 Email:

  AEmail
  ADmail
    AmigaELM  
    INetUtils  
    MunPack    MIME decoder
    THOR  
    Voodoo  


 Gopher:

  BBGopher (aminet)
  Goppher (aminet)

 Web browsers:

    Amosaic  
    IBrowse  
    AWeb II  
  Voyager

 Web editors:

    HTML-Heaven  
    Heddley  
 
 News:

    GRn  
    Offline-Orbit  
    THOR  
    TIN  

 IRC:

  Grapevine


 --------

 Terminal emulation:

    Handshake  
    Ncomm  
    Termite  
    Term  
  Terminus (JRComm 102)
    VLT  

 ----<end of list>----

 hardware-bycat 
----------


Hardware Listed by Category:



 Ethernet cards:

    A2065  
    A4066  
    Ariadne  
    Hydra  
    ICard  
    LAN Rover  



 ISDN:

    ISDN-MASTER  



 Other:

    Amigalink  
    GG2-Bus+ Card  
    Quicknet  

 Software-Specs 
================

Specifications for Amiga Networking Software

This is not an exhaustive list. There are several good  web pages  that list even
more programs. Also, you should check out   Aminet   and   Fred Fish    for the latest
software. The news group   comp.sys.amiga.announce   is quite handy as well.

   AmigaELM  -- email

   AmigaNOSFlavors  -- protocols

   AmiTCP  -- TCP/IP protocol

   AmigaUUCP  -- UUCP protocol

   AmiWin   -- X-windows

   Amosaic  -- Web browser

   AS225  -- TCP/IP protocol

   CrossMac  -- Mac formated disk support

   DECnet  -- Decnet protocol

   DNET  -- protocol and file sharing

   ENLAN-DFS  -- protocol and resource sharing

   Envoy  -- protocol and resource sharing

   GPDial  -- dialing script for Amitcp

   GRn  -- NEWS reader

   HTML-Heaven   -- Web processor

   INet 225  -- TCP/IP Protocol

   INetUtils  -- support for news and mail

   Link It   -- Amiga-PC file sharing

   MaxDOS  -- Mac formated disk support

   Miami  -- TCPIP for modem users

   Mlink  -- TCPIP for Shell users

   MunPack  -- MIME and uuen/decode

   NCOMM  -- terminal emulation

   netser.device  -- remote serial port access

   Offline-Orbit  -- NEWS/BBS reader

   Parnet  -- protocol and file sharing

   Plip   -- Parallel port device driver for TCP/IP

   PPP.device  -- device driver for PPP-TCP/IP

   SAMBA  -- protocol and file sharing (UNIX/PC/AMIGA)

   telser  -- allows modem terminals to be used with telnet

   Termite  -- terminal emulation

   TermiteTCP  -- TCPIP for modem users

   THOR  -- NEWS/BBS reader

   TIN  -- NEWS reader

   TorqueWare (TM)  -- Distributed Processing

   VLT  -- terminal emulation

   Voodoo  -- email with GUI and MIME

   X11R4  -- X-windows

 AmigaELM 
---------------------------

AmigaELM by Andreas M. Kirchwitz.

elm-fan@zikzak.in-berlin.de

AmigaELM is available on   AmiNET   in the /comm/mail directory.

AmigaELM is a shareware electronic mail utility for   UUCP   or TCP/IP that allows
you to read and post mail through a remote unix mail box. It can also be setup to
run without UUCP or IP on the Amiga. 

AmigaELM 8 (8.20) was just announced in   c.s.a.announce    Announcements are
archived on Aminet so I won't repeat the text here.

It works with MetaMail which is also on Aminet. MetaMail handles a lot  of
different   MIME   message types.

You should also pick up a copy of   INetUtils   from   Aminet .  It has  a   SMTP  
  client which is suppose to work with AmigaELM.

 AmigaNOSFlavors 
------------------------------------

AmigaNOS and AmigaNOSGW are Amiga ports of the PD TCP/IP  package for MS-DOS
called "ka9q". Note that there are MANY  versions of "ka9q" which tends to make
them somewhat unstable,  since they have so many variations.

AmigaNOS is a program that will allow one to participate in the Internet (or any
TCP/ IP network for that matter) via one of two dial-up TCP/IP protocols: SLIP or
PPP. It also works with HAM radio equipment.

Both programs are a single, integrated "package" of the required  TCP/IP protocols
(e.g.; TCP, IP, UDP, etc.) and some TCP/IP applications/commands (e.g.; Finger,
Telnet, Ping, SMTP). Though the required file structure may seem daunting at
first, it is actually simpler to set up than is AmiTCP.

Both AmigaNOS and AmigaNOSGW are very close in capability and  can be considered
equal, in general, for TCP/IP.   The main  differences between the two versions is
that Graham Walter's version,  AmigaNOSGW, comes with an external Gopher client
program and  has an ARexx port.


 AmigaNOS is by John Heaton  available by FTP from 130.88.200.4


 AmigaNOSGW is by Graham Walter available by FTP from newgate.demon.co.uk

 AmiTCP 
---------------------

AmiTCP by   NSDi  

Versions 2 to 3.0b2 of AmiTCP are GNU-ware  versions of   TCP-IP   for the Amiga. It
will work with SLIP or ethernet cards. For more details see the   AmiTCP FAQ  

Version 4.0 is now commercial. A demo version is available on    Aminet  . The
commercial version is available from the original authors  the Network Solutions
Development Inc. (  NSDi  ).  For ordering  information send an email message to
info@nsdi.fi which contains the  text "SEND AMITCP ORDER" in the body of the
message.


They also have a Web page

  http://www.nsdi.fi

AmiTCP can be a bear to install, so read the   Amitcp Install   question, and
Especially the   AmiTCP FAQ   written by Mike Meyer  and Neil McRae. Also you  can
find some install utilities on Aminet such as iiNST.

 AmigaUUCP 
--------------------------

AmigaUUCP is a port of Unix to Unix CoPy    UUCP   to the Amiga. It allows an Amiga
to participate in the USEnet network. It has it's own   UUCP FAQ  

There are actually several versions of UUCP for the Amiga. I've lumped it all here
to make it easier on me. As I sort it out I may divide it into more informative
nodes.

Parts of UUPC (a version of UUCP by John Gilmore) were ported to  the Amiga by
William P. Loftus in 1986. After developing a system that  worked for him, it was
taken over by Matthew Dillon, who (along with a  cast of dozens) developed it into
a full-fledged   UUCP   package. Matt maintained AmigaUUCP (often called DUUCP) from
1988 until 1992.

In 1992, Matt had the press of other obligations; and after the release of
AmigaUUCP v1.16, turned the buglists over to Michael B. Smith.  Michael is in the
process of releasing AmigaUUCP v1.17. v1.17beta  has been available freely for
some months (currently at update #4).

After Matt quit working on UUCP, Kai 'wusel' Siering also started on a version of
UUCP based on AmigaUUCP v1.15. It has most of  the v1.16 enhancements as well as
other features.

 AmiWin 
-------

AmiWin


A shareware   Xwindows   server for Amiga by Holger Kruse.

AmiWin is available on   Aminet .

Although I haven't used it myself, several kind folks on the net have provided
some input.

AmiWin works with both local and remote xclients.

Most notable among the remote clients supported is NetScape. Since X-windows is
slow, a 14.4k line is pretty much unusable for running a remote graphics intensive
client such as NetScape.


Most notable among the local clients supported is Chimera which is another web
browser. Chimera supports forms and inlined-images, but probably doesn't support
all of the Netscape-isms.

Chimera can be started from inside AmiWin by adding Chimera to the menu by
modifying the X11:lib/x11/twm/system.twmrc file. Add something like:

  menu "LocalClients"
  {
    "Chimera"  f.exec "Chimera.script"
    "XV"       f.exec "XV.script"
    "XClock"   f.exec "run >NIL: XClock"
  }

Where Chimera.script is a small script that sets up proper task priority, and
stack size for Chimera before running it.

For running local clients such as Chimera you should use the ppipc transport and
open -display "local:0"

 Amosaic 
--------------------


Amosaic is a freeware version for the Amiga  of NCSA's Mosaic. A hypertext based
multimedia interface for accessing the Internet.

AMosaic allows you to browse and retrieve files using a point and click interface.
With a single mouse click you can retrieve and view a text file, a picture, or an
MPEG movie. Or you can download the most  recent version of your favorite program
from one of the archive sites. Use one of the many search utilities, and ride the
wave of pointers to sites all around the globe! They don't call it the World Wide
Web (WWW) for nothing ;-)

Amosaic is available via FTP from max.physics.sunysb.edu or via Mosaic from the
Amiga home page by Witbrock. Amosaic is also available on   Aminet   in the
/comm/net directory.

It requires MUI,    AmiTCP   or   AS225r2    TCP-IP software, and  some  sort of
internet connection to access remote information.  Also due to datatypes it
currently requires AmigaDos 3.0  

See the product specific section   AMosaic(AM)   for more hints!

 AS225 
---------------------

AS225 by      Commodore Business Machines  

CBM only released version one which is known as AS225r1. It is listed here for
historical purposes.

AS225r2 is and will be released by third party developers.


AS225r1 Compatibility:  NFS - TCP/IP software for the Amiga is compatible with all
models of the Amiga.  Allows connection to Internet, DDN  and other networks
supporting TCP/IP and UDP/IP protocols. Works with the A2065 and Ameristar
Ethernet Adapters.

AS225r1 Network Functions: rlogin  (client only), rloginVT (client only VT100
terminal emulation), rsh (client and server, but no interactive shells),  NFS
client, telnet (client only), ftp (client and server), finger (client  only),
ping, arp, netstat, rcp (client and server), route, showmount  

  AS225r2  

 AS225r2 
