9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Rahul Murmuria <rahul.is.also@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 19:00:54 -0400	[thread overview]
Message-ID: <9511f83e0903241600v21f4681bj846bbb6e8f69cc31@mail.gmail.com> (raw)
In-Reply-To: <20090324213537.268005B05@mail.bitblocks.com>

So, the bottom line is no one has really explored Plan 9 on routers.

It seems that /net/iproute is where I can start. It has a complete
interface for editing routes. What we need is a user space script that
implements routing, like http://www.openbgp.org/ does on OpenBSD.
Except that, it will only have to send add, delete and flush control
messages to the iproute file.

This is not quite as powerful as most routers do. I remember Mauro
mentioning that Cisco IOS provides, among other things, a more
fine-grained control over passwords and information-hiding to the
per-interface level. I wonder how that would be incorporated into Plan
9. Could namespaces come into picture here?

@ Devon:
About Packet Classification. I read that iptables is not needed on
Plan 9 because its "mount /net over the network" concept achieved
anonymity or transparency -- something along those lines. "There are
no logs about who is sending what, and that is a good thing".

I am not sure where exactly the packet classification idea fits in. I
read in the /proc documents that /proc/net provides useful information
about the network stack. There is this ip_conntrack which is used to
list / track network connections. I wonder what we would need to get
packet information and perform filtering. Is it desirable to get that
filtering to work if it already does not exist?


Thank you all for replying so far!
--
Rahul Murmuria



  reply	other threads:[~2009-03-24 23:00 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 [this message]
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=9511f83e0903241600v21f4681bj846bbb6e8f69cc31@mail.gmail.com \
    --to=rahul.is.also@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).