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

Markus Stenberg <> Sat, 23 April 2016 17:09 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 97A5212D161 for <>; Sat, 23 Apr 2016 10:09:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -0.048
X-Spam-Status: No, score=-0.048 tagged_above=-999 required=5 tests=[RCVD_IN_DNSWL_LOW=-0.7, SPF_NEUTRAL=0.652] autolearn=ham autolearn_force=no
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id W8Fk9BOjSHfA for <>; Sat, 23 Apr 2016 10:09:23 -0700 (PDT)
Received: from ( []) by (Postfix) with ESMTP id 5260212D0BA for <>; Sat, 23 Apr 2016 10:09:23 -0700 (PDT)
RazorGate-KAS: Status: not_detected
RazorGate-KAS: Rate: 0
RazorGate-KAS: Envelope from:
RazorGate-KAS: Version: 5.5.3
RazorGate-KAS: LuaCore: 215 2015-05-29_17-31-22 60ae4a1b4d01d14f868b20a55aced8d7df7b2e28
RazorGate-KAS: Lua profiles 78662 [Jun 02 2015]
RazorGate-KAS: Method: none
Received: from poro.lan ( by ( (authenticated as stenma-47) id 570CF19A00E974F2; Sat, 23 Apr 2016 20:08:50 +0300
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\))
From: Markus Stenberg <>
In-Reply-To: <>
Date: Sat, 23 Apr 2016 20:08:49 +0300
Content-Transfer-Encoding: quoted-printable
Message-Id: <>
References: <> <> <> <> <> <>
To: Juliusz Chroboczek <>
X-Mailer: Apple Mail (2.3124)
Archived-At: <>
Cc:, Tim Coote <>
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: Sat, 23 Apr 2016 17:09:25 -0000

On 23.4.2016, at 19.39, Juliusz Chroboczek <> wrote:
>> I’m starting by running shncpd on a boundary router and tried a trivial
>> installation.
> Excellent, thanks.
>> I don’t see how dns gets updated. Are such updates out of scope of
>> shncpd?
> Do you mean, (1) how is a DNS resolver advertised to clients, or
> (2) how clients are registered in DNS ?
> (1) is done by using the -N flag on the router advertising an external
> connection (-E).  This flag can be repeated multiple times.

hnetd grabs this automatically from wan-facing DHCP client, but again, requires integration to work nicely (odhcp6c glue script supported on most Linux platforms). Clients on the other hand are given always just first-hop router address.

> (2) is a host issue, so I believe it is better handled outside of shncpd,
> but I'm quite willing to be convinced otherwise.  (The obvious alternative
> would be to have shncpd update DNS when it gives out a DHCP lease, but
> that would mean giving up on stateless autoconf.)

Well, DHCPv4 is stateful anyway, and you could in theory bind state from there as well (at least if you do IPv4).

>> Are they in scope for the other homenet protocols?
> Markus, Steven, Ted?  What's the plan here?  Do we count on mDNS proxying,
> or should we be advertising an RFC 2136 server over HNCP?

I think the plan varies ;-)

hnetd (and current HNCP + my expired autoconf draft) are based on the idea of using mDNS _and/or stateful DHCPv4 and/or stateful DHCPv6 to determine what’s on each link, and advertise the routers responsible for each link across the homenet. It does work with ‘current stuff’ for some relatively high % of likelihood.

Ted’s draft proposes either learn-from-mDNS (=proxy DNS-update) and/or (manually/automatically configured client-sourced) DNS-update scheme. I am worried about zone merging + conflict resolution, although if it works out it sounds like a good solution. 

(Zone merging + plain hybrid proxy is at least very problematic, if you want hybrid proxies to remain stateless. I have looked at it and it is neither pretty nor efficient.)