dan@dribble.c-mols.siu.edu (Dan Ellison) (04/16/91)
>========================================================================= >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 + \============================================================================/
nelson@sun.soe.clarkson.edu (Russ Nelson) (04/17/91)
In article <9104160849.aa09417@dribble.c-mols.siu.EDU> dan@dribble.c-mols.siu.edu (Dan Ellison) writes:
ip ttl 16
This ttl is too low. For example, it's twenty hops between MIT and my PC.
I use 255. Since the value is only there to prevent zombie packets, you're
not hurt much by too-high values, but you're hurt greatly by too-low values.
tcp mss 216
tcp window 1500
That's an awfully small mss value. I'd use tcp mss 1024 and window 4096,
unless I was using a 3c501, in which case I'd use a window of 1024 also.
--
--russ <nelson@clutx.clarkson.edu> I'm proud to be a humble Quaker.
It's better to get mugged than to live a life of fear -- Freeman Dyson
I joined the League for Programming Freedom, and I hope you'll join too.opschk@GANGES.UCOP.EDU (04/19/91)
Thanks to Dan Ellison and Rick Beebe for their answers. I am still trying to experiment with it. I am getting the additional cards next week. I built the following autoexec.nos in the root directory: hostname grumpy.ucop.edu attach packet 0x65 nt1 3 1500 ifconfig nt1 netmask 0xffffff00 ip 128.48.103.18 broadcast 128.48.103.255 route add 128.48.103.0/24 nt1 route add default nt1 # # incorporate the local nameserver for lookups # domain addserver [128.48.100.91] #nile # # for broadcasts to work! # arp add 128.48.103.255 ether ff:ff:ff:ff:ff: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 128.48.100.91 rip add 128.48.100.91 60 # refresh must be less than 3 minutes Q: can 1 use the names autoexec.nos and autoexec.net interchangeably ?? The problem is I have to give the IP adresses, when I am ftp'ing. What do I have to do to be able to use names instead of IP adresses ?? Thanks in advance, Camille opschk@ganges.ucop.edu, 415 987 03 62
BEEBE@YALEMED.BITNET (Rick Beebe) (04/19/91)
>[...] >I built the following autoexec.nos in the root directory: > >[...] ># incorporate the local nameserver for lookups ># >domain addserver [128.48.100.91] #nile >[...] >Q: can 1 use the names autoexec.nos and autoexec.net interchangeably ?? > >The problem is I have to give the IP adresses, when I am ftp'ing. >What do I have to do to be able to use names instead of IP adresses ?? There are two versions of the KA9Q software out there. The original was called NET and used autoexec.net. Sometime around 1989, Phil Karn completely rewrote it and renamed it NOS. Obviously, one uses autoexec.net the other autoexec.nos. Unfortunately, to add the to the confusion, oft-times I see copies of NOS that are named NET.EXE. Very bewildering, although it does display the name correctly when you fire it up. You can pass the name of the configuration file on the command line, so if your heart is set on using autoexec.net, just call it like this: NOS AUTOEXEC.NET. The line in your autoexec.nos (included above) "domain addserver" adds the ip address of your local name server. That should be all you need to be able to use names. When you open a connection using a name, NOS will send a query to 128.48.100.91 to resolve that name. If it's not working, then you need to talk to your local net gurus to see why. When NOS has resolved a name, it will put it in a file on your disk called domains.txt (called a local cache) so that subsequent connects to that node will be much faster. ----------------------------------------------------------------------------- Rick Beebe (203) 785-4566 ***** ***** ***** * * Biomedical Computing Unit * * * ** * Yale University School of Medicine * * *** * * * 333 Cedar Street, New Haven, CT 06514 * * * * ** * * * * * BEEBE@YALEMED.BITNET beebe@biomed.med.yale.edu -----------------------------------------------------------------------------
opschk@GANGES.UCOP.EDU (04/20/91)
Dan, thanks for your answers: In your message, you wrote: >There are two versions of the KA9Q software out there. The original was called >NET and used autoexec.net. Sometime around 1989, Phil Karn completely rewrote >it and renamed it NOS. Obviously, one uses autoexec.net the other autoexec.nos. I think then I am running net, which is the older version, (it's displaying net> and I must use autoexec.net ). I ftp'd to thumper.bellcore.com, this is the dir listing of pub/ka9q/nos: ftp> dir 200 PORT command successful. 150 Opening data connection for /bin/ls (ascii mode) (0 bytes). total 3498 -rw-r--r-- 1 406 406 7122 Mar 9 00:06 asmobj.zip -rw-r--r-- 1 406 406 181144 Mar 9 00:07 net.exe -rw-r--r-- 1 406 61 11627 Feb 1 14:39 pi.zip -rw-r--r-- 1 406 406 575471 Jan 28 23:56 src0127.zip -rw-r--r-- 1 406 406 586562 Feb 1 03:39 src0131.zip -rw-r--r-- 1 406 406 578296 Feb 1 22:51 src0201.zip -rw-rw-rw- 1 406 406 580567 Mar 9 00:06 src0308.zip -rw-r--r-- 1 406 406 529116 Nov 28 17:30 src1128.zip -rw-r--r-- 1 406 406 529562 Nov 30 09:32 src1130.zip there is no nos.exe, I am running the same net.exe, where can I then get nos.exe . Many Thanks, Camille opschk@ganges.ucop.edu, 415 987 03 62
spgdrp@GANGES.UCOP.EDU ("Donald R. Proctor spgdrp@ganges.ucop.edu") (04/20/91)
I think then I am running net, which is the older version, (it's displaying net> and I must use autoexec.net ). I ftp'd to thumper.bellcore.com, this is the dir listing of pub/ka9q/nos: Notice, though, that at the top of the screen it says "KA9Q NOS". Don