From owner-freebsd-net@FreeBSD.ORG Thu Jan 8 11:55:27 2015 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 28F73C54 for ; Thu, 8 Jan 2015 11:55:27 +0000 (UTC) Received: from smarthost1.sentex.ca (smarthost1.sentex.ca [IPv6:2607:f3e0:0:1::12]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "smarthost.sentex.ca", Issuer "smarthost.sentex.ca" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id E6CC8605 for ; Thu, 8 Jan 2015 11:55:26 +0000 (UTC) Received: from [IPv6:2607:f3e0:0:4:f025:8813:7603:7e4a] (saphire3.sentex.ca [IPv6:2607:f3e0:0:4:f025:8813:7603:7e4a]) by smarthost1.sentex.ca (8.14.9/8.14.9) with ESMTP id t08BtL7r061192; Thu, 8 Jan 2015 06:55:21 -0500 (EST) (envelope-from mike@sentex.net) Message-ID: <54AE6FF4.6030504@sentex.net> Date: Thu, 08 Jan 2015 06:54:28 -0500 From: Mike Tancsa Organization: Sentex Communications User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:31.0) Gecko/20100101 Thunderbird/31.3.0 MIME-Version: 1.0 To: Przemyslaw Frasunek , freebsd-net@freebsd.org Subject: Re: Corrupted IPv6 routing table References: <54ADBDDC.3040901@frasunek.com> In-Reply-To: <54ADBDDC.3040901@frasunek.com> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit X-Scanned-By: MIMEDefang 2.75 X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 08 Jan 2015 11:55:27 -0000 On 1/7/2015 6:14 PM, Przemyslaw Frasunek wrote: > Dear all, > > We are running FreeBSD 9.2-RELEASE-p3 on few PPPoE access servers, each > servicing about 1000 customers. Each server exchanges customers' /32 (for IPv4) > and /64 (for IPv6) routes using OSPF and BIRD. > > Few times in a month, we are experiencing routing table corruption, which causes > spurious IPv6 routes appearing with prefixlen 0: I saw this a few yrs ago when I tried mpd with ipv6 after about a month. There are some threads (i think on freebsd-net) about it and some of the areas that needed to be fixed. I had to give up on v6 and mpd as a result. I seem to recall some commits to RELENG_10 that might had addresses some of the bugs I saw, but thats just speculation. Have you tried RELENG_10 as an LNS ? ---Mike -- ------------------- Mike Tancsa, tel +1 519 651 3400 Sentex Communications, mike@sentex.net Providing Internet services since 1994 www.sentex.net Cambridge, Ontario Canada http://www.tancsa.com/