Re: [homenet] HNCP: interaction with routing protocol?

Mikael Abrahamsson <swmike@swm.pp.se> Mon, 14 December 2015 06:15 UTC

Return-Path: <swmike@swm.pp.se>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B50D71B2C87 for <homenet@ietfa.amsl.com>; Sun, 13 Dec 2015 22:15:12 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.961
X-Spam-Level:
X-Spam-Status: No, score=-3.961 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HELO_EQ_SE=0.35, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
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 TQQvMO2gXURN for <homenet@ietfa.amsl.com>; Sun, 13 Dec 2015 22:15:10 -0800 (PST)
Received: from uplift.swm.pp.se (swm.pp.se [212.247.200.143]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B0D551B2C8A for <homenet@ietf.org>; Sun, 13 Dec 2015 22:15:10 -0800 (PST)
Received: by uplift.swm.pp.se (Postfix, from userid 501) id 5F4CDA2; Mon, 14 Dec 2015 07:15:07 +0100 (CET)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=swm.pp.se; s=mail; t=1450073707; bh=hV/9WkRFsZ5s6bcMaO5LqICdXkT34ZvpWm2DBF8LDNI=; h=Date:From:To:cc:Subject:In-Reply-To:References:From; b=352miBLV9Z6+tSj//UI4PwJz04ctVTa30SNUrH7nZFXUHX0TqufvUibI0Np4BUKJz 2lTfdBszfT+9j2/OCu3uXh+ipDZVt2zWGKVZMA1SapwUK5jpmk6OPP60aUXbOuqliT EOzrrkqnUIIdqK6mGHqvs9m2jS4yShVnv1y5LtQU=
Received: from localhost (localhost [127.0.0.1]) by uplift.swm.pp.se (Postfix) with ESMTP id 56D59A1; Mon, 14 Dec 2015 07:15:07 +0100 (CET)
Date: Mon, 14 Dec 2015 07:15:07 +0100 (CET)
From: Mikael Abrahamsson <swmike@swm.pp.se>
To: Juliusz Chroboczek <jch@pps.univ-paris-diderot.fr>
In-Reply-To: <87wpsif4kq.wl-jch@pps.univ-paris-diderot.fr>
Message-ID: <alpine.DEB.2.02.1512140712170.20919@uplift.swm.pp.se>
References: <87a8pegqs5.wl-jch@pps.univ-paris-diderot.fr> <alpine.DEB.2.02.1512132029350.20919@uplift.swm.pp.se> <87wpsif4kq.wl-jch@pps.univ-paris-diderot.fr>
User-Agent: Alpine 2.02 (DEB 1266 2009-07-14)
Organization: People's Front Against WWW
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
Archived-At: <http://mailarchive.ietf.org/arch/msg/homenet/6x5XhV4SfJssXeaWjxXFXUKmIE8>
Cc: homenet@ietf.org
Subject: Re: [homenet] HNCP: interaction with routing protocol?
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.15
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: Mon, 14 Dec 2015 06:15:12 -0000

On Sun, 13 Dec 2015, Juliusz Chroboczek wrote:

> The OpenWRT hnetd configuration redistributes everything, indeed.  The
> recommended shncpd configuration redistributes just hncpd routes:
>
>    redistribute local deny
>    redistribute proto 43 allow

Just to be clear here, when you say "hnetd configuration" you are 
referring to babeld.conf that gets installed when you install hnetd-full? 
So it's really the babel configuraton that you get when installing hnetd?

Because as far as I understand, hnetd doesn't do any redistribution into 
the routing protocol, this is done by configuring the routing protocol to 
look at interface addresses/prefix and communicating this to other 
participants in the routing protocol?

hnetd does address configuration on interfaces, the routing protocol 
picks this up because that's how it's configured...? Hnetd doesn't 
communicate directly with the routing protocol at all, right? It just sets 
up the landscape so the routing protocol can come and survey it and 
communicate the contents.

-- 
Mikael Abrahamsson    email: swmike@swm.pp.se