From owner-freebsd-net@FreeBSD.ORG Tue Apr 5 15:31:50 2011 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 4B43F1065670 for ; Tue, 5 Apr 2011 15:31:50 +0000 (UTC) (envelope-from if@freebsd.org) Received: from chile.gbit.at (ns1.xip.at [193.239.188.99]) by mx1.freebsd.org (Postfix) with ESMTP id A76C88FC0C for ; Tue, 5 Apr 2011 15:31:49 +0000 (UTC) Received: (qmail 11330 invoked from network); 5 Apr 2011 17:31:47 +0200 Received: from unknown (HELO filebunker.xip.at) (89.207.145.147) by chile.gbit.at with (DHE-RSA-AES256-SHA encrypted) SMTP; 5 Apr 2011 17:31:47 +0200 Date: Tue, 5 Apr 2011 17:31:45 +0200 (CEST) From: Ingo Flaschberger X-X-Sender: if@filebunker.xip.at In-Reply-To: Message-ID: References: User-Agent: Alpine 2.00 (LRH 1167 2008-08-23) MIME-Version: 1.0 Content-Type: MULTIPART/MIXED; BOUNDARY="168430090-1871926318-1302017507=:2152" Cc: Nikolay Denev , freebsd-net@freebsd.org Subject: Re: Routing enhancement - reduce routing table locking X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 05 Apr 2011 15:31:50 -0000 This message is in MIME format. The first part should be readable text, while the remaining parts are likely unreadable without MIME-aware tools. --168430090-1871926318-1302017507=:2152 Content-Type: TEXT/PLAIN; charset=ISO-8859-15; format=flowed Content-Transfer-Encoding: 8BIT >> Can you say something more about : >>    "implement some multipath changes to use a direct attached >>      interface route and a real route, used some OpenBSD code" >> >> I've looked at the patch but it's not obvious to me. >> >> P.S.: I've just saw your reply to kern/155772 and was wondering if this >> patch can help. > > regarding kern/155772: > at stock 8.2 FreeBSD the system panics after ifconfig down / ifconfig up / > ifconfig down with 1 route and 1 interface route (multipath). > > Also there are problems with arp, due wrong multipath route selection > (if the decision is already made that the route should go the direct way, the > route and not the interface route is choosen, depends on which route was > first in the tree). see "in_lltable_rtcheck" > And finally, there are problems when adding / deleteing routes. > > example that does not work: > ifconfig em0 192.168.0.1/24 > ifconfig em1 10.0.0.1/24 > route add 10.0.0.0/24 192.168.0.2 > > example that currently works with 8.2: > ifconfig em0 192.168.0.1/24 > ifconfig em1 10.0.0.1/24 > route add 172.16.0.0/24 192.168.0.2 > route add 172.16.0.0/24 10.0.0.2 > > Kind regards, > Ingo Flaschberger --168430090-1871926318-1302017507=:2152--