From owner-freebsd-net@FreeBSD.ORG Wed Feb 1 13:19:53 2006 Return-Path: X-Original-To: freebsd-net@FreeBSD.org 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 AB86016A422 for ; Wed, 1 Feb 2006 13:19:53 +0000 (GMT) (envelope-from subscriber@osk.com.ua) Received: from gandalf.osk.com.ua (osk.com.ua [195.5.17.76]) by mx1.FreeBSD.org (Postfix) with ESMTP id C696943D49 for ; Wed, 1 Feb 2006 13:19:52 +0000 (GMT) (envelope-from subscriber@osk.com.ua) Received: from localhost (localhost [127.0.0.1]) by gandalf.osk.com.ua (Postfix) with ESMTP id C8F2378C22 for ; Wed, 1 Feb 2006 15:20:57 +0200 (EET) Received: from gandalf.osk.com.ua ([127.0.0.1]) by localhost (gandalf.osk.com.ua [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 03147-01; Wed, 1 Feb 2006 15:20:57 +0200 (EET) Received: from OLEG (unknown [192.168.82.111]) by gandalf.osk.com.ua (Postfix) with ESMTP id 15CAB78C1F; Wed, 1 Feb 2006 15:20:57 +0200 (EET) Date: Wed, 1 Feb 2006 15:19:48 +0200 From: Oleg Tarasov X-Mailer: The Bat! (v3.64.01 Christmas Edition) Professional X-Priority: 3 (Normal) Message-ID: <215703718.20060201151948@osk.com.ua> To: FreeBSD MailList In-Reply-To: <898692010.20060125181955@osk.com.ua> References: <898692010.20060125181955@osk.com.ua> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Virus-Scanned: amavisd-new at osk.com.ua Cc: freebsd-net@FreeBSD.org Subject: Re: Policy routing and multipath routing needed (override routing table) X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: FreeBSD MailList List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 01 Feb 2006 13:19:53 -0000 Hello, Sorry for messing with things I should not as I am not a FreeBSD developer but I think this idea can be implemented without titanic work (I can be wrong due to lack of information about FreeBSD developement). Now routing is performed using lookup of destination address in the routing table. To extend its functionality I suggest adding several new fields like source address, source interface, source and destination ports, protocol and priority (like metric in windows). Priority is for identification of which rules will be tested first in the case of multiple compliance of the packet to table entries. This actually is a sorting field to the table marking the order of lookup. This configuration is reversly compatible with standart FreeBSD routing and as I think will not lead to old program malfunction. In this case there must be a default value of "any" to all table fields that are not supplied to "route" command. This method will cover both policy routing and multipath routing. It is simple but very effective. It is obviously better than Linux multiple tables and IMHO does not lead to major network stack changes. Please tell me if I am wrong but from a first glance (and the second one ;) ) it seems to be very complementary to FreeBSD functionality. -- Best regards, Oleg Tarasov mailto:subscriber@osk.com.ua