From owner-freebsd-doc Sat Oct 7 18:30: 5 2000 Delivered-To: freebsd-doc@freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id AA2E737B502 for ; Sat, 7 Oct 2000 18:30:02 -0700 (PDT) Received: (from gnats@localhost) by freefall.freebsd.org (8.9.3/8.9.2) id SAA66833; Sat, 7 Oct 2000 18:30:02 -0700 (PDT) (envelope-from gnats@FreeBSD.org) Date: Sat, 7 Oct 2000 18:30:02 -0700 (PDT) Message-Id: <200010080130.SAA66833@freefall.freebsd.org> To: freebsd-doc@freebsd.org Cc: From: Brooks Davis Subject: Re: docs/21826: ARP proxy feature lacks documentation Reply-To: Brooks Davis Sender: owner-freebsd-doc@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org The following reply was made to PR docs/21826; it has been noted by GNATS. From: Brooks Davis To: Bernd Luevelsmeyer Cc: Brooks Davis , freebsd-gnats-submit@FreeBSD.ORG Subject: Re: docs/21826: ARP proxy feature lacks documentation Date: Sat, 7 Oct 2000 18:26:34 -0700 On Sun, Oct 08, 2000 at 03:07:22AM +0200, Bernd Luevelsmeyer wrote: > Thanks. I tried that already, to no avail. The gateway answered ARP > requests as intended but didn't forward the traffic, just as with 'arp > -s'. > Hence, the documentation issue about the /etc/rc.conf feature > "arpproxy_all" remains. Err, what do you want to do? ARP proxying is just to allow a gateway to lie to hosts who's idea of network layout doesn't match reality. The gateway must handle packet forwarding seperatly. Clearly this needs to be documented, but I'm not sure you're looking for the right thing. -- Brooks -- Any statement of the form "X is the one, true Y" is FALSE. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-doc" in the body of the message