From: Ivan Shmakov <oneingray@gmail.com>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] IPv6 support for -net user?
Date: Wed, 29 Aug 2012 16:43:18 +0700 [thread overview]
Message-ID: <86wr0i58zt.fsf@gray.siamics.net> (raw)
I'm writing an iPXE mini-HOWTO (in Russian), using QEMU and
-net user in examples (so that they're runnable by unprivileged
users.)
However, the QEMU documentation [1] seems to suggest that only
IPv4 is implemented for -net user, which made me curious on
whether the IPv6 support is planned to be added anytime soon?
Personally, I'm interested mostly in QEMU sending router
(prefix) advertisements to the “guest”, and forwarding TCP and
UDP traffic, although support for recursive DNS discovery and
DHCPv6 may also be nice to have.
TIA.
PS. I hope to announce the mini-HOWTO itself later this week, in both
the iPXE [2] and planning-ru@ [3] mailing lists.
[1] http://qemu.weilnetz.de/qemu-doc.html
[2] http://dir.gmane.org/gmane.network.ipxe.devel/
[3] http://dir.gmane.org/gmane.user-groups.foss.sfd.planning.ru/
--
FSF associate member #7257 http://sf-day.org/
next reply other threads:[~2012-08-29 9:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-29 9:43 Ivan Shmakov [this message]
2012-08-30 7:23 ` [Qemu-devel] IPv6 support for -net user? Stefan Hajnoczi
2012-08-30 9:19 ` Jan Kiszka
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=86wr0i58zt.fsf@gray.siamics.net \
--to=oneingray@gmail.com \
--cc=qemu-devel@nongnu.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.