Thanks Pete.. the install does force me to link to the Hydra driver and I know it works because I can see the driver in my setup and I can also ping machines and the router....so perhaps you are right with the browser but before I go down that road (as per Kolla's request) - here are some screen dumps after I run the ROUTE from command line:
What happens when I run ROUTE from a shell after I initialize startinet prefs
===================================================
MISC{150-DH1}:NetWking/Inet225/Inet/c> route add amiga2000 192.168.1.1 1---> Integer metric
add host amiga2000: gateway 192.168.1.1 ----> output after I run the command
5.MISC{150-DH1}:NetWking/Inet225/Inet/c> netstat -rn
Routing tables
Destination Gateway Flags Refs Use Interface
127.0.0.1 127.0.0.1 UH 0 97 lo0
192.168.1.76 192.168.1.1 UGH 0 0 s0
192.168.1.76 127.0.0.1 UH 0 1 lo0
default 192.168.1.76 U 0 0 s0
192.168.1 192.168.1.76 U 0 1 s0
ROUTE COMMANDS DOC BELOW (note the Integer Metric switches)
==========================================
Interworks I-Net 225 - TCP/IP Networking Software
Command: route
Location: inet:c/
NAME
route - manually manipulate the routing tables
SYNOPSIS
0m1mroute0m -N=NOSYM/S,-F=FLUSH/S,ROUTES/S,CMD/M
DESCRIPTION
route is used to manipulate the network routing tables manually.
route supports two commands:
1. Add a route.
add [net |host] destination gateway [count]
2. Delete a route.
delete [net |host] destination gateway [count]
The ROUTES switch will cause 0m1mroute0m to read its input from the file
'inet:db/routes'. Each line in that file must be either an 0m1madd0m or
0m1mdelete0m command as shown above, or a comment line (starting with
';' or '#'). Blank lines are ignored. Incorrect lines will be reported to
the console, but the rest of the file will still be processed.
When adding a route, if the route already exists, a message is printed and
nothing changes.
Other command line arguments are:
net or host
specifies the type of destination address. If not specified, routes to a
particular host are distinguished from those to a network by interpreting
the Internet address associated with destination. If the destination has a
"local address part" (last section of 'dotted' address, i.e. if address is
'200.0.0.20', '.20' is the part referenced) of 0, route is assumed to be to
a network; otherwise, it is treated as a route to a host.
destination destination host system where the packets will be
routed. destination can be either a host name (the official name or an
alias), a network name (the official name or an alias, an Internet address
in "dot" notation, or the keyword "default", which signifies the wildcard
gateway route.
gateway The gateway through which the destination is reached.
gateway can be either a host name (the official name or an alias), or an
Internet address in "dot" notation.
count An integer that indicates whether the gateway is a remote
host or the local host. If the route leads to a destination via a remote
gateway, count should be a number greater than 0. If the route leads to
destination and the gateway is the local host, count should be 0. The
default for count is zero. The result is not defined if count is negative.
All symbolic names specified for a destination or gateway are looked up
first as a hostname using gethostbyname(); if the hostname is not found,
the destination is searched as a network name using getnetbyname().
destination and gateway can be in dot notation. If the -n option is not
specified, any host and network addresses are displayed symbolically
according to the name returned by gethostbyaddr() and getnetbyaddr(),
respectively, except for the default network address (printed as default)
and addresses that have unknown names. Addresses with unknown names are
printed in Internet dot notation. If the -n option is specified, any host
and network addresses are printed in Internet dot notation except for the
default network address which is printed as default.
If the -f option is specified, route deletes all route table entries
that specify a remote host for a gateway. If this is used with one of
the commands described above, the entries are deleted before the
command's application.
Output
add destination: gateway gateway flags flags
The specified route is being added to the tables.
delete destination: gateway gateway flags flags
The specified route is being deleted from the tables.
Flags
The following truth table can be used to help understand the relationship
between count, destination type, flags, and route type.
Count Destination Type Flags Route Type
_________________________________________________________
=0 network 1 =U route to a network via a
gateway which is the local host
>0 network 3 =UG route to a network via a
gateway which is a remote host
=0 host 5 =UH route to a host via
a gateway which is
the local host
itself
>0 host 7 =UGH route to a host via a gateway
which is a remote host
=0 "default" 1 =U wildcard route via the local host
>0 "default" 3 =UG wildcard route via a remote gateway
DIAGNOSTICS
error: delete a route that does not exist
meaning: The specified route was not in the route table.
error: add a route that already exists
meaning: The specified entry is already in the route table.
error: add too many routes
meaning: The routing table is full.
AUTHOR
route was developed by the University of California, Berkeley. The ROUTES
switch and other related items were designed and developed by Jim Cooper of
Interworks.
SEE ALSO
netstat
ifconfig
