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: Wed, 12 Oct 2016 19:46:46 +0200	[thread overview]
Message-ID: <20161012174646.GD10902@otheros> (raw)
In-Reply-To: <CAGghcR7wro6kSZrFfC=dMrXcuFrK89i7Vjz8Vr+u+UwVTk_UnQ@mail.gmail.com>

First result in my favorite search engine for "linux network
namespace":

http://blog.scottlowe.org/2013/09/04/introducing-linux-network-namespaces/

Extensively describes how to set up and use network namespaces
with veth.

Have fun :-).

Regards, Linus


On Wed, Oct 12, 2016 at 10:42:30PM +0530, Kaushik N P wrote:
> Hello,
> 
> @Linus, I am a bit new to this and haven't much exposure to compiling
> kernels and all. I will try out and see what I can do with it, but a
> little more explanation would help a lot.
> 
> "Then you connect the namespace via veth-pairs." Didn't get the
> namespace and making veth-pairs part.
> 
> Anyways, I'll be certain to see what I can do with the code itself.
> 
> Thanks and regards,
> Kaushik
> 
> Thanks and Regards,
> 
> Kaushik NP
> LI | Tw | FB
> SAP Ambassador,
> General Secretary, Computer Society
> Team IEEE UVCE,
> 3rd Year Undergraduate Student,
> University Visvesvaraya College of Engineering,
> Bangalore, IN
> 
> 
> On Wed, Oct 12, 2016 at 10:19 PM, Kaushik N P <kaushik.np.in@ieee.org> wrote:
> > Hello,
> >
> > @Linus, I am a bit new to this and haven't much exposure to compiling
> > kernels and all. I will try out and see what I can do with it, but a little
> > more explanation would help a lot.
> >
> > "Then you connect the namespace via veth-pairs." Didn't get the namespace
> > and making veth-pairs part.
> >
> > Anyways, I'll be certain to see what I can do with the code itself.
> >
> > Thanks and regards,
> > Kaushik
> >
> >
> > On Oct 11, 2016 4:06 PM, "Linus Lüssing" <linus.luessing@c0d3.blue> wrote:
> >
> > 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-12 17:46 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
     [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 [this message]
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=20161012174646.GD10902@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