From: michi1@michaelblizek.twilightparadox.com
To: netdev@vger.kernel.org, davem@davemloft.net
Subject: [RFC] Connection oriented routing
Date: Sat, 27 Nov 2021 10:27:41 +0100 [thread overview]
Message-ID: <20211127092741.GA2599@grml> (raw)
Hi!
I have been deleloping a connection oriented layer 3+4 protocol mostly for
wifi mesh networks. Its main difference is that "tcp" connections are not
end-to-end but between neighboring routers instead.
It runs ane you can test it, if you want, but it is not ready for merging or
actual use yet. Some unfinished tasks include:
- cleanups
- performance: lots of things which can be improved
- keepalive
- interfaces for configuration+statistics
- move to a newer upstream kernel
- I am not sure how some of the in-kernel interfaces work. More specifically,
I am not sure which "struct proto/proto_ops" functions need to be
implemented and how ho avoid race conditions when accessing various
variables. Also, network namespaces are not handled yet either. I will look
closer into this when the other issues are resolved in order to avoid
upstream changes breaking it in the mean time.
Website: https://michaelblizek.twilightparadox.com/projects/cor/index.html
Kernel repo: https://repo.or.cz/w/cor.git?a=tree
Userspace tools: https://repo.or.cz/w/corutils.git
Please share your thoughts!
-Michi
next reply other threads:[~2021-11-27 9:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-27 9:27 michi1 [this message]
-- strict thread matches above, loose matches on Subject: below --
2011-01-06 7:34 [RFC] Connection oriented routing Michael Blizek
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=20211127092741.GA2599@grml \
--to=michi1@michaelblizek.twilightparadox.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).