From owner-freebsd-isp Fri Oct 2 11:48:54 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA16683 for freebsd-isp-outgoing; Fri, 2 Oct 1998 11:48:54 -0700 (PDT) (envelope-from owner-freebsd-isp@FreeBSD.ORG) Received: from carp.gbr.epa.gov (carp.gbr.epa.gov [204.46.159.110]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA16672 for ; Fri, 2 Oct 1998 11:48:52 -0700 (PDT) (envelope-from mjenkins@carp.gbr.epa.gov) Received: (from mjenkins@localhost) by carp.gbr.epa.gov (8.8.8/8.8.8) id NAA03536; Fri, 2 Oct 1998 13:48:27 -0500 (CDT) (envelope-from mjenkins) Date: Fri, 2 Oct 1998 13:48:27 -0500 (CDT) From: Mike Jenkins Message-Id: <199810021848.NAA03536@carp.gbr.epa.gov> To: steven@shellnet.co.uk Subject: Re: IPFW, Dual network cards Cc: freebsd-isp@FreeBSD.ORG In-Reply-To: <3615a823.10152184@smtp.shellnet.co.uk> Sender: owner-freebsd-isp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > .-----------------------. > | FreeBSD 3 | > '-----------------------' > / \ > Intel Realtek > 194.129.209.8 192.168.0.1/194.129.209.15 > | | | > | Internal network | > Cisco Hub to | > 2501 router. bandwidth limited servers If you can convince FreeBSD that a few strays from 194.129.209.0 live on the inside network, then arpproxy_all="YES" is your friend. No need for any extra routes in the router. FreeBSD will answer the arp requests for the strays and forward the packets. This is no different than a PPP dialup where the remote client appears to be on the LAN. Mike To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isp" in the body of the message