> Well, the rabel repo exists for the crazy ideas... and unfortunately
> testing them at scale tends towards being a PITA.
Exactly my point. Ideas are cheap.
-- Juliusz
___
Babel-users mailing list
Babel-users@lists.alioth.debian.org
> If that is the only error in two highly speculative documents then I'm
> winning. :)
You'll be helpful (I prefer this to "winning") when you implement some of
your ideas and provide us with hard data to show that they are useful.
(For the record, CS6 and unicast IHU have both been implemented,
On Mon, Jan 2, 2017 at 3:35 PM, Juliusz Chroboczek wrote:
>> For the wired link case, I am surprised babel considers it "interfering"!
>
> It doesn't.
>
> https://github.com/jech/babeld/blob/master/interface.c#L210
If that is the only error in two highly speculative documents
On Mon, Jan 2, 2017 at 6:28 AM, Benjamin Henrion wrote:
> On Mon, Dec 12, 2016 at 6:25 PM, Dave Taht wrote:
>> I've long been testing a few out of tree patches for babel and long
>> have had the intent to try a few more once the first phase of the
>>
On Mon, Dec 12, 2016 at 6:25 PM, Dave Taht wrote:
> I've long been testing a few out of tree patches for babel and long
> have had the intent to try a few more once the first phase of the
> make-wifi-fast work was completed - which it mostly is, so far as lede
> is concerned
Dave,
Thanks for writing this up, it's an interesting read.
I agree with you on the topic of multicast. My implementation sends
everything unicast, with the exception of Hellos. I'm interested in
working on a way to allow unicast Hellos. I read your thoughts here:
6 matches
Mail list logo