From owner-freebsd-net@FreeBSD.ORG Tue Jan 3 15:42:07 2012 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 1C8691065676 for ; Tue, 3 Jan 2012 15:42:07 +0000 (UTC) (envelope-from borjam@sarenet.es) Received: from proxypop04b.sare.net (proxypop04b.sare.net [194.30.0.79]) by mx1.freebsd.org (Postfix) with ESMTP id CEDCC8FC12 for ; Tue, 3 Jan 2012 15:42:06 +0000 (UTC) Received: from [172.16.2.2] (izaro.sarenet.es [192.148.167.11]) by proxypop04.sare.net (Postfix) with ESMTPSA id 4899A9DC53A; Tue, 3 Jan 2012 16:42:05 +0100 (CET) Mime-Version: 1.0 (Apple Message framework v1084) Content-Type: text/plain; charset=us-ascii From: Borja Marcos In-Reply-To: <20120103152909.GA83706@sandvine.com> Date: Tue, 3 Jan 2012 16:42:04 +0100 Content-Transfer-Encoding: quoted-printable Message-Id: <6A630554-160A-4A20-B791-6E110D5B9FF4@sarenet.es> References: <99A5FFD9-8815-4CCC-9868-FB2E3D799566@gridfury.com> <4F027BC0.1080101@FreeBSD.org> <8F87C898-3290-41B9-ACDF-3558D7C28D74@gmail.com> <20120103152909.GA83706@sandvine.com> To: Ed Maste X-Mailer: Apple Mail (2.1084) Cc: Nikolay Denev , freebsd-net@freebsd.org Subject: Re: openbgpds not talking each other since 8.2-STABLE upgrade 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, 03 Jan 2012 15:42:07 -0000 On Jan 3, 2012, at 4:29 PM, Ed Maste wrote: > On Tue, Jan 03, 2012 at 09:07:56AM +0200, Nikolay Denev wrote: >=20 >> Since I've had similar problem with Quagga after updating to = 8.2-STABLE I'd suggest >> you to try setting "net.inet.tcp.signature_verify_input=3D0" and see = if that would help. >>=20 >> Here is another thread about the similar (if not the same) problem :=20= >> = http://groups.google.com/group/mailing.freebsd.bugs/browse_thread/thread/e= a347a919dbc165d/eeaa2965fc4f64c9?show_docid=3Deeaa2965fc4f64c9&pli=3D1 >=20 > Thanks for the link Nikolay. >=20 > Borja, I assume it's the PR submission form that gave you trouble - > sorry for that. Based on your report it sounds to me like the bug is Yes, I was filling a very detailed report and it was lost. Quite = annoying... > in OpenBGPd itself. If it works on OpenBSD with the TCP_MD5SIG option > though I'd assume it's due to a difference in our (FreeBSD's) > implementation of the option. Did you look at the OpenBSD/FreeBSD > differences in your investigation? What I saw is that OpenBGPd *sets* the TCP_MD5SIG for the socket just to = test if TCP_MD5 is available. Maybe in OpenBSD the behavior is different = and unless you set the key TCP_MD5 won't be really enabled. In FreeBSD, = the keys are set outside of your program using setkey(8). The second link you mention is simply a configuration problem. Unless = you include TCP_SIGNATURE in the kernel config file, TCP_MD5 support = will not be available. What I observed is this: if you have TCP_MD5 correctly available in the = system, I mean, TCP_SIGNATURE and the rest of the IPSEC support = correctly configured into the kernel, OpenBGPd is unable to work = *without* TCP_MD5. Quagga works, I can use TCP_MD5 or not, my choice.=20 Borja.