From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-iw0-f171.google.com (mail-iw0-f171.google.com [209.85.214.171]) (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 05842200875 for ; Wed, 22 Jun 2011 09:36:57 -0700 (PDT) Received: by iwn34 with SMTP id 34so1304447iwn.16 for ; Wed, 22 Jun 2011 10:04:05 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=2XKIYc+/RVr6r+euU6cw9ZywBoCDvI3J7DLU7AeU1eo=; b=hru+CO7+gXcbwpb7SKftXEWPeN7WvBAajbmXSjsLO+/IhP5Yc8vaU4ljeKTD82bp6M LXE6WHn+dxGbLcUKXtiMJr18fmjy2iObp4KjvX7W7VJ2RT57o9yYthDGNHhTLSueDJjk 9vZV3ze5tJzs9O1IpjOPrCHgKjV69Xd4/0bbI= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=AmQ7Pyn21fFn09lCr+5YNA5SmZQ2T4Pu+27eRJYx+T8mQKK3V5Ks/7M5+zITWYzz7Q d0wdtN5Nr1TL8FeSnqucOKqK73/pTYguP0AlWpsfzlvVYRIpN2YISZjOzEmzhY9htNy6 E7GBLqLK18Z5RveI9T0rPJ7N9Fye50VJcnnzE= MIME-Version: 1.0 Received: by 10.43.61.196 with SMTP id wx4mr846878icb.310.1308762244101; Wed, 22 Jun 2011 10:04:04 -0700 (PDT) Received: by 10.231.13.76 with HTTP; Wed, 22 Jun 2011 10:04:03 -0700 (PDT) In-Reply-To: <7ipqm6c7ds.fsf@lanthane.pps.jussieu.fr> References: <7ipqm6c7ds.fsf@lanthane.pps.jussieu.fr> Date: Wed, 22 Jun 2011 11:04:03 -0600 Message-ID: Subject: Re: battling with babel and route changes From: Dave Taht To: Juliusz Chroboczek Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Cc: bloat-devel@lists.bufferbloat.net, babel-users@lists.alioth.debian.org X-BeenThere: bloat-devel@lists.bufferbloat.net X-Mailman-Version: 2.1.13 Precedence: list List-Id: "Developers working on AQM, device drivers, and networking stacks" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 22 Jun 2011 16:36:58 -0000 On Wed, Jun 22, 2011 at 7:39 AM, Juliusz Chroboczek wr= ote: > > A patch to reflect the metric in the kernel priority has been published > on this list at some point; I'll not be merging it into Babel, since > I remain convinced that that's the wrong thing to do. I agree that it is the wrong thing to do. Babel's metric calculations are decidedly different than that of other protocols. However, to clean up the route change... either maintaining two routes of different priority differing by 1, or inserting the new route with priority of base+1 and moving it down after removing the first route, seems like a workable solution, that can save hundreds of packets at high volumes. I'm perfectly willing to try implementing either of these approaches (the latter being far easier than the first) my concern was that by doing so I'd break something somewhere else, and felt the best approach was the first, which, as I said, is harder to implement. >> 1) babel installs ipv4 routes with a metric of 0, ipv6 routes with a >> metric of 1024 > > These are apparently the kernel's defaults -- we call the kernel with > the value 0 in both cases. =A0You can set the priority with -k (but canno= t > set it to be different between v4 and v6), and if you need any more > control, use routing tables (-t and -T). > > -- Juliusz > --=20 Dave T=E4ht SKYPE: davetaht US Tel: 1-239-829-5608 http://the-edge.blogspot.com