9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: "Devon H. O'Dell" <devon.odell@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] Plan 9 on Routers?
Date: Wed, 25 Mar 2009 11:59:54 -0400	[thread overview]
Message-ID: <9ab217670903250859q5b53e652obb65a78b8ce75429@mail.gmail.com> (raw)
In-Reply-To: <20090325154721.1E2785B29@mail.bitblocks.com>

2009/3/25 Bakul Shah <bakul+plan9@bitblocks.com>:
> On Wed, 25 Mar 2009 09:00:58 EDT "Devon H. O'Dell" <devon.odell@gmail.com>  wrote:
>>                                                  While creating an
>> entire routing suite (such as Zebra/Quagga) is probably outside of the
>> scope of a 3 month project, I think a diligent student could probably
>> do something useful with OSPF or BGP. It's entirely possible that a 3
>> month project could consist of analyzing Plan 9's ability to function
>> in this environment and making changes to facilitate the
>> implementation of routing protocols. Or creating a packet filter.
>
> Thinking a bit more about it, extending /net/iproute to allow
> routing metrics may be what is needed for porting/building
> something like openospfd or openbgpd.  Basically
> /net/{iproute,ipifc} etc need to do more or less what a
> routing socket does under *BSD (man 4 route).  Of course,
> there may be other things missing in the p9 IP stack that may
> get in the way but now I think porting something like
> openospfd in a summer is doable.

Yeah, that's what I meant to imply :) Thanks for clarifying that :)

--dho



  reply	other threads:[~2009-03-25 15:59 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-24 19:11 Rahul Murmuria
2009-03-24 19:35 ` [9fans] drawterm font Benjamin Huntsman
2009-03-24 19:52   ` erik quanstrom
2009-03-24 20:01   ` Russ Cox
2009-03-24 20:12     ` Benjamin Huntsman
2009-03-24 19:45 ` [9fans] Plan 9 on Routers? Devon H. O'Dell
2009-03-24 19:51   ` J.R. Mauro
2009-03-24 20:05   ` Rahul Murmuria
2009-03-24 20:33     ` J.R. Mauro
2009-03-24 21:35     ` Bakul Shah
2009-03-24 23:00       ` Rahul Murmuria
2009-03-24 23:20         ` erik quanstrom
2009-03-25  6:35           ` Rahul Murmuria
2009-03-25 10:41           ` Eris Discordia
2009-03-25 13:00         ` Devon H. O'Dell
2009-03-25 13:25           ` erik quanstrom
2009-03-25 13:31             ` Devon H. O'Dell
2009-03-25 15:47           ` Bakul Shah
2009-03-25 15:59             ` Devon H. O'Dell [this message]
2009-03-26  4:37           ` lucio
2009-03-26 13:26             ` Devon H. O'Dell
2009-03-24 19:58 ` erik quanstrom
2009-03-25 15:09 ` jetskean
2009-03-25 15:40   ` andrey mirtchovski

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=9ab217670903250859q5b53e652obb65a78b8ce75429@mail.gmail.com \
    --to=devon.odell@gmail.com \
    --cc=9fans@9fans.net \
    /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).