IETF Logo Mail Archive

Re: [babel] Example configuration

Toke Høiland-Jørgensen <toke@toke.dk> Wed, 14 August 2019 12:47 UTC

Return-Path: <toke@toke.dk>
X-Original-To: babel@ietfa.amsl.com
Delivered-To: babel@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 633F9120803 for <babel@ietfa.amsl.com>; Wed, 14 Aug 2019 05:47:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level:
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=toke.dk
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 lE5z30YO9p8E for <babel@ietfa.amsl.com>; Wed, 14 Aug 2019 05:47:02 -0700 (PDT)
Received: from mail.toke.dk (mail.toke.dk [52.28.52.200]) (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 A6EFF1200A3 for <babel@ietf.org>; Wed, 14 Aug 2019 05:47:02 -0700 (PDT)
From: Toke Høiland-Jørgensen <toke@toke.dk>
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=toke.dk; s=20161023; t=1565786819; bh=Wc14KeAxm8Ukk6Vrm017CMEfqBblndsHAwUPLN/+9lo=; h=From:To:Cc:Subject:In-Reply-To:References:Date:From; b=YB1dyoj2tAvoTU2r3Kp5YEZxArifzIvMQXn4VJ5dtuW2Sk4RtwGTrkLEXrFBXZzyi /dAalZa9gfqoycxx0XyhQczaiLMVBzcLuRRUXYpvyciMNVxFGwT5lH+qobINCKRQep CdGY+kIc3IBnjKEKRIrt63A6tlYQtCnQGSRW8EoDy+CL3Y3QTTsiYe1kYKmqqnXHxZ kuhZexPUIiF00AxzBA4RJOTwNdOi8HrUN8r/bnh826zD2L7DPYEY0cCW0CwQCj/vFJ KV3imJUMd/ySR//rADmV3u8XxpufY/covohSGPIPAFRAMyeW0bO+KGeW55I7ecnJuX Ku1b/RxHTPgJg==
To: Mahesh Jethanandani <mjethanandani@gmail.com>, "STARK, BARBARA H" <bs7652@att.com>
Cc: Juliusz Chroboczek <jch@irif.fr>, Babel at IETF <babel@ietf.org>
In-Reply-To: <9554AC75-4674-4EB2-B40D-26CA383E3343@gmail.com>
References: <E726ED50-6D90-4537-B237-6E52D375F50B@gmail.com> <8736itu6j8.wl-jch@irif.fr> <0E0A89B7-3D7A-4605-8776-2CF685B268B0@gmail.com> <877e7qaxte.wl-jch@irif.fr> <1C6F628C-7A3C-4D66-9930-9F0244A20722@gmail.com> <8736ieasm6.wl-jch@irif.fr> <EF249683-1BB0-4686-A77A-847E64E4EA50@gmail.com> <87pnlhaixh.wl-jch@irif.fr> <2D09D61DDFA73D4C884805CC7865E6114E257961@GAALPA1MSGUSRBF.ITServices.sbc.com> <0B28A1FA-32B4-41E6-B646-C6A3907E9CCC@gmail.com> <2D09D61DDFA73D4C884805CC7865E6114E258CF7@GAALPA1MSGUSRBF.ITServices.sbc.com> <B2CE14DA-DEDA-40FB-AA96-FB4009F5FA19@gmail.com> <2D09D61DDFA73D4C884805CC7865E6114E25905B@GAALPA1MSGUSRBF.ITServices.sbc.com> <87lfw3u52i.fsf@toke.dk> <110D87BA-BBA1-417B-9BC3-77BAD4B201D1@gmail.com> <87ftmbs92f.fsf@toke.dk> <26F1A0CD-1FD2-456E-B295-8A60D93CF8E0@gmail.com> <87sgqbmhhe.wl-jch@irif.fr> <F30C9756-5104-4A43-BDD9-008FF3011362@gmail.com> <2D09D61DDFA73D4C884805CC7865E6114E2680FE@GAALPA1MSGUSRBF.ITServices.sbc.com> <9554AC75-4674-4EB2-B40D-26CA383E3343@gmail.com>
Date: Wed, 14 Aug 2019 14:46:59 +0200
X-Clacks-Overhead: GNU Terry Pratchett
Message-ID: <87woffap8c.fsf@toke.dk>
MIME-Version: 1.0
Content-Type: text/plain
Archived-At: <https://mailarchive.ietf.org/arch/msg/babel/wrPm3WGiwjsDi62TE0GB3KTYobM>
Subject: Re: [babel] Example configuration
X-BeenThere: babel@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "A list for discussion of the Babel Routing Protocol." <babel.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/babel>, <mailto:babel-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/babel/>
List-Post: <mailto:babel@ietf.org>
List-Help: <mailto:babel-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/babel>, <mailto:babel-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 14 Aug 2019 12:47:04 -0000

Mahesh Jethanandani <mjethanandani@gmail.com> writes:

> Hi Barbara, et. all, 
>
> If you are managing a small number of interfaces (< 10 in my mind),
> then your approach is simpler. Configure link properties per interface
> and be done, even if means repeating the configuration on those 10
> interfaces.
>
> If we are talking about a larger set, then the complexity might be
> worth it, simply to allow changes in one place.
>
> The question therefore comes down to, what is the normal number of
> interfaces a device will configure to run babeld?

For most current Babel deployments I'm familiar with: One or two
wireless interfaces and maybe a single wired. Definitely less than 10...

-Toke

v2.23.0 | Report a Bug | By Email