Development issues regarding the cerowrt test router project
 help / color / mirror / Atom feed
From: Dave Taht <dave.taht@gmail.com>
To: Daniel Ezell <dezell@stonescry.com>
Cc: cerowrt-devel@lists.bufferbloat.net
Subject: Re: [Cerowrt-devel] atomic route updates?
Date: Sun, 5 May 2013 11:31:36 -0700	[thread overview]
Message-ID: <CAA93jw5LDe_mPRQfzG638xEYCnhUmQo11-F0BmGzsmr+q83M-g@mail.gmail.com> (raw)
In-Reply-To: <CANp2as-NBE1f=xrRcnab1xjA9V_RoHG5Pfwaaq_a5dTo082rnA@mail.gmail.com>

When I try to add minidlna to the build package database (e.g.
./scripts/feeds add minidlna ), nothing happens. So something's either
broke in my build or the minidlna package.


On Sun, May 5, 2013 at 6:58 AM, Daniel Ezell <dezell@stonescry.com> wrote:
> If minidlna will compile, and you have the time, could you include it in the
> next release?
>
> On May 5, 2013 6:28 AM, "Dave Taht" <dave.taht@gmail.com> wrote:
>>
>> On Thu, Apr 25, 2013 at 8:05 AM, Robert Bradley
>> <robert.bradley1@gmail.com> wrote:
>> > 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.
>>
>> Still stuck on this? I'm planning a new build this week with your
>> atomic route stuff in it. babel 1.3.6 and 1.40 have been released.
>>
>> >
>> > 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
>> >
>> > _______________________________________________
>> > Cerowrt-devel mailing list
>> > Cerowrt-devel@lists.bufferbloat.net
>> > https://lists.bufferbloat.net/listinfo/cerowrt-devel
>>
>>
>>
>> --
>> Dave Täht
>>
>> Fixing bufferbloat with cerowrt:
>> http://www.teklibre.com/cerowrt/subscribe.html
>> _______________________________________________
>> Cerowrt-devel mailing list
>> Cerowrt-devel@lists.bufferbloat.net
>> https://lists.bufferbloat.net/listinfo/cerowrt-devel



-- 
Dave Täht

Fixing bufferbloat with cerowrt: http://www.teklibre.com/cerowrt/subscribe.html

  reply	other threads:[~2013-05-05 18:31 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-20  9:56 Dave Taht
2013-04-24  6:14 ` Maciej Soltysiak
2013-04-24  9:33   ` Dave Taht
2013-04-24 13:27 ` Robert Bradley
2013-04-24 14:03   ` Robert Bradley
2013-04-24 15:46   ` Dave Taht
2013-04-25 15:05     ` Robert Bradley
2013-05-05 12:02       ` Dave Taht
2013-05-05 13:58         ` Daniel Ezell
2013-05-05 18:31           ` Dave Taht [this message]
2013-05-05 17:01         ` Robert Bradley

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://lists.bufferbloat.net/postorius/lists/cerowrt-devel.lists.bufferbloat.net/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CAA93jw5LDe_mPRQfzG638xEYCnhUmQo11-F0BmGzsmr+q83M-g@mail.gmail.com \
    --to=dave.taht@gmail.com \
    --cc=cerowrt-devel@lists.bufferbloat.net \
    --cc=dezell@stonescry.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox