From owner-freebsd-hackers Tue Jan 23 05:03:28 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id FAA14001 for hackers-outgoing; Tue, 23 Jan 1996 05:03:28 -0800 (PST) Received: from rocky.sri.MT.net (rocky.sri.MT.net [204.182.243.10]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id FAA13989 Tue, 23 Jan 1996 05:03:25 -0800 (PST) Received: (from nate@localhost) by rocky.sri.MT.net (8.6.12/8.6.12) id GAA25331; Tue, 23 Jan 1996 06:05:59 -0700 Date: Tue, 23 Jan 1996 06:05:59 -0700 From: Nate Williams Message-Id: <199601231305.GAA25331@rocky.sri.MT.net> To: Bill Fenner Cc: hackers@freebsd.org, wollman@freebsd.org Subject: Re: arp(8) and proxy arp's In-Reply-To: <199601230714.XAA07552@freefall.freebsd.org> References: <199601230714.XAA07552@freefall.freebsd.org> Sender: owner-hackers@freebsd.org Precedence: bulk > I propose to seperate out "pub" (announce this ARP entry to others, use > this ARP entry when trying to talk to this host) and "proxy" (only > announce this ARP entry and don't try to use it) to make it deterministic > which one the arp(8) command creates. I plan to add a "Do-What-I-Mean" > that recognizes "arp -s ip myetheraddress pub" and turns it into a > "proxy" request. But "pub" will create a "proxy-and-use" entry and > "proxy" will create a "proxy only" entry and the behavior will always > be predictable no matter what is in the routing table. > > Comments? Please do. :) Nate