From mboxrd@z Thu Jan 1 00:00:00 1970 From: Michael Roth Subject: Re: [Qemu-devel] [PATCH v3 9/9] net: support to include ipv6 address by brackets Date: Tue, 13 Mar 2012 14:47:35 -0500 Message-ID: <20120313194735.GE3699@illuin> References: <20120306224330.24264.9494.stgit@dhcp-8-167.nay.redhat.com> <20120306224857.24264.88329.stgit@dhcp-8-167.nay.redhat.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: aliguori@us.ibm.com, kvm@vger.kernel.org, quintela@redhat.com, jasowang@redhat.com, qemu-devel@nongnu.org, owasserm@redhat.com, laine@redhat.com To: Amos Kong Return-path: Received: from mail-pz0-f52.google.com ([209.85.210.52]:54517 "EHLO mail-pz0-f52.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754340Ab2CMTrl (ORCPT ); Tue, 13 Mar 2012 15:47:41 -0400 Received: by dadp12 with SMTP id p12so1456376dad.11 for ; Tue, 13 Mar 2012 12:47:41 -0700 (PDT) Content-Disposition: inline In-Reply-To: <20120306224857.24264.88329.stgit@dhcp-8-167.nay.redhat.com> Sender: kvm-owner@vger.kernel.org List-ID: On Wed, Mar 07, 2012 at 06:48:57AM +0800, Amos Kong wrote: > That method of representing an IPv6 address with a port is I'm not sure what "that" is referencing. I assumed the previous patch but the representation seems to be the same? > discouraged because of its ambiguity. Referencing to RFC5952, > the recommended format is: > > [2312::8274]:5200 > > For IPv6 brackets must be mandatory if you require a port. > > test status: Successed > listen side: qemu-kvm .... -incoming tcp:[2312::8274]:5200 > client side: qemu-kvm ... > (qemu) migrate -d tcp:[2312::8274]:5200 > > Signed-off-by: Amos Kong > --- > net.c | 6 ++++++ > 1 files changed, 6 insertions(+), 0 deletions(-) > > diff --git a/net.c b/net.c > index d6ce1fa..499ed1d 100644 > --- a/net.c > +++ b/net.c > @@ -88,6 +88,12 @@ static int get_str_sep(char *buf, int buf_size, const char **pp, int sep) > if (!p1) > return -1; > len = p1 - p; > + /* remove brackets which includes hostname */ > + if (*p == '[' && *(p1-1) == ']') { > + p += 1; > + len -= 2; > + } Sorry, looking again I guess net/slirp.c actually has it's own copy of get_str_sep(), so modifying this doesn't look like it would break anything currently. It might cause some confusion though :). And I think the special handling for brackets should be done in parse_host_port_info() since get_str_sep() is pretty generically named. > + > p1++; > if (buf_size > 0) { > if (len > buf_size - 1) > >