From owner-freebsd-net@FreeBSD.ORG Thu Jul 31 11:36:47 2003 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A0FAC37B401 for ; Thu, 31 Jul 2003 11:36:47 -0700 (PDT) Received: from phoenix.gargantuan.com (rrcs-se-24-73-171-238.biz.rr.com [24.73.171.238]) by mx1.FreeBSD.org (Postfix) with ESMTP id E333E43FBD for ; Thu, 31 Jul 2003 11:36:46 -0700 (PDT) (envelope-from michael@gargantuan.com) Received: from cyclops.gargantuan.com (cyclops.gargantuan.com [3ffe:c00:8034:a00::300]) by phoenix.gargantuan.com (Postfix) with ESMTP id 201B7292; Thu, 31 Jul 2003 14:36:46 -0400 (EDT) From: "Michael W. Oliver" To: Barney Wolff , Bob Date: Thu, 31 Jul 2003 14:36:36 -0400 User-Agent: KMail/1.5.2 References: <01a801c35782$8886b380$6501010a@gis2.com> <20030731181316.GA90414@pit.databus.com> In-Reply-To: <20030731181316.GA90414@pit.databus.com> MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Description: clearsigned data Content-Disposition: inline Message-Id: <200307311436.45134.michael@gargantuan.com> cc: freebsd-net@freebsd.org Subject: Multihomed Routing (was Re: Multiple Interfaces) X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: michael@gargantuan.com List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 31 Jul 2003 18:36:48 -0000 =2D----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 +--- On Thursday, July 31, 2003 14:13, | Barney Wolff proclaimed: | | On Thu, Jul 31, 2003 at 11:07:18AM -0600, Bob wrote: | > All you are missing is the fact FreeBSD cannot handle | > two NICs the same subnet. OpenBSD does, NetBSD does and Linux does. | | Wrong. As already stated, make the netmask on the second one /32. | | Re freevrrpd, so far as I know it's intended for the case of two machines | where one backs up the other, not two interfaces on one machine taking | over for each other. I may be wrong here, but the problem lies in having duplicate routes in the= =20 routing table, which is what would happen if two interfaces were in the=20 same network and had the same mask (/26 for example). This is solved by=20 having a different mask for the second interface (much like using the /32=20 for VRRPd), but it is only a band-aid. I am no programmer, so forgive my ignorance in that respect, but why can't = a=20 metric be used to differentiate routes to the same destination network=20 within the routing table? I happened to be googling and found: http://daily.daemonnews.org/view_story.php3?story_id=3D3878 which describes exactly what I am talking about. Is there any reason why=20 this shouldn't be implemented by default in the OS? Personally, I would=20 very much like the ability of Zebra to feed the kernel the same route to=20 multiple destinations, differentiating those routes by metric value. Comments? =2D --=20 +-------------------------------------+------------------------------+ | Michael W. Oliver, CCNP | "The tree of liberty must be | | IPv6 & FreeBSD mark | refreshed from time to time | | michael@gargantuan.com | with the blood of patriots | | http://michael.gargantuan.com/ | and tyrants." | | ASpath-tree, Looking Glass, etc. | - President Thomas Jefferson | | +------------------------------+ | gpg key - http://michael.gargantuan.com/gnupg/pubkey.asc | +--------------------------------------------------------------------+ =2D----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.2 (FreeBSD) iD8DBQE/KWG9sWv7q8X6o8kRAvsBAJwMhuja+N/U/W9Oqbb406Al1dI5MgCgjIQz aQxPupNElWciMWw9cXLMYjo=3D =3Dkg2R =2D----END PGP SIGNATURE-----