Re: [homenet] How many people have installed the homenet code?

Tim Coote <tim+ietf.org@coote.org> Thu, 21 April 2016 15:30 UTC

Return-Path: <tim+ietf.org@coote.org>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4317212EC10 for <homenet@ietfa.amsl.com>; Thu, 21 Apr 2016 08:30:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id fca6gGfOFhkA for <homenet@ietfa.amsl.com>; Thu, 21 Apr 2016 08:30:13 -0700 (PDT)
Received: from mercury.coote.org (575185b4.skybroadband.com [87.81.133.180]) by ietfa.amsl.com (Postfix) with ESMTP id BC39012E9FF for <homenet@ietf.org>; Thu, 21 Apr 2016 08:30:12 -0700 (PDT)
Received: by mercury.coote.org (Postfix, from userid 1000) id 56E7516C129F; Thu, 21 Apr 2016 16:30:11 +0100 (BST)
X-Original-To: homenet@ietf.org
Received: from [127.0.0.1] (localhost [IPv6:::1]) by mercury.coote.org (Postfix) with ESMTP id AF96816C1183; Thu, 21 Apr 2016 16:30:10 +0100 (BST)
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2104\))
From: Tim Coote <tim+ietf.org@coote.org>
In-Reply-To: <87oa93vz8e.wl-jch@pps.univ-paris-diderot.fr>
Date: Thu, 21 Apr 2016 16:30:10 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <917CFE11-2386-4B0D-8A81-F87764AC09A4@coote.org>
References: <6E709688-414A-4AFB-AEAE-56BAE0469583@coote.org> <87oa93vz8e.wl-jch@pps.univ-paris-diderot.fr>
To: Juliusz Chroboczek <jch@pps.univ-paris-diderot.fr>
X-Mailer: Apple Mail (2.2104)
X-Spambayes-Classification: ham; 0.00
Archived-At: <http://mailarchive.ietf.org/arch/msg/homenet/ypsNYG1Bu-PnsFxoHLROBdFrvQA>
Cc: homenet@ietf.org
Subject: Re: [homenet] How many people have installed the homenet code?
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF Homenet WG mailing list <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/homenet/>
List-Post: <mailto:homenet@ietf.org>
List-Help: <mailto:homenet-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/homenet>, <mailto:homenet-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 21 Apr 2016 15:30:14 -0000

Thanks.
> On 21 Apr 2016, at 15:00, Juliusz Chroboczek <jch@pps.univ-paris-diderot.fr>; wrote:
> 
> Hnetd is designed to integrate into the OpenWRT ecosystem, which it does
> remarkably well.  Because of that, it depends on a large part of the
> OpenWRT stack, such as their DHCP and RA clients and servers.  While it is
> possible to run hnetd
> 
> This was the second most important reason for writing shncpd: to make an
> implementation of Homenet that is easy to port to any Unix system.
> I think I've been reasonably successful with that, but shncpd needs some
> more work [1].
> 
> [1] https://www.irif.univ-paris-diderot.fr/~jch/software/homenet/shncpd.html
>    has a list of known limitations.
It’s the IPv6 stuff that I’m most interested in - IoT with ipv4 (NAT) is too expensive to support at scale. At least for the retail market. My sense was that the api to the openwrt tools was a likely stumbling block.  I did get the babeld stuff working (thanks for what you’ve done there), but gave up with tools like dibbler for PD as the challenge is the coordination across nodes.
> 
> Even if you're just testing plain babeld, even without hnetd, you must
> kill network manager.  If you don't, thinkgs may appear to work at first,
> but NM will take revenge later.
I hated NM. But I think that it’s getting better. It does provide an initial overall visualisation of what’s going on. Something will be required to show the overall picture across all digital entities involved in a system, including ‘phones with both wifi and LTE connections. For the consumer there needs to be at least a green/red light (cf a CD pipeline status), but finer granularity would also have value.  I would hope to encourage the NM community to at least take cognisance of the Homenet protocols.

At the complexity that is emerging in homes, a configuration defined by a gui will not scale: too hard to get to a known state, especially with >1 node.

Maybe I need to create a separate openwrt vm if I cannot run the hnetd stack on a more complete distro.
> 
> — Juliusz
> 
Tim