From: michi1@michaelblizek.twilightparadox.com (michi1 at michaelblizek.twilightparadox.com)
To: kernelnewbies@lists.kernelnewbies.org
Subject: Open source networking Projects
Date: Fri, 29 Nov 2013 17:46:57 +0100 [thread overview]
Message-ID: <20131129164656.GA4112@grml> (raw)
In-Reply-To: <5297F60E.1060608@meetinghouse.net>
Hi!
On 21:03 Thu 28 Nov , Miles Fidelman wrote:
> michi1 at michaelblizek.twilightparadox.com wrote:
> > Hi!
> >
> > On 18:15 Tue 26 Nov , Robert Clove wrote:
> >> I am a new (sort of fresher) and want to do some work in networking domain
> >> like network device driver or some changes that increase the network
> >> performance and all.
> >>
> >> Could you please suggest me some projects if they are new it would be good
> >> and easy to understand.
> > I am programing a layer 3+4 network protocol for mesh networks. Take a look at
> > http://michaelblizek.twilightparadox.com . I would especially like to see
> > somebody improve the user space routing daemon (in the corutils repository).
> >
> >
> Isn't this just a bit of putting the cart before the horse? There's
> nothing there that looks like a design document, architecture, or
> protocol spec - it seems a bit early to think about coding a routing daemon.
Well, the website is pretty much a design document. The protocol is partially
documented on the website too and you can find more details if you open the
net/cor/cor.h file. Also, if there is something you want to know, feel free to
ask. I try to keep the docs readable by not adding too much irrelevant stuff
and without feedback it is hard to know whether something is relevant or not.
-Michi
next prev parent reply other threads:[~2013-11-29 16:46 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-26 12:45 Open source networking Projects Robert Clove
2013-11-28 18:22 ` michi1 at michaelblizek.twilightparadox.com
2013-11-29 2:03 ` Miles Fidelman
2013-11-29 16:46 ` michi1 at michaelblizek.twilightparadox.com [this message]
2013-11-29 17:14 ` Miles Fidelman
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=20131129164656.GA4112@grml \
--to=michi1@michaelblizek.twilightparadox.com \
--cc=kernelnewbies@lists.kernelnewbies.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).