From: Ethan Grammatikidis <eekee57@fastmail.fm>
To: 9fans@9fans.net
Cc: comp.os.plan9@googlegroups.com
Subject: Re: [9fans] Parallels 6/7 and Q(qemu for mac)
Date: Thu, 22 Sep 2011 11:55:23 +0100 [thread overview]
Message-ID: <20110922115523.42c8ced2@kolari.ethans.dre.am> (raw)
In-Reply-To: <9308466.1350.1316527827694.JavaMail.geo-discussion-forums@vbbfh29>
On Tue, 20 Sep 2011 14:28:52 GMT
mccoyst@gmail.com wrote:
> Networking in Q doesn't work on OSX because qemu needs a TUN/TAP bridge to get off the host. OSX doesn't come with the tools to set it up as far as I can tell — some searching I did a while back made it seem like older versions of OSX may have had the appropriate programs, but nothing I could find described getting qemu working on 10.5 or up. I found this http://tuntaposx.sourceforge.net/ , but was already too frustrated to put the effort into getting it to work with qemu.
>
I have vague memories of the software networking working under Q. Such
memories may be delusional but I don't see why it wouldn't. You might
have a bit of trouble running a server with the software stack due the
port<1024 thing. I ran a cpu server in qemu under Linux after I patched
Linux to allow user programs to use low ports, (Trivial patch,) or
there is a simple iptables workaround. (There's an iptables script in
mycroftiv's bundles.) There is a way of doing such port-mapping in OS X
but I never got around to it so couldn't tell you how. It might even be
a port of pf but you have to install some user-space tools which don't
ship with the system.
next prev parent reply other threads:[~2011-09-22 10:55 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-20 0:56 stephano zanzin
2011-09-20 1:30 ` Lyndon Nerenberg
2011-09-20 4:23 ` Adrian Tritschler
2011-09-20 5:12 ` geoff
2011-09-20 7:37 ` Bakul Shah
2011-09-20 14:28 ` mccoyst
2011-09-22 10:55 ` Ethan Grammatikidis [this message]
[not found] <CAEAMzUEn5ZDbqccnek7sgACWLXRnL0HJy_xPCFh95zSyok65pQ@mail.gmail.c>
2011-09-20 0:59 ` 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=20110922115523.42c8ced2@kolari.ethans.dre.am \
--to=eekee57@fastmail.fm \
--cc=9fans@9fans.net \
--cc=comp.os.plan9@googlegroups.com \
/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).