Xref: utzoo comp.protocols.tcp-ip:6697 comp.dcom.lans:2640
Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!nrl-cmf!ames!hc!lanl!cmcl2!rutgers!bellcore!ka9q.bellcore.com!karn
From: karn@ka9q.bellcore.com (Phil Karn)
Newsgroups: comp.protocols.tcp-ip,comp.dcom.lans
Subject: Re: Super Cheap IP router (< $1000)
Message-ID: <15165@bellcore.bellcore.com>
Date: 6 Apr 89 05:20:35 GMT
References: <583@accuvax.nwu.edu.NWU.EDU> <1989Apr4.000727.2759@utzoo.uucp> <25098@amdcad.AMD.COM> <15134@bellcore.bellcore.com> <16648@dcatla.UUCP>
Sender: news@bellcore.bellcore.com
Reply-To: karn@ka9q.bellcore.com (Phil Karn)
Organization: Secular Humanists for No-Code
Lines: 16

>Is a proxy arp scheme good enough scheme for such a low-end router?
>Phil Karn says that his KA9Q can be used as a router by configuring
>it for proxy arp...[]..Proxy arp schemes would not work in the internet at 
>large, but may be usefull in some limited applications.

You misunderstood the reason I suggested you use proxy arp. The idea was to
use it only to circumvent the "one IP address per system" design inherent in
my code. Proxy arp allows the package to reply properly to ARP requests for
its secondary IP address.

You could, of course, go further and use my proxy arp as a general routing
mechanism, but in this case the objections you raise become valid. There
is, however, no routing algorithm code in my package, although there is
talk of adding OSPFIGP.

Phil