From: yan cui <ccuiyyan@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: [9fans] [GSOC] port forwarding
Date: Thu, 12 Jun 2014 00:52:33 -0400 [thread overview]
Message-ID: <CAAVq3rnQmJ4NrP15_R4dnNVDmqQXXKynP-rO2M+-z-K3Z4Xj-Q@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 746 bytes --]
Hi all,
I run into a situation that may need to setup the port forwarding rule,
but not quite sure. Hope you guys can provide some suggestions. Thanks in
advance!
Basically, I have a virtual machine (KVM) working as plan9's fs+auth
server.
The auth+fs server listens the port 564 and uses NAT (network address
translation) to connect to the Internet.
The virtual machine runs on a Linux box. On the same Linux machine,
I use qemu to execute an enhanced plan9 cpu server (with new features
included). The qemu instance needs to boot from the auth+fs server.
My question is, to make the boot successful, do I need to set any port
forwarding rules? If so, how to do that?
--
Think big; Dream impossible; Make it happen.
[-- Attachment #2: Type: text/html, Size: 1006 bytes --]
next reply other threads:[~2014-06-12 4:52 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-12 4:52 yan cui [this message]
2014-06-12 7:29 ` Nick Owens
2014-06-12 7:53 ` Charles Forsyth
2014-06-12 9:56 ` Aram Hăvărneanu
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=CAAVq3rnQmJ4NrP15_R4dnNVDmqQXXKynP-rO2M+-z-K3Z4Xj-Q@mail.gmail.com \
--to=ccuiyyan@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).