9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: "J.R. Mauro" <jrm8005@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] Plan 9 on Routers?
Date: Tue, 24 Mar 2009 15:51:10 -0400	[thread overview]
Message-ID: <3aaafc130903241251q5338fe02g1031927d268393a8@mail.gmail.com> (raw)
In-Reply-To: <9ab217670903241245o1893f818vb01ae7e30ab4d8cf@mail.gmail.com>

On Tue, Mar 24, 2009 at 3:45 PM, Devon H. O'Dell <devon.odell@gmail.com> wrote:
> 2009/3/24 Rahul Murmuria <rahul.is.also@gmail.com>:
>> I was poking around for what it would take to get there. I found
>> this[1]. I am basically looking to have a way to do routing using Plan
>> 9. You can already do that on any standard Linux using Quagga[2] based
>> on GNU Zebra.
>>
>> Maybe there is a filesystem that exposes the kernel routing table to
>> user space for certain routing algorithm scripts to hack upon?
>>
>> My objective is to be able to implement a new routing protocol on a
>> router created using a standard computer with multiple NIC cards,
>> maybe on a model P2P type network? I also would love to see what
>> having /net on a router would enable us to do.
>>
>> Has anyone any experience with using Plan 9 on routers?
>
> Are you a student? This kind of stuff has interested me quite a bit in
> Plan 9 (though more from a packet classification standpoint -- read:
> firewalling), and it seems like a nifty project for GSoC.
>
> As far as I'm aware, there is nothing similar to the OSPF/BGP/RIP
> support directly in Plan 9. I am pretty sure Charles has written a RIP
> daemon that is in sources somewhere.

RIP is fairly simplistic, I wonder if Plan 9 exposes enough
information via /net to actually implement OSPF. You need to know
load-balancing, bandwidth and "distance" metrics that RIP doesn't care
about.

>
> --Devon
>
>> --
>> Rahul Murmuria
>>
>> [1] http://searchenterpriselinux.techtarget.com/tip/1,289483,sid39_gci1102834,00.html
>> [2] http://www.quagga.net/docs/quagga.html#SEC3
>>
>>
>
>



  reply	other threads:[~2009-03-24 19:51 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 [this message]
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
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=3aaafc130903241251q5338fe02g1031927d268393a8@mail.gmail.com \
    --to=jrm8005@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).