From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-wi0-x236.google.com (mail-wi0-x236.google.com [IPv6:2a00:1450:400c:c05::236]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority" (verified OK)) by huchra.bufferbloat.net (Postfix) with ESMTPS id 71DC821F1B5 for ; Thu, 25 Apr 2013 08:05:59 -0700 (PDT) Received: by mail-wi0-f182.google.com with SMTP id m6so3514309wiv.15 for ; Thu, 25 Apr 2013 08:05:56 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:message-id:date:from:user-agent:mime-version:to:subject :references:in-reply-to:content-type:content-transfer-encoding; bh=ed/nqEoizkcejArwlfSQ1abpqMEPVC6BBcgufsjdfTs=; b=n2Izh2953JeTM4pVYWhGYQe2ghriE3u/ztX+WKvgDmmS8eQLf36MbIITGRY6y52vhC IyYMWxwSAVlD/Tg+VPb2ygu/ciByUmjyx5sxzLv5Em9GdyjHVZ+lzyLbaWCoU6wLkpNs PaKK1AQrWl2x5KbHA5z20TR87ZNyt8VfFZUugOQo39KqwIbPKLPSF9hXfYj2Wjz0NMK1 lNJQLodr3uZo1jOmAJVkbda4+7qFrlKjSug4C+8+6yB8rOaGNVTGY5jNl/mm9QAzlVLw Wf1Y/vfdT3a1A1/HAIPPGyF4obMALWkwkaxhtGEY6arU/8igbte8FWMv4yUd85nDAweK f8dw== X-Received: by 10.194.92.176 with SMTP id cn16mr58313932wjb.51.1366902356641; Thu, 25 Apr 2013 08:05:56 -0700 (PDT) Received: from ?IPv6:2001:470:6aac:3::783c:88e8? ([2001:470:6aac:3::783c:88e8]) by mx.google.com with ESMTPSA id g4sm11447653wib.11.2013.04.25.08.05.55 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Thu, 25 Apr 2013 08:05:56 -0700 (PDT) Message-ID: <51794652.4030906@gmail.com> Date: Thu, 25 Apr 2013 16:05:54 +0100 From: Robert Bradley User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130404 Thunderbird/17.0.5 MIME-Version: 1.0 To: cerowrt-devel References: <5177DDA8.8010801@gmail.com> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: [Cerowrt-devel] atomic route updates? X-BeenThere: cerowrt-devel@lists.bufferbloat.net X-Mailman-Version: 2.1.13 Precedence: list List-Id: Development issues regarding the cerowrt test router project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 25 Apr 2013 15:06:00 -0000 On 24/04/13 16:46, Dave Taht wrote: > There is a possibly related bug being discussed on the babel-users list with an > easy fix. > > Not sure what kernel versions it happens on. > I was seeing that bug on the quantal 3.5 kernel as well. So far, testing with the raring 3.8 kernel seems to fix both the unreachable route bug and the random /128 route bugs. My patched babeld also appears to work no worse than the distro-provided 1.3.1 build. That said, with both versions I see that babeld switches to wireless routes and stays there if eth0 is disconnected and later restored. It may be time for me to try running the babeld HEAD code without the patches and compare the behaviour of that to the patched version next... -- Robert Bradley