Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!uwm.edu!linac!att!ucbvax!dribble.c-mols.siu.edu!dan
From: dan@dribble.c-mols.siu.edu (Dan Ellison)
Newsgroups: comp.protocols.tcp-ip.ibmpc
Subject: Re: ka9q configuration
Message-ID: <9104160849.aa09417@dribble.c-mols.siu.EDU>
Date: 16 Apr 91 13:49:38 GMT
Sender: rwh@ucbvax.BERKELEY.EDU
Reply-To: dan%c-mols@siucvmb.cdale.siu.edu
Organization: The Internet
Lines: 88

>=========================================================================
>Date:         Mon, 15 Apr 91 13:31:00 PDT
>From:         opschk@GANGES.UCOP.EDU
>Subject:      Installing ka9q/nos as a router on a 386 PC
> 
>Thanks for Tony and Milton for their answers so far. More clarifications
>on what I am doing:
	
	text deleted.....

>Let's say I get the appropriate IP adresses, how do I start net now,
>how do I build autoexec.net  ? sample autoexec.net's appreciated .
> 
>Also I have to remove ethdrv from autoecex.bat right ?

Right.  Just the packet driver should be between ka9q and the hardware.
I currently use ka9q and the Clarkson packet drivers (Version 9) for a
router between my local ethernet and the building tokenring backbone.
The following is what my "autoexec.net" looks like.  Works quite well
I might add.  Another thanks to the developers of ka9q!!!!

AUTOEXEC.NET:

# ka9q NOS router implementation as configured by: Dan Ellison (KA9NEW)

hostname drizzle.c-mols.siu.edu
attach packet 0x61 et 5 1500
attach packet 0x62 tr 5 1500
#
# the tokenring card belongs to the backbone subnet!
#
ifconfig tr netmask 0xffffff00 ip 131.230.91.120 broadcast 131.230.91.255
#
# the ethernet belongs to the local ethernet subnet
#
ifconfig et netmask 0xffffff00 ip 131.230.93.7 broadcast 131.230.93.255
#
# set up the default routing information then let RIP take care of the
# rest
#
route add 131.230.91.0/24 tr 
route add 131.230.93.0/24 et 
route add 131.230.92/24 et 131.230.93.4 2
route add 131.230.1/24 tr 131.230.91.127 6
route add default tr 
#
# incorporate the local nameserver for lookups
#
domain addserver [131.230.93.2]
#
# for broadcasts to work!
#
arp add 131.230.93.255 ether ff:ff:ff:ff:ff:ff
arp add 131.230.91.255 ether ff:ff:ff:ff:7f:ff
#
# some standard parameters
#
ip ttl 16
tcp mss 216
tcp window 1500
#
# start up the servers
#
start telnet
start smtp
start ftp
start echo
start discard
start rip
#
# start up rip hosts, seed from the backbone router and then pass on
# everything that we learn!
#
rip request 131.230.91.127
rip add 131.230.91.127 60		# refresh must be less than 3 minutes
rip add dribble.c-mols.siu.edu 60	# or we lose our routing info!
rip add iris.c-mols.siu.edu 60
rip add agate.c-mols.siu.edu 60
rip merge on				# this is a nice feature (experimental)

I hope that this helps.
-- 
/============================================================================\
+ Dan Ellison, Network Admin	- internet: dan%c-mols@siucvmb.cdale.siu.edu +
+ Molecular Science Program	- BITNET:   dan%c-mols@siucvmb.BITNET	     +
+ Southern Illinois University 	- UUCP:     uunet!siucvmb.BITNET!c-mols!dan  +
+ Carbondale, IL  62901		- PHONE:    (618) 453-7321		     +
\============================================================================/