From: Thomas Huth <thuth@redhat.com>
To: Markus Armbruster <armbru@redhat.com>,
Samuel Thibault <samuel.thibault@gnu.org>
Cc: jan.kiszka@siemens.com, jasowang@redhat.com, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] slirp: Allow to disable IPv4 or IPv6
Date: Tue, 22 Mar 2016 09:02:31 +0100 [thread overview]
Message-ID: <56F0FC17.5000805@redhat.com> (raw)
In-Reply-To: <87d1qnt0x2.fsf@blackfin.pond.sub.org>
On 22.03.2016 08:41, Markus Armbruster wrote:
> Samuel Thibault <samuel.thibault@gnu.org> writes:
>
>> Markus Armbruster, on Mon 21 Mar 2016 08:33:52 +0100, wrote:
>>> Samuel Thibault <samuel.thibault@ens-lyon.org> writes:
>>>> Make net=0.0.0.0 disable IPv4 and ip6-net=:: disable IPv6, so the user can
>>>> setup IPv4-only and IPv6-only network environments.
>>>
>>> Do "net=" and "ip6-net=" mean anything useful? If not, wouldn't that be
>>> a more natural way to switch off than abusing the wildcard address?
>>
>> An empty parameter looks odd to me. 0.0.0.0 is used e.g. by ifconfig to
>> disable an interface, that's why I thought about it. Perhaps an even
>> better way would be net=none and ip6-net=none?
>
> An empty string as parameter value looks just fine to me. "none" would
> be fine, too, because it's not a valid value so far. I acknowledge the
> precedence for abusing the wildcard address. Pick something you like.
I like the "=none" syntax.
Thomas
next prev parent reply other threads:[~2016-03-22 8:02 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-20 11:39 [Qemu-devel] [PATCH] slirp: Allow to disable IPv4 or IPv6 Samuel Thibault
2016-03-20 13:32 ` Samuel Thibault
2016-03-21 7:33 ` Thomas Huth
2016-03-21 7:33 ` Markus Armbruster
2016-03-21 9:02 ` Samuel Thibault
2016-03-21 9:44 ` Markus Armbruster
2016-03-21 23:55 ` Samuel Thibault
2016-03-22 7:41 ` Markus Armbruster
2016-03-22 8:02 ` Thomas Huth [this message]
2016-03-22 21:46 ` Samuel Thibault
2016-03-23 10:01 ` Markus Armbruster
2016-03-23 10:13 ` Daniel P. Berrange
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=56F0FC17.5000805@redhat.com \
--to=thuth@redhat.com \
--cc=armbru@redhat.com \
--cc=jan.kiszka@siemens.com \
--cc=jasowang@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=samuel.thibault@gnu.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).