From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from forward14.mail.yandex.net (forward14.mail.yandex.net [IPv6:2a02:6b8:0:801::4]) by huchra.bufferbloat.net (Postfix) with ESMTP id AAF0821F0BB for ; Tue, 3 Jul 2012 07:14:15 -0700 (PDT) Received: from web9f.yandex.ru (web9f.yandex.ru [95.108.131.225]) by forward14.mail.yandex.net (Yandex) with ESMTP id 8131719811E3; Tue, 3 Jul 2012 18:14:12 +0400 (MSK) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yandex.ru; s=mail; t=1341324852; bh=u1A1ifiqq7ssj9PcrpmB6wQhbSB85YqiRhtOU8uKy2U=; h=From:To:Cc:In-Reply-To:References:Subject:MIME-Version:Message-Id: Date:Content-Transfer-Encoding:Content-Type; b=uO6OLaOx4MPDXVRNF65YL8GGz8uPp4DazVpfzDC8hgpFGKsC8JrXDA817vUyea1LN GEA3+JwCkzOhTLtRY/ogIsNLWHY3EQlFqw834i5HqL59HB5BtQZXtTkPD2sIJbVFf5 3NflFtsjJpmzh0+XWE0pbSckRHdAPDFc/vDRGbDY= Received: from 127.0.0.1 (localhost.localdomain [127.0.0.1]) by web9f.yandex.ru (Yandex) with ESMTP id 3C66DF90022; Tue, 3 Jul 2012 18:14:12 +0400 (MSK) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yandex.ru; s=mail; t=1341324852; bh=u1A1ifiqq7ssj9PcrpmB6wQhbSB85YqiRhtOU8uKy2U=; h=From:To:Cc:In-Reply-To:References:Subject:MIME-Version:Message-Id: Date:Content-Transfer-Encoding:Content-Type; b=uO6OLaOx4MPDXVRNF65YL8GGz8uPp4DazVpfzDC8hgpFGKsC8JrXDA817vUyea1LN GEA3+JwCkzOhTLtRY/ogIsNLWHY3EQlFqw834i5HqL59HB5BtQZXtTkPD2sIJbVFf5 3NflFtsjJpmzh0+XWE0pbSckRHdAPDFc/vDRGbDY= Received: from dhcp-217-131-wifi.yandex.net (dhcp-217-131-wifi.yandex.net [213.180.217.131]) by web9f.yandex.ru with HTTP; Tue, 03 Jul 2012 18:14:10 +0400 From: Denis Ovsienko To: cerowrt-devel In-Reply-To: References: <2187151341044351@web9d.yandex.ru> <7isjdcpm1q.fsf@lanthane.pps.jussieu.fr> <40851341093226@web25d.yandex.ru> <7ik3yoz7p2.fsf@lanthane.pps.jussieu.fr> <1521341229978@web13h.yandex.ru> <206861341262491@web23d.yandex.ru> <458481341303008@web7d.yandex.ru> <751571341318910@web30g.yandex.ru> MIME-Version: 1.0 Message-Id: <847401341324850@web9f.yandex.ru> Date: Tue, 03 Jul 2012 18:14:10 +0400 X-Mailer: Yamail [ http://yandex.ru ] 5.0 Content-Transfer-Encoding: 8bit Content-Type: text/plain; charset=koi8-r Cc: babel-users Subject: [Cerowrt-devel] switching cerowrt to quagga-babeld issues 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: Tue, 03 Jul 2012 14:14:16 -0000 03.07.2012, 17:18, "Dave Taht" : > šOn Tue, Jul 3, 2012 at 8:35 AM, Denis Ovsienko wrote: >>> ššDoes anybody know where this difference comes from? >> ššThe difference comes from NetworkManager. Its efforts in reproducing high-metric RTPROT_KERNEL routes with low-metric RTPROT_STATIC ones are effectively hiding the kernel issue outside of CeroWrt runtime. Would it be better to add a watchdog shell script, which does the same, or patch the kernel? > šI would *much rather* patch the kernel than have a watchdog. However I > šdon't quite understand > šthe redistribution issue vs a vs ipv6 here. If I have a "redistribute > škernel" on for ipv4, it does propagate the default route. The matter is, IPv4 default route comes flagged as either "static" or "boot" (both cases are displayed without "proto" column by /sbin/ip route). This is properly picked up. IPv6 default route comes flagged as "kernel".. > š(I note that I dislike network manager too as it tries too hard to > šwork around bugs in the base OS and my own view of the world is far > šmore "meshy") > > šI'll gladly try pushing a patch up to the mainline if that's what is needed. I've got no required expertise to make such change safe for all, but starting with a Cero-only patch seems possible. -- šššDenis Ovsienko