From owner-freebsd-net Sat Mar 17 11:10:57 2001 Delivered-To: freebsd-net@freebsd.org Received: from spider.pilosoft.com (p55-222.acedsl.com [160.79.55.222]) by hub.freebsd.org (Postfix) with ESMTP id DC52937B718 for ; Sat, 17 Mar 2001 11:10:54 -0800 (PST) (envelope-from alex@acecape.com) Received: from localhost (alexmail@localhost) by spider.pilosoft.com (8.9.3/8.9.3) with ESMTP id OAA08955; Sat, 17 Mar 2001 14:15:39 -0500 (EST) X-Authentication-Warning: spider.pilosoft.com: alexmail owned process doing -bs Date: Sat, 17 Mar 2001 14:15:39 -0500 (EST) From: Alex Pilosov X-Sender: alexmail@spider.pilosoft.com To: Julian Elischer Cc: Nick Rogness , freebsd-net@FreeBSD.ORG, Jeroen Ruigrok/Asmodai Subject: Re: same interface Route Cache In-Reply-To: <3AB3B2FF.3A04B53C@elischer.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Sat, 17 Mar 2001, Julian Elischer wrote: > this will do what you want for OUTGOING packets. > incoming packets will probably all come in on one network. And to fix this, you play tricks with your DNS server :) A setup that I have at home: Domain with two listed nameservers (same machine, different IPs). BIND set up split-brained: two named.confs, one configured to listen only on IP on network A, the other on network B. Two zone files, one listing IPs on A, other on B. Result: BIND will reply with IPs that belong to the interface packet came in on. This provides load-sharing (nameservers for domain are usually queried randomly) and reliability (if one connection is down, everything still works, because the other "half" of nameserver is still running and giving out IPs on the correct interface). -- -- Alex Pilosov | http://www.acecape.com/dsl CTO - Acecape, Inc. | AceDSL:The best ADSL in Bell Atlantic area 325 W 38 St. Suite 1005 | (Stealth Marketing Works! :) New York, NY 10018 | To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message