From owner-freebsd-questions Mon Oct 23 16:24:26 2000 Delivered-To: freebsd-questions@freebsd.org Received: from rapidnet.com (rapidnet.com [205.164.216.1]) by hub.freebsd.org (Postfix) with ESMTP id 899DC37B479; Mon, 23 Oct 2000 16:24:22 -0700 (PDT) Received: from localhost (nick@localhost) by rapidnet.com (8.9.3/8.9.3) with ESMTP id RAA09295; Mon, 23 Oct 2000 17:23:28 -0600 (MDT) Date: Mon, 23 Oct 2000 17:23:28 -0600 (MDT) From: Nick Rogness To: les@safety.net Cc: Fred Clift , Marko Ruban , freebsd-questions@FreeBSD.ORG, freebsd-hackers@FreeBSD.ORG Subject: Re: gateway on different subnet In-Reply-To: <200010232214.PAA14556@ns3.safety.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 23 Oct 2000, Les Biffle wrote: > > Hm -- how about using proxy-arp style routing? > > Here's what I've done in the past: > > 1. Have a friend out in the net ping your address 208.59.162.242 > > 2. Run tcpdump and look for someone ARPing for you. That someone > will very likely be your default gateway as seen from your site. > If that router is in your subnet, set your default to it and you're > done. If not, continue at the next step. > > 3. Pick an IP Address in your cable subnet that feels like a really > good router address to you. Make something up. 208.59.162.1 perhaps? > > 4. Use "arp -s 208.59.162.1 xx:xx:xx:xx:xx:xx" to install an arp > entry in your route table for this made-up address. That will keep > you from ARPing for 208.59.162.1 and discovering the device that > really owns that address. > > 5. Set your default gateway to 208.59.162.1. If that doesn't work (it should), you could also look into the ipfw fwd option. I would like to know when you get it to work... Nick Rogness - Drive defensively. Buy a tank. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message