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
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
Actually, for some basic tests you could skip the netns part and just use veth directly:
$ ip link add veth0 type veth peer name veth1 $ batctl -m bat0 if add veth0 $ batctl -m bat1 if add veth1 $ ip link set up dev veth0 $ ip link set up dev veth1 $ ip link set up dev bat0 $ ip link set up dev bat1
And then check with "batctl -m bat{0,1} originators" for instance.
Cheers, Linus
On Wed, Oct 12, 2016 at 07:46:46PM +0200, Linus Lüssing wrote:
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
b.a.t.m.a.n@lists.open-mesh.org
-
Kaushik N P -
Linus Lüssing