public inbox for b.a.t.m.a.n@lists.open-mesh.org
 help / color / mirror / Atom feed
From: "Linus Lüssing" <linus.luessing@c0d3.blue>
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.] Help in setting up mesh test bed using qemu - BATMAN adv
Date: Tue, 11 Oct 2016 12:36:29 +0200	[thread overview]
Message-ID: <20161011103629.GA8598@otheros> (raw)
In-Reply-To: <CAGghcR5CDGwxFBzwEm5jadLP+X9rBYvhDxDj=hkCH=NSHExsBg@mail.gmail.com>

Haven't tried that myself yet, but maybe the new network namespace
support in the git master branch might be an easy alternative to
start with?

You could first try to compile and load the batman-adv
kernel module. Then you'd create a namespace for each virtual node
you want to have. Then you connect the namespace via veth-pairs.
And finally, within each network namespace you would hook some veth
ends into a batX interface.


First you could try wiring two, then three nodes manually. If
that works and looks good you could then write a script to setup
the testbed with an arbitrary amount of virtual nodes.

Regards, Linus

  reply	other threads:[~2016-10-11 10:36 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-10-03 14:14 [B.A.T.M.A.N.] Help in setting up mesh test bed using qemu - BATMAN adv Kaushik N P
2016-10-03 17:08 ` leftbydefault
2016-10-04 10:11   ` Kaushik N P
2016-10-06 15:09     ` Ufo
     [not found]       ` <CAGghcR7QjF+yugxao-P5YsB_TkC_0D_YU2tc0+dinN9AJhZX9w@mail.gmail.com>
2016-10-07 19:53         ` Kaushik N P
2016-10-08  3:22           ` jmh8
2016-10-10 15:21             ` Kaushik N P
2016-10-10 15:47               ` jmh8
2016-10-10 15:58                 ` Kaushik N P
2016-10-11 10:36                   ` Linus Lüssing [this message]
     [not found]                     ` <CAGghcR47zo=9+jiH8L1jMRMB23ZWSZu06KYVSnzdVFR7s3JLcQ@mail.gmail.com>
     [not found]                       ` <CAGghcR7d-xuSkj7Joard+JE2ug-yHvrAxCfJ0wYa6tdybw2Aeg@mail.gmail.com>
2016-10-12 17:12                         ` Kaushik N P
2016-10-12 17:46                           ` Linus Lüssing
2016-10-12 18:04                             ` Linus Lüssing
2016-10-06  1:28 ` Marek Lindner

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=20161011103629.GA8598@otheros \
    --to=linus.luessing@c0d3.blue \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox