From: Michael Blizek <michi1@michaelblizek.twilightparadox.com>
To: netdev@vger.kernel.org
Cc: davem@davemloft.net, chambilkethakur@gmail.com
Subject: [RFC] Connection oriented routing
Date: Thu, 6 Jan 2011 08:34:08 +0100 [thread overview]
Message-ID: <20110106073408.GA2017@michaelblizek.twilightparadox.com> (raw)
Hi!
I am implementing a connection oriented source routed layer 3/4 protocol for
zero administration (community/mesh) networks. It takes care of things like
fair bandwidth allocation and has higher security/privacy so that it can really
run without administration. It is basically running, but not entirely stable
and with some loose ends. You can find some more info here:
http://michaelblizek.twilightparadox.com/projects/cor/index.html
git repo (based on 2.6.28):
http://repo.or.cz/w/cor.git?a=tree
My 2 previous queries to netdev:
http://article.gmane.org/gmane.linux.network/80232
http://article.gmane.org/gmane.linux.network/144915
-Michi
next reply other threads:[~2011-01-06 7:53 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-06 7:34 Michael Blizek [this message]
-- strict thread matches above, loose matches on Subject: below --
2021-11-27 9:27 [RFC] Connection oriented routing michi1
2009-11-26 8:34 Michael Blizek
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=20110106073408.GA2017@michaelblizek.twilightparadox.com \
--to=michi1@michaelblizek.twilightparadox.com \
--cc=chambilkethakur@gmail.com \
--cc=davem@davemloft.net \
--cc=netdev@vger.kernel.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).