From: "Linus Lüssing" <linus.luessing@web.de>
To: The list for a Better Approach To Mobile Ad-hoc Networking
<b.a.t.m.a.n@lists.open-mesh.org>
Subject: Re: [B.A.T.M.A.N.] Batman-adv + lxc
Date: Fri, 21 Mar 2014 11:12:06 +0100 [thread overview]
Message-ID: <20140321101205.GA6008@Linus-Debian> (raw)
In-Reply-To: <1629001.Cx5dbnsKCT@lappi>
Hi Christof,
On Thu, Mar 20, 2014 at 07:59:16PM +0100, Christof Schulze wrote:
> Hello,
>
> This is my first post to this list. I would like to run batman-adv
> inside an lxc-container just as described in [1]. I do not want to do it
> to simulate a network having multiple nodes but to separate duties of
> different "virtual machines" - linux containers in my case and to be
> able to easily migrate the configuration to a differen machine lateron.
lxc-container support has not been properly implemented in
batman-adv yet. So things are not always working "naturely" and can
even make your system crash (e.g. rebooting an lxc-container makes
your system crash [0]).
>
> I started by loading batman-adv on the host and bridging it into the
> container. After adding the interfaces inside the container where
> meshing should happen I cannot add a gateway because batctl complains
> that /sys/class/net/bat0/mesh does not exist. Indeed, in the container
> it does not exist.
>
> How can batman-adv be used from an lxc-container?
>
What I usually did was configuring batman-adv properly on the host
via batctl. And only in the end adding it to the lxc-container.
That seemed to work for me (except the reboot crash noted above).
Cheers, Linus
[0]: http://www.open-mesh.org/issues/179
next prev parent reply other threads:[~2014-03-21 10:12 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-20 18:59 [B.A.T.M.A.N.] Batman-adv + lxc Christof Schulze
2014-03-21 10:12 ` Linus Lüssing [this message]
2014-03-21 10:12 ` Antonio Quartulli
2014-03-21 10:39 ` Christof Schulze
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20140321101205.GA6008@Linus-Debian \
--to=linus.luessing@web.de \
--cc=b.a.t.m.a.n@lists.open-mesh.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.