From: Vlad Yasevich <vladislav.yasevich@hp.com>
To: David Miller <davem@davemloft.net>
Cc: chuck.lever@oracle.com, tytso@mit.edu, Valdis.Kletnieks@vt.edu,
arvidjaar@mail.ru, rjw@sisk.pl, netdev@vger.kernel.org,
bonding-devel@lists.sourceforge.net, jamagallon@ono.com,
linux-kernel@vger.kernel.org
Subject: Re: 2.6.29 regression? Bonding tied to IPV6 in 29-rc5
Date: Wed, 18 Feb 2009 20:11:06 -0500 [thread overview]
Message-ID: <499CB1AA.70801@hp.com> (raw)
In-Reply-To: <20090218.141431.103832064.davem@davemloft.net>
David Miller wrote:
> From: Vlad Yasevich <vladislav.yasevich@hp.com>
> Date: Wed, 18 Feb 2009 13:33:42 -0500
>
>> Would a module parameter that disables ipv6 or at least addrconf be
>> enough of a solution?
>
> We have it, it's just that (as others have stated) it doesn't
> prevent IPV6 sockets from being openned by applications.
>
Is that what people really want to block?
Or do they want to prevent the use of IPv6 in environments where
IPv6 is not supported? If it's this case, then simply not configuring
any IPv6 addresses on the system interfaces will make it seem as if
IPv6 is not there.
Without IPv6 addresses, AF_INET6 sockets are the same as AF_INET.
I really see no reason to block them. Any legacy apps that people
might worry about don't use this type socket any way.
One doesn't even need to worry about processing IPv6 traffic,
since the system would never join any IPv6 multicast groups and thus
would never see 99% of the traffic.
-vlad
next prev parent reply other threads:[~2009-02-19 1:11 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <alpine.LFD.2.00.0902131413120.3179@localhost.localdomain>
[not found] ` <20090217095232.5da06b9f@werewolf.home>
2009-02-17 17:01 ` 2.6.29 regression? Bonding tied to IPV6 in 29-rc5 Andrey Borzenkov
2009-02-17 18:17 ` Andrey Borzenkov
2009-02-17 20:08 ` [Bonding-devel] " Jay Vosburgh
2009-02-17 22:49 ` David Miller
2009-02-17 20:10 ` Brian Haley
2009-02-17 20:56 ` Thomas Backlund
2009-02-17 21:06 ` [Bonding-devel] " Jay Vosburgh
2009-02-17 21:49 ` Brian Haley
2009-02-17 22:24 ` Jay Vosburgh
2009-03-04 11:46 ` Jan Engelhardt
2009-02-17 22:30 ` Nicolas de Pesloüan
2009-02-17 22:54 ` David Miller
2009-02-17 22:51 ` David Miller
2009-02-17 22:29 ` David Miller
2009-02-18 4:41 ` Valdis.Kletnieks
2009-02-18 5:29 ` David Miller
2009-02-18 5:55 ` Roland Dreier
2009-02-18 13:55 ` Theodore Tso
2009-02-18 16:24 ` Chuck Lever
2009-02-18 18:33 ` Vlad Yasevich
2009-02-18 19:57 ` Brian Haley
2009-02-18 21:21 ` John Dykstra
2009-02-18 21:29 ` [Bonding-devel] " Stephen Hemminger
2009-02-19 13:32 ` Herbert Xu
2009-02-18 22:14 ` David Miller
2009-02-19 1:11 ` Vlad Yasevich [this message]
2009-02-19 13:29 ` Herbert Xu
2009-02-18 6:55 ` Frank Blaschka
2009-02-19 18:15 ` Randy Dunlap
2009-02-19 18:19 ` Andrey Borzenkov
2009-02-19 18:20 ` Jay Vosburgh
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=499CB1AA.70801@hp.com \
--to=vladislav.yasevich@hp.com \
--cc=Valdis.Kletnieks@vt.edu \
--cc=arvidjaar@mail.ru \
--cc=bonding-devel@lists.sourceforge.net \
--cc=chuck.lever@oracle.com \
--cc=davem@davemloft.net \
--cc=jamagallon@ono.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=rjw@sisk.pl \
--cc=tytso@mit.edu \
/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).