From: Cong Wang <amwang@redhat.com>
To: David Stevens <dlstevens@us.ibm.com>
Cc: "Bjørn Mork" <bjorn@mork.no>,
"David Miller" <davem@davemloft.net>,
netdev@vger.kernel.org, netdev-owner@vger.kernel.org,
yoshfuji@linux-ipv6.org
Subject: Re: [Patch net-next] ipv6: separate out procfs code from mcast.c
Date: Wed, 24 Apr 2013 13:26:24 +0800 [thread overview]
Message-ID: <1366781184.3849.10.camel@cr0> (raw)
In-Reply-To: <OF8FAF5C90.C6D83D68-ON85257B56.005F1762-85257B56.005FCD21@us.ibm.com>
On Tue, 2013-04-23 at 13:26 -0400, David Stevens wrote:
> BTW, another thing I thought of after I sent my patch comments -- you
> also need to consider the state of net.ipv6.bindv6only. When v6 is
> enabled, you use one socket for v4 and v6, but if bindv6only=1, you
> actually need a separate socket for v4 receives. If you want to support
> both v4 and v6 with bindv6only=1, you need two sockets. Or even if you
> want to support v4-only VXLAN and the sysadmin has set bindv6only=1.
>
Good point!
Actually the initial version of my patch did use two sockets for v4 and
v6. I am adding this to my TODO list.
Thanks!
next prev parent reply other threads:[~2013-04-24 5:27 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-23 7:07 [Patch net-next] ipv6: separate out procfs code from mcast.c Cong Wang
2013-04-23 7:11 ` David Miller
2013-04-23 7:15 ` Cong Wang
2013-04-23 7:18 ` David Miller
2013-04-23 7:30 ` Cong Wang
2013-04-23 7:36 ` David Miller
2013-04-23 7:41 ` Cong Wang
2013-04-23 12:33 ` Bjørn Mork
2013-04-23 16:13 ` Ben Hutchings
2013-04-24 3:33 ` Cong Wang
2013-04-23 17:26 ` David Stevens
2013-04-24 5:26 ` Cong Wang [this message]
2013-04-24 3:29 ` 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=1366781184.3849.10.camel@cr0 \
--to=amwang@redhat.com \
--cc=bjorn@mork.no \
--cc=davem@davemloft.net \
--cc=dlstevens@us.ibm.com \
--cc=netdev-owner@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=yoshfuji@linux-ipv6.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.