Hmmm I can get it working OK with manually added routes and ping, but babel
is acting weird. I've got 2 nodes hooked up, but only one of them is
receiving the other's hellos. I'll be at the Omni tomorrow to work on this
and an email server.
-Jehan
On Sat, Apr 22, 2017 at 10:46 AM, Jehan Tremback <jehan.tremback(a)gmail.com>
wrote:
I'm actually setting up a test scenario with babel
right now.
Unfortunately the dependency story with shell is nonexistent. I'll post the
babel-testing code here when it's ready. I think that it should be
relatively easy to fit everything into the startup script for each node. If
stuff gets really repetitive, maybe we can add some sort of global startup
script that lets you template in values having to do with each node.
-Jehan
On Fri, Apr 21, 2017 at 7:42 AM, Jorrit Poelen <jhpoelen(a)xs4all.nl> wrote:
Cool! Would it be an idea to make babeld-lab
depend on this project and
provide an example of how to use it to test babeld?
-jorrit
On Thu, 2017-04-20 at 20:45 -0700, Jehan Tremback wrote:
I was working on some changes to the babeld-lab repo. I ended up not
using any of the existing code, but learning from the concepts, so I put
the new code in its own repo:
https://github.com/sudomesh/network-lab
It reads a JSON network graph format defining nodes and edges and uses it
to create nodes in network namespaces linked by virtual ethernet edges of
differing quality (babeld-lab connects all nodes to one switch).
Each edge has configurable latency and packet loss in both directions
provided by tc netem.
Each node can run arbitrary scripts in its namespace on startup. These
scripts could be used to start a routing protocol.
-Jehan
_______________________________________________
mesh mailing listmesh@lists.sudoroom.orghttps://sudoroom.org/lists/listinfo/mesh
_______________________________________________
mesh mailing list
mesh(a)lists.sudoroom.org
https://sudoroom.org/lists/listinfo/mesh