From owner-freebsd-hackers Mon Sep 20 4:23:13 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from not.demophon.com (ns.demophon.com [193.65.70.13]) by hub.freebsd.org (Postfix) with ESMTP id 0CB2114F51 for ; Mon, 20 Sep 1999 04:22:57 -0700 (PDT) (envelope-from will@not.demophon.com) Received: (from will@localhost) by not.demophon.com (8.9.3/8.8.7) id OAA98267; Mon, 20 Sep 1999 14:22:50 +0300 (EEST) (envelope-from will) To: zzhang@cs.binghamton.edu (Zhihui Zhang) Cc: hackers@freebsd.org Subject: Re: Multiple routes to the same destination References: From: Ville-Pertti Keinonen Date: 20 Sep 1999 14:22:49 +0300 In-Reply-To: zzhang@cs.binghamton.edu's message of "17 Sep 1999 17:53:11 +0300" Message-ID: <8667154yk6.fsf@not.demophon.com> Lines: 20 X-Mailer: Gnus v5.5/XEmacs 20.4 - "Emerald" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG zzhang@cs.binghamton.edu (Zhihui Zhang) writes: > As said by the 4.4 BSD book (page 423), 4.4 BSD does not support multiple > routes to the same destination (identical key and mask). Does the radix > tree code in FreeBSD - 4.0 has the same limitation? I am wondering if > there is already a solution for this? How would the routing code use multiple routes? You'd need additional rules to determine how to use them (e.g. round-robin for load balancing). In some cases where you want something unusual, you can use different net sizes for the same net. The code selects the route with the smallest net (or at least used to - I don't know whether this is documented behavior). Note that the destination presumably means the destination where the data being routed should end up, not the gateway it is sent to. Multiple routes referring to the same gateway are obviously supported. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message