From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: From: Marek Lindner Date: Fri, 13 Apr 2012 00:17:31 +0200 References: <4F86B02B.9060900@gmail.com> In-Reply-To: MIME-Version: 1.0 Content-Type: Text/Plain; charset="utf-8" Content-Transfer-Encoding: 7bit Message-Id: <201204130017.31711.lindner_marek@yahoo.de> Subject: Re: [B.A.T.M.A.N.] Migration to Batman Reply-To: The list for a Better Approach To Mobile Ad-hoc Networking List-Id: The list for a Better Approach To Mobile Ad-hoc Networking List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: b.a.t.m.a.n@lists.open-mesh.org Cc: Jernej Kos On Thursday, April 12, 2012 19:05:54 Mitar wrote: > > In batman-adv you can add/remove interfaces at runtime without problems > > so you doesn't need bridging or similar nasty things > > Great. Can you also say to work on all "tun+" interfaces, so that any > interface which starts with "tun" is automatically operated on? No, batman-adv is not a user space daemon with a configuration file, hence you can't tell batman-adv to wait for tun+. However, you can easily write a simple shell script for hotplug which adds whatever interface you want to batman-adv as soon as it is created. Or, if you are using OpenWrt, you can simply extend the existing hotplug shell script to interprete the "+" as you like. Regards, Marek