🚀 go-pugleaf

It's 06 Apr 97  14:30,
We'll return to pm@mail.campaspe.net.au and All's
discussion of TCP/IP via network failure

 pm> IP:             192.168.0.1
 pm> Gateway:        0.0.0.0
 pm> Netmask:        255.255.255.0
 pm> Nameserver:     Should point to the machine with Domain Name
 pm> Services.

In Linux, you shouldn't need to specify a router.  Just a couple of
route commands:

route add 127.0.0.1 lo
route add 192.168.0.0 netmask 255.255.255.0 eth0

should do the trick. :-)

As for the nameserver, leave it blank if none present, and edit
/etc/resolv.conf to have the line:

order hosts

so Linux doesn't attempt to query a non-existent nameserver, and only
uses the local hosts file to resolve hostnames.

Otherwise if a nameserver is available, point it to that machine.

 pm> Win 95 box
 pm> ----------

 pm> IP:             192.168.0.2
 pm> Gateway:        0.0.0.0 ( This normally points to a router. )
 pm> Netmask:        255.255.255.0
 pm> Nameserver:     Should point to the machine with Domain Name
 pm> Services.

Or leave blank if no nameserver is present.  For 2 machines, it's
simpler to put the hostnames in /etc/hosts (Linux) and hosts.txt
(Windows). :)

 pm> Just for you reference the set of IP numbers I have used are public
 pm> numbers. This means that they don't conflict with any numbers used on
 pm> the internet today....

And should only be used for isolated networks or those behind a
firewall, where traffic can't (under normal circumstances) directly
enter the Internet.  (the Internet won't know how to route for these
addresses, so things won't work).

... "I'm out of coffee, off my medication, and you say NO mail!?!"
--
| Fidonet:  Tony Langdon 3:632/367.2
| Internet: tlang@freeway.DIALix.oz.au
|
| Freeway Internet Gateway, Melbourne, Australia.  For information about
| our services and conditions of use, e-mail:
| info@freeway.DIALix.oz.au, to receive a copy of the FAQ.