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

Markus Stenberg <> Thu, 21 April 2016 17:33 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 1A4BF12D55E for <>; Thu, 21 Apr 2016 10:33:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -3.593
X-Spam-Status: No, score=-3.593 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, MIME_QP_LONG_LINE=0.001, RCVD_IN_DNSWL_LOW=-0.7, RP_MATCHES_RCVD=-0.996, URIBL_DBL_ABUSE_REDIR=0.001] autolearn=ham autolearn_force=no
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id t6MEVrG35gHT for <>; Thu, 21 Apr 2016 10:33:05 -0700 (PDT)
Received: from ( []) by (Postfix) with ESMTP id 6314312E34D for <>; Thu, 21 Apr 2016 10:32:59 -0700 (PDT)
RazorGate-KAS: Rate: 0
RazorGate-KAS: {MIME-Version: double versions}
RazorGate-KAS: Envelope from:
RazorGate-KAS: Version: 5.5.3
RazorGate-KAS: LuaCore: 80 2014-11-10_18-01-23 260f8afb9361da3c7edfd3a8e3a4ca908191ad29
RazorGate-KAS: Method: none
RazorGate-KAS: Lua profiles 69136 [Nov 12 2014]
RazorGate-KAS: Status: not_detected
Received: from [] ( by ( (authenticated as stenma-47) id 57123F91006A0B86; Thu, 21 Apr 2016 20:32:58 +0300
Content-Type: multipart/alternative; boundary=Apple-Mail-ABEFBD1D-CEA0-476F-8FCC-2AB523FD92CB
Mime-Version: 1.0 (1.0)
From: Markus Stenberg <>
X-Mailer: iPad Mail (13E238)
In-Reply-To: <>
Date: Thu, 21 Apr 2016 20:32:57 +0300
Content-Transfer-Encoding: 7bit
Message-Id: <>
References: <>
To: Tim Coote <>
Archived-At: <>
Subject: Re: [homenet] How many people have installed the homenet code?
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF Homenet WG mailing list <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Thu, 21 Apr 2016 17:33:13 -0000

While we have tested all hnetd versions on Debian stable as well, I cannot recommend it as there is no configuration or real integration with the system beyond "edit/create shell scripts". 

Obviously anything else automated on the associated interfaces has to be disabled as Juliusz noted. 

Disclaimer: I do not find Linux distribution integration fun so OpenWrt is enough for me. Of course I am for sale given enough money ;) ( consulting mainly on some other stuff at the moment though )


Sent from my preciouss, aka iPad ;)

> On 21.4.2016, at 15.24, Tim Coote <> wrote:
> Hullo
> Sorry, this is a bit of a granular question, and this may not be the right place for it - I’m relying on the value of running code to the group ;-) . My background is s/w engineering, rather than networking, so I could well have made some fundamentally poor assumptions.
> There was a discussion back in Oct 2015 about running hnetd (I presume) on mainstream linux distros ( Henning Rogge raised the question and Markus Stenberg responded that it had been tried on Debian 7. The discussion also referred to building hnetd on OpenWRT ( and ( based on using a larger distro and shncpd for a subset of the homenet protocols. The hnetd repo implies that it can be made to work with generic linux router firmware, which I took to mean any linux distro.
> I think that this is an important issue, based on my experience of trying to build home automation products in the IoT space. Environments without carefully engineered networks can behave in unexpected ways, even with small numbers of end devices and realistic deployments will require significant software instrumentation and the ability to change the instrumentation to understand what is going. So, I believe, you need a full fat distro for such environments that’s responsible, say, for handling 6LowPAN devices, abstraction of such devices for use by other services, and managing their lifecycles.
> So I tried to spin hnetd up on a fedora vm, and found it fighting the distro set-up. Maybe the implementation isn’t supposed to co-exist with other network controlling software on the same computer. What’s my best approach to getting the homenet protocols running as a proof of concept? I cannot find a ‘top down’ view of how the different components fit together - the descriptions seem to assume a depth of knowledge of openwrt that I don’t have.
> tia
> Tim
> _______________________________________________
> homenet mailing list