public inbox for netdev@vger.kernel.org 
 help / color / mirror / Atom feed
From: Stephen Hemminger <stephen@networkplumber•org>
To: Cong Wang <amwang@redhat•com>
Cc: netdev@vger•kernel.org
Subject: Re: [PATCH iproute2] vxlan: add ipv6 support
Date: Fri, 19 Apr 2013 08:26:23 -0700	[thread overview]
Message-ID: <20130419082623.0bc17afc@nehalam.linuxnetplumber.net> (raw)
In-Reply-To: <1366381212.5117.23.camel@cr0>

On Fri, 19 Apr 2013 22:20:12 +0800
Cong Wang <amwang@redhat•com> wrote:

> On Thu, 2013-04-18 at 15:57 -0700, Stephen Hemminger wrote:
> > On Wed, 17 Apr 2013 13:10:23 +0800
> > Cong Wang <amwang@redhat•com> wrote:
> > 
> > > +			if (!inet_pton(AF_INET, *argv, &gaddr)) {
> > > +				if (!inet_pton(AF_INET6, *argv, &gaddr6)) {
> > > +					fprintf(stderr, "Invalid address \"%s\"\n", *argv);
> > > +					return -1;
> > > +				} else if (!IN6_IS_ADDR_MULTICAST(&gaddr6))
> > > +					invarg("invald group address", *argv);
> > > +			} else if (!IN_MULTICAST(ntohl(gaddr)))
> > > +					invarg("invald group address", *argv);
> > 
> > Maybe using getaddrinfo would be better to allow symbolic names as well?
> 
> Yes, but I don't think many people use symbolic name for a multicast
> group?
> 
> Thanks.
> 

You can use AI_NUMERICHOST to avoid symbolic names.

  reply	other threads:[~2013-04-19 15:26 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-17  5:10 [Patch net-next v4 0/5] vxlan: add ipv6 support Cong Wang
2013-04-17  5:10 ` [Patch net-next v4 1/5] vxlan: defer vxlan init as late as possible Cong Wang
2013-04-17  5:10 ` [Patch net-next v4 2/5] ipv6: export ipv6_sock_mc_join and ipv6_sock_mc_drop Cong Wang
2013-04-17  5:10 ` [Patch net-next v4 3/5] vxlan: add ipv6 support Cong Wang
2013-04-17  8:15   ` Mike Rapoport
2013-04-17  9:57     ` Cong Wang
2013-04-17 10:36       ` Mike Rapoport
2013-04-17 13:18         ` Cong Wang
2013-04-17 16:34           ` Mike Rapoport
2013-04-18 14:34   ` Mike Rapoport
2013-04-19 11:35     ` Cong Wang
2013-04-17  5:10 ` [Patch net-next v4 4/5] vxlan: add scope_id support for ll addr Cong Wang
2013-04-18 13:36   ` Cong Wang
2013-04-19 11:14   ` David Stevens
2013-04-19 11:56     ` Cong Wang
2013-04-21 13:47     ` Cong Wang
2013-04-21 14:46       ` Bjørn Mork
2013-04-21 14:57         ` Cong Wang
2013-04-21 15:10           ` Bjørn Mork
2013-04-17  5:10 ` [Patch net-next v4 5/5] ipv6: Add generic UDP Tunnel segmentation Cong Wang
2013-04-18 17:23   ` Pravin Shelar
2013-04-19 11:30     ` Cong Wang
2013-04-17  5:10 ` [PATCH iproute2] vxlan: add ipv6 support Cong Wang
2013-04-18 22:55   ` Stephen Hemminger
2013-04-19 11:36     ` Cong Wang
2013-04-18 22:57   ` Stephen Hemminger
2013-04-19 14:20     ` Cong Wang
2013-04-19 15:26       ` Stephen Hemminger [this message]
  -- strict thread matches above, loose matches on Subject: below --
2013-09-03  3:33 [Patch " Cong Wang
2013-09-12  7:16 ` Cong Wang
2013-04-08  2:18 [Patch net-next v3 1/4] vxlan: defer vxlan init as late as possible Cong Wang
2013-04-08  2:18 ` [PATCH iproute2] vxlan: add ipv6 support Cong Wang
2013-04-05 12:16 [Patch net-next v2 1/4] vxlan: defer vxlan init as late as possible Cong Wang
2013-04-05 12:16 ` [PATCH iproute2] vxlan: add ipv6 support Cong Wang
2013-03-31  5:43 [Patch net-next v1 1/4] vxlan: defer vxlan init as late as possible Cong Wang
2013-03-31  6:17 ` [PATCH iproute2] vxlan: add ipv6 support Cong Wang

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=20130419082623.0bc17afc@nehalam.linuxnetplumber.net \
    --to=stephen@networkplumber$(echo .)org \
    --cc=amwang@redhat$(echo .)com \
    --cc=netdev@vger$(echo .)kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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