From owner-freebsd-net@FreeBSD.ORG Wed Feb 13 21:06:07 2008 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 96AEE16A420; Wed, 13 Feb 2008 21:06:07 +0000 (UTC) (envelope-from jp@tns.cz) Received: from bonifac.tns.cz (sodat1-51.bm.gin.cz [213.194.214.51]) by mx1.freebsd.org (Postfix) with ESMTP id 4E93413C457; Wed, 13 Feb 2008 21:06:07 +0000 (UTC) (envelope-from jp@tns.cz) Received: by bonifac.tns.cz (Postfix, from userid 1001) id CE4ABF1996; Wed, 13 Feb 2008 21:30:12 +0100 (CET) Date: Wed, 13 Feb 2008 21:30:12 +0100 From: Josef Pojsl To: Eygene Ryabinkin Message-ID: <20080213203012.GB1157@bonifac.tns.cz> References: <20080207074944.GA56085@bonifac.tns.cz> <20080207141422.GG11393@diehard.n-r-g.com> <20080206144104.GL1122@bonifac.tns.cz> <20080207074944.GA56085@bonifac.tns.cz> <20080208105357.GF1142@bonifac.tns.cz> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.16 (2007-06-09) Cc: freebsd-net@freebsd.org, farrokhi@FreeBSD.org, Claudio Jeker Subject: Re: ospf cost and route selection (openospfd) 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: Wed, 13 Feb 2008 21:06:07 -0000 Hello Eygene, On Wed, Feb 13, 2008 at 10:37:29PM +0300, Eygene Ryabinkin wrote: > Found another OpenBSD/FreeBSD discrepancy: FreeBSD wants to see IP > header's length in the native host order, when it sends the packets > with sendmsg(). Corrected the patch and tried it on my test setup > with Qemu: it worked in the configuration that is simular to yours. > But one exception: my interfaces are not point-to-point, because > it is too late to get VPNs up and running for today ;)) So it will > be very good if you will be able to test the new version. > > Attached is the modified patch for the port itself and the modified > file 'files/patch-ospfd_packet.c': it is the only changed file from > the previous version of my patch. So, if you had already patched > the port to 4.2 with previous version, just drop patch-ospfd_packet.c > into the 'files/' directory and rebuild the patch. Thanks for that patch. I have replaced patch-ospfd_packet.c with the new one, and OSPF packets can find their way through again now. Unfortunately, the behavior is the same as with openospfd 4.0; it converges with right costs etc., but with the wrong interface. Everything is exactly the same. -- Josef