qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Samuel Thibault <samuel.thibault@gnu.org>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: "J. Kiszka" <jan.kiszka@siemens.com>,
	QEMU Developers <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [PULL 0/5] ipv4-only and ipv6-only support
Date: Thu, 31 Mar 2016 13:44:52 +0200	[thread overview]
Message-ID: <20160331114452.GO2636@var.bordeaux.inria.fr> (raw)
In-Reply-To: <CAFEAcA-j_gX4QrwZxqTh_pioFKH4LHxdqtUcw2UovKLFvhH89A@mail.gmail.com>

Peter Maydell, on Thu 31 Mar 2016 12:30:24 +0100, wrote:
> On 31 March 2016 at 10:20, Samuel Thibault <samuel.thibault@ens-lyon.org> wrote:
> >   http://people.debian.org/~sthibault/qemu.git tags/samuel-thibault-2
> >
> > for you to fetch changes up to c99751f2a711e9eecf60901520c6d4197bdaf9b4:
> >
> >   slirp: Add RDNSS advertisement (2016-03-31 11:18:13 +0200)
> >
> > ----------------------------------------------------------------
> > slirp updates (2)
> >
> > ----------------------------------------------------------------
> > Samuel Thibault (5):
> >       slirp: Allow disabling IPv4 or IPv6
> >       slirp: Split get_dns_addr
> >       slirp: Add dns6 resolution
> >       slirp: Support link-local DNS addresses
> >       slirp: Add RDNSS advertisement
> 
> 
> Some of these look suspiciously "new feature" -- can you provide
> a brief justification for why they should go in after hardfreeze, please?

The first commit, at least, would very probably be welcome: now that
ipv6 will be enabled by default, this may disturb some people for
whatever reason, so they may want to have a way to disable it.

Also, some people may want to start testing ipv6-only setups. The 4
subsequent commits are useful in such setups, to automatically setup the
DNS server address. It is not strictly needed, since the user can set by
hand inside the guest an external DNS server IPv6 address to be used.

Samuel

  reply	other threads:[~2016-03-31 11:44 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-31  9:20 [Qemu-devel] [PULL 0/5] ipv4-only and ipv6-only support Samuel Thibault
2016-03-31  9:20 ` [Qemu-devel] [PULL 1/5] slirp: Allow disabling IPv4 or IPv6 Samuel Thibault
2016-03-31  9:20 ` [Qemu-devel] [PULL 2/5] slirp: Split get_dns_addr Samuel Thibault
2016-03-31  9:20 ` [Qemu-devel] [PULL 3/5] slirp: Add dns6 resolution Samuel Thibault
2016-03-31  9:20 ` [Qemu-devel] [PULL 4/5] slirp: Support link-local DNS addresses Samuel Thibault
2016-03-31  9:20 ` [Qemu-devel] [PULL 5/5] slirp: Add RDNSS advertisement Samuel Thibault
2016-03-31 11:30 ` [Qemu-devel] [PULL 0/5] ipv4-only and ipv6-only support Peter Maydell
2016-03-31 11:44   ` Samuel Thibault [this message]
2016-03-31 11:49     ` Vasiliy Tolstov
2016-03-31 11:57       ` Samuel Thibault
2016-03-31 12:03         ` Vasiliy Tolstov
2016-03-31 12:04           ` Vasiliy Tolstov
2016-03-31 12:14             ` Samuel Thibault
2016-03-31 12:20               ` Vasiliy Tolstov
2016-03-31 12:10           ` Samuel Thibault
2016-03-31 12:20             ` Vasiliy Tolstov
2016-03-31 12:47 ` Peter Maydell
2016-03-31 12:51   ` Samuel Thibault
2016-03-31 14:11     ` Peter Maydell
2016-03-31 14:19       ` Samuel Thibault
2016-03-31 14:44         ` Peter Maydell
2016-03-31 14:49           ` Samuel Thibault

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=20160331114452.GO2636@var.bordeaux.inria.fr \
    --to=samuel.thibault@gnu.org \
    --cc=jan.kiszka@siemens.com \
    --cc=peter.maydell@linaro.org \
    --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).