Xref: utzoo comp.protocols.tcp-ip:6664 comp.dcom.lans:2631
Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!tut.cis.ohio-state.edu!ucbvax!amdcad!rpw3
From: rpw3@amdcad.AMD.COM (Rob Warnock)
Newsgroups: comp.protocols.tcp-ip,comp.dcom.lans
Subject: Re: Super Cheap IP router (< $1000)
Message-ID: <25098@amdcad.AMD.COM>
Date: 4 Apr 89 11:23:49 GMT
References: <583@accuvax.nwu.edu.NWU.EDU> <1989Apr4.000727.2759@utzoo.uucp>
Reply-To: rpw3@amdcad.UUCP (Rob Warnock)
Organization: [Consultant] San Mateo, CA
Lines: 24

In article <1989Apr4.000727.2759@utzoo.uucp> henry@utzoo.uucp writes:
+---------------
| In article <583@accuvax.nwu.edu.NWU.EDU> morrison@accuvax.nwu.edu writes:
| >I have developed software for Turning a klunky old IBM XT into a IP router...
| Was there some reason not to just use the Phil Karn ("KA9Q") TCP/IP
| for the PC/XT/AT/...?  I can't see any reason why Phil's stuff wouldn't
| make a perfectly good router; were you aware of its existence?
+---------------

Well, for one thing, Phil's code associates an IP address with the *host*,
not with each interface. (See? KA9Q isn't *perfect*... yet.)  That's all
right when you a gatewaying from (say) Ethernet to a SLIP link, but isn't
so hot if you are trying to go Ether-to-Ether.  (Someone at AMD hacked the
KA9Q code to put the IP addresses with the interface, and *is* playing with
it as an experimental IP router. But it's a hack, and not completely general.
Best would be for one of the real KA9Q maintainers to do an "official" fix.)


Rob Warnock
Systems Architecture Consultant

UUCP:	  {amdcad,fortune,sun}!redwood!rpw3
DDD:	  (415)572-2607
USPS:	  627 26th Ave, San Mateo, CA  94403