qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Stefan Hajnoczi <stefanha@gmail.com>
To: Ivan Shmakov <oneingray@gmail.com>
Cc: Jan Kiszka <jan.kiszka@siemens.com>, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] IPv6 support for -net user?
Date: Thu, 30 Aug 2012 08:23:51 +0100	[thread overview]
Message-ID: <20120830072351.GA6814@stefanha-thinkpad.localdomain> (raw)
In-Reply-To: <86wr0i58zt.fsf@gray.siamics.net>

On Wed, Aug 29, 2012 at 04:43:18PM +0700, Ivan Shmakov wrote:
> 	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.

Jan Kiszka is the -net user maintainer, I have CCed him.

I'm not aware of work to add IPv6 support to slirp.  Someone would have
to step up and submit patches :).

You can still do unprivileged IPv6 networking with external DHCPv6, etc
software:

  $ qemu -netdev socket,id=socket0,listen=127.0.0.1:1234 \
         -device virtio-net-pci,netdev=socket0

The socket netdev tunnels traffic over a TCP or UDP socket.  For TCP it
prefixes each packet with the big-endian uint32_t length.  For UDP no
length header is necessary because packet boundaries are preserved.

You could write your own code or find something that can speak with
QEMU's -netdev socket.

Stefan

  reply	other threads:[~2012-08-30  8:04 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-29  9:43 [Qemu-devel] IPv6 support for -net user? Ivan Shmakov
2012-08-30  7:23 ` Stefan Hajnoczi [this message]
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=20120830072351.GA6814@stefanha-thinkpad.localdomain \
    --to=stefanha@gmail.com \
    --cc=jan.kiszka@siemens.com \
    --cc=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 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).