III. More Information on MiNT-Net

> MiNT-Net looks great but how is it supposed to be used? Does MintNet 
> actually provide a link between several Ataris? If so does use the serial 
> port or midi port? 

As of version 0.30 it does support linking Ataris with Ataris/Unix Boxes/whatev
stuff running IP software. 

For now SLIP (IP over serial lines) and PLIP (IP over parallel lines) is suppor
SLIP is compatible with (hopefully) all Unix SLIP implementations. PLIP is 
nonstandard, but much faster (> 15 kB/sec). 

> I realise that mint 1.10 needs to be patched to work - but what about 1.08? 
> I've tried MiNT 1.08 and I get the 'non patched MiNT 1.10' error message. 

Don't worry about the 1.10 in the message. It just means, that MintNet will not
with your version of Mint. 

> Finally I notice there is a fair bit of other stuff in the same directory 
> as net-030-tgz: >
> Mint/Network/ 
>  inetd-01.tgz 45 Pl1 of Internet Super Server.  Needs net-030.tgz 
>  net-030.tgz 321 Ver0.30 of MintNet, a networking extension w/BSD socket 
>  portlib-02.tgz 13 Pl2 of library software for porting unix stuff 
>  rpc-01.tgz 450 Pl1 of Sun RPC for Mint + MintNet 
>  term-1.08.tgz 244 A port of term for MiNT+net  
>  tftp-00.tgz 37 Pl0 of trivial ftp for Mint+MintNet 
>  tftpd-00.tgz 27 Pl0 of the tftp server program for MiNT+MiNTNet 
>  udpprobe.tgz 23 Prg for testing connectivity in M+MN.  Similar to ping 
> Is any of this other stuff necessary to start with, and does any 
> of it superceed the stuff in net-util.tgz? 

Some files (those with patchlevel > 0) superseed files in net-util.tgz. You sho
get at least inetd and udpprobe to have some stuff to test if MintNet is workin

If you think you have installed MintNet correctly, try the following: 

% inetd % udpprobe localhost daytime "i" 

The last command should give you the current time and date of your machine. 

> I haven't been able to build syslog from the init1.1 package - 
> but MiNT-Net seems to work without it. 

Mint-Net itself doesn't need it, only inetd, tftp and the other ported BSD sofw

> I'm having a bit of trouble with TFTP. After a lot of fiddling I 
> managed to GET a file between 2 directories. (I'm playing arround with 
> TFTPing between directories on 1 machine so I don't have to keep turning 
> on the spare ST ;-) 
> I can't get PUT to work however. I've tried dozens of combinations of: 
> put   
> both with and without "localhost:" infront, but no luck. I get "Error X: 
> File not found" or similar. 
> BTW I'm doing all of this between directories on the U drive. The 
> destination dirctory is a MINIX-FS one, while the source is /bin where TFTP 
> lives. Any ideas? 

First, tftp allows you only to `put' files which already EXIST at the destinati
machine and are WRITEABLE by the world. Eg. 

put some.file.tar.z remote:/tmp/xyz.tar.z 

will only work if the file 


already exists and looks like 


This stupid behavior is because of missing authentification methods in the tftp
protocol, ie the tftp daemon doesn't know who is putting the file. 

> Also I don't understand the entry in inetd.con: 
> tftp dgram udp wait root /usr/etc/tftpd tftpd 
>                                         ^^^^^ 

This is the first argument to /usr/ets/tftpd (The one you can access as argv[0]
 -- the 
name of the executing program -- in main() if you are familiar with C). You mus
always give it. You can give tftpd further arguments by writing them after the 
`tftpd'. If you do so, access is restricted to the directories they specify. Eg

tftp dgram udp wait root /usr/etc/tftpd tftpd /tmp/ 

restricts tftp `put' to the /tmp/ directory. 

> Is 'proper' FTP going to be available at some time? TFTP is fine - but 
> there is very little I can connect to with it ;-) 

This requires to implement the TCP protocol in MintNet. I'm working on it. But 
guess in some days Ulrich Kuehn's NFS will be available. It is quite stable now
and will give you lots of fun :) 

> Also although:
> udpprobe localhost .... 
> works. Trying: 
> udpprobe  ..... 

For the latter to work you have to do several things: 

Write your hosts's name into /etc/hostname (suppose `larry'). 

Choose an IP address for it (suppose 

Add the line larry to /etc/hosts. 

Add the line nameserver to /etc/resolv.conf if it doen't exist. 

Do an ifconfig lo0 addr route add lo0 at startup. 

Then you will be able to access your local machine both as `larry' and `localho

But when doing the above with MintNet 0.30 you won't be able to access your 
machine as `localhost` any longer. This is fixed in 0.31. 

As a temporary solution you could make your hosts name an alias for `localhost'
by adding `larry' to the line in /etc/hosts: localhost loopback larry 

> CAn't seem to format the manual pages. nroff -man  doesn't seem 
> to work. 

You need groff and the tmac.doc macro package to format them: 

groff -mdoc -Tascii filename > filename.formatted 

should work. 

> Any idea where I can ftp groff from? 

try a.a.u.e:/atari/Mint/Utilities/groff* 

> I'm not too up on internet addressing but the setting up of localhost 
> confused me slightly: 
> /etc/ifconfig lo0 addr up 
> /etc/route add lo0 
> Is is right that in the first line the address is and in the 
> second 

As you probably already know an Internet address consists of a host part and a 
Network part. For the class A address 127 is the network part and 0.0
is the host part. The host address with the host part all zero is the address o
f the 

So the second command adds a route for the Network 127, that is for all hosts i
the Network 127. This is necessary so that broadcasts (an IP address with the 
host part all 1's, ie for the loopback net). will get routed to
localhost interface too. 

Adding a route to the Network (ie with the host part of the IP address all zero
) is 
indeed necessary for all non point-to-point interfaces that support broadcasts.

So the above commands are perfectly right.  

> I seem to be able to use either address as a loopback address. 

That is because is threatet as a broadcast address too. You probably 
should be able to use 127.x.y.z where x, y, z are numbers in between 1 and 254 
you issue the above commands. 

(Info on FSP client)

From: tj@aiscube.AIS-dortmund.de (Theo Janssen)
Newsgroups: comp.sys.atari.st.tech
Subject: FSP (WAS: Mosaic/WWW ??)
Date: 21 Apr 1994 09:51:19 GMT
Summary: a substitute for ftp
Hello "MiNT-netters"

Obviously, there has been some porting of Net-Software, now as MiNT-Net
becomes more and more popular. For those, who are interested, i've
compiled the fspclient source with no bigger problems.  FSP is an
"UDP-based FTP", and is a lot like his TCP-based brother.  There are  a
couple of sites, which support FSP (i.e. ftp.germany.eu.net,
src.doc.ic.ac.uk, tu-clausthal, wuarchive and a lot more). I already 
transferred a lot of files via SLIP using this tool and it worked fine.

I'm also working on a fspd. As soon as i have a stable (rigth word ?) version,
i'll let you know and send it to the Net.

You now can get the package using ftp or E-Mail or fsp (PORT 2001) :-) from 
"ftp.germany.eu.net" (pub/comp/atari-st/mint/fspclient.tgz)

       good luck   Theo

>So what's the scoop on MiNT NET 4? 

Well I ftped MiNT-Net 0.4 from uni-paderborn last night. It had only been
up there a few hours when I got (I think).

I've only had it running for a little time, as it comes with a patch for
MiNT 1.10, so I had to recompile that first. Which wouldn't be problem if my
GCC hadn't packed up. Lucky I backed it all up last week!

Anyway so far its much the same, but as the .XDD file has grown from 50K
to 80K I suspect its much more developed. Seems to work with Ulrich's NFS
as well as 0.3 did.


It's not just 30k "bigger" In this 30k you'll find TCP-Support. That
means you can now compile and run most TCP/IP Clients. I already
compiled ftp, ftpd, finger, fingerd. After I received MiNT-Net 0.4
i did a 2 hrs. lasting WWW-Session with Bart Schulers "lynx" Port. I
really enjoyed it, doing this with my Mega-4.
I think there will be a lot of new Internet-Tools in the near future.
There were rumours that some people are working on a GEM-based WWW-Client.
So, if you have an Atari and a SLIP-Account, just hold the line ;-) !

      cheerio  Theo

>Installing Finger

After i received a lot of mails on how to install the finger-tools, here
are the most important points to watch out for:

- do not try to start the fingerd in rc.net! it has to be started by
  inetd. Look into "etc/inetd.conf" and read the MiNT-Net Documents.

- If your "finger" is not in /usr/bin, make a copy or a link, so that
  /usr/bin/finger is existent. Otherwise your machine will not send out
  any infos (fingerd calls "/usr/bin/finger")

- and PLEASE, PLEASE, don't send me more mails on what finger is, and
  what it does, and how to use it .......

  Believe me, threre are a lot of books, which describe daemons, tools
  and basics of Internetworking.

          cheerio   Theo


: What worries me is that I just can't get 2 machines running 0.4 to talk
: to each other, or even one with 0.3 and one with 0.4. I just can't see what
: I'm doing wrong.

Configuring TCP/IP is often a little bit confusing. It sounds to me, as if
there is no problem with the software, it's just a question of configuration.
So here are some points to check:

- Do your machines have a hostname and an IP-Address ? (must be different
  four every machine)

- Did you start the Loopback-Net(s) ? (Nameserver ?!?!)

- Did you start the SLIP or PLIP connections ?

- Check your routing !

- You have the tools ifconfig and route. USE THEM !


>Any hints on how to use 'ifconfig' and 'route' to trace non connections?
>Well this is what my main machine does to bring up MiNT-Net:
>(loads patched MiNT 1.10, all the .XFS and .XDD drivers and spawns ksh 
|> u:/bin/ifconfig sl0 addr dstaddr mtu 4096 up
|> u:/bin/route add sl0
|> u:/bin/ifconfig lo0 addr up
|> u:/bin/route add lo0
|> u:/bin/ifconfig
|> u:/bin/route
|> u:/bin/portmap
|> u:/usr/etc/inetd
|> u:/bin/mountd
|> u:/bin/nfsd
|> This file is unchanged from my (working) 0.3 configuration.
|> On the other machine the file is much the same, but obviously sets up a
|> route the other way. ( to Note: this network is *not*
|> connected to the rest of the internet, so the ip addresses aren't meaningful

You might want to try to leave out the lines with the loopback device, 
and add
instead the lines
ifconfig lo0 addr up
route add lo0
to be able to access your own computer with its own address. There was a 
bug in mint-net 0.30, where the loopback address was handled incorrectly. 
That was fixed in 0.31 and newer.


Hmmm, the description of your setup sounds quite ok to me. Perhaps
some other points to check :-) ...

- Are there appropriate entries for hostname and IP-Address in
  /etc/hosts and /etc/hostname ? check both machines.

- Try to setup ONE of your machines as nameserver (/etc/resolv.conf).
  Use either or but the SAME entry on BOTH machines.
  You should now be able to run 'hostlookup' on both machines.
  (BTW: if this works ok, forget about the next point.)

- Do both machines work with the same serial line speed ? (stty)

I guess you want to "connect" your machines via NFS ?
I have only on machine, for that reason i didn't work a lot with nfs and
do not know about any debugging-support of the nfs-package. Perhaps you
can find the bug using "nfs-debugging" !?

   Good Luck    Theo


>Some of the new MiNT net software packages look like they're set up
>to work with a syslog daemon to record kernel messages. I've looked
>around on atari.archive.umich.edu for such a beast, but I haven't
>been able to find anything.
>Does a MiNT syslog daemon already exist?

Yes, it's a part of the MiNTOS package, look for either mintossc.tgz or
mintosbn.tgz somewhere under the Mint directory hierarchy. Alternatively,
you can ftp it from:-




PS. By the way, yes, I am working on a new release and the binary
distribution will have much (if not all) the MiNTnet utilities set up in the
correct places with the rc scripts starting the daemons.