From: Christopher Nielsen <cnielsen@pobox.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] Issues with 2 networks, fs server, and namespaces
Date: Fri, 21 Aug 2009 15:14:50 -0700 [thread overview]
Message-ID: <e0ac85f90908211514w585251bera5bfc019f92645cc@mail.gmail.com> (raw)
In-Reply-To: <9ab217670908211459n796751ecpa28ab4adcc423f04@mail.gmail.com>
Certainly. No problem.
Yes, just bind #l1 to /net, assign it an IP addr on that private
network, and put a route in the routing table for good measure. Though
that last step may not be entirely necessary.
-Chris
On Fri, Aug 21, 2009 at 14:59, Devon H. O'Dell<devon.odell@gmail.com> wrote:
> 2009/8/21 Devon H. O'Dell <devon.odell@gmail.com>:
>> 2009/8/21 Christopher Nielsen <cnielsen@pobox.com>:
>>> You don't need a second IP stack. You can run both interfaces on the
>>> same IP stack and routing will just work. That's how I did it when I
>>> had a similar setup.
>
> Wait, I misread your explanation. Would you care to explain more about
> that? Is that just binding '#l1' into /net?
>
> --dho
>
>
--
Christopher Nielsen
"They who can give up essential liberty for temporary
safety, deserve neither liberty nor safety." --Benjamin Franklin
next prev parent reply other threads:[~2009-08-21 22:14 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-21 21:07 Devon H. O'Dell
2009-08-21 21:50 ` Christopher Nielsen
2009-08-21 21:58 ` Devon H. O'Dell
2009-08-21 21:59 ` Devon H. O'Dell
2009-08-21 22:14 ` Christopher Nielsen [this message]
2009-08-21 22:04 ` Noah Evans
2009-08-21 23:21 ` Devon H. O'Dell
2009-08-21 23:53 ` Devon H. O'Dell
2009-08-22 0:24 ` Devon H. O'Dell
2009-08-22 1:01 ` erik quanstrom
2009-08-22 0:52 ` erik quanstrom
2009-08-22 1:08 ` erik quanstrom
2009-08-22 1:09 ` Devon H. O'Dell
2009-08-22 1:00 ` erik quanstrom
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=e0ac85f90908211514w585251bera5bfc019f92645cc@mail.gmail.com \
--to=cnielsen@pobox.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).