From: Marek Lindner <lindner_marek@yahoo.de>
To: b.a.t.m.a.n@lists.open-mesh.org
Subject: [B.A.T.M.A.N.] multiple mesh clouds
Date: Sat, 10 Jul 2010 16:06:27 +0200 [thread overview]
Message-ID: <201007101606.27989.lindner_marek@yahoo.de> (raw)
Hi folks,
we already had quite some patches going into batman-adv to allow concurrent
meshes on the same device. I'm happy to announce that this is the final batch
which will unlock this feature.
As you can see it is a lot of code that needs to be reviewed and tested. On my
testbed it works quite well but nearly all subsystems are affected, so I expect
more bugs to materialize. Please give it a try and let me know what you think.
Regards,
Marek
next reply other threads:[~2010-07-10 14:06 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-10 14:06 Marek Lindner [this message]
2010-07-10 14:06 ` [B.A.T.M.A.N.] [PATCH 1/3] batman-adv: attach each hard-interface to a soft-interface Marek Lindner
2010-07-10 14:06 ` [B.A.T.M.A.N.] [PATCH 2/3] batman-adv: multiple mesh clouds Marek Lindner
2010-07-10 14:06 ` [B.A.T.M.A.N.] [PATCH 3/3] batctl: support for " Marek Lindner
2010-07-11 6:26 ` [B.A.T.M.A.N.] " Sven Eckelmann
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=201007101606.27989.lindner_marek@yahoo.de \
--to=lindner_marek@yahoo.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).