[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <alpine.LSU.2.00.0903041244400.31513@fbirervta.pbzchgretzou.qr>
Date: Wed, 4 Mar 2009 12:46:37 +0100 (CET)
From: Jan Engelhardt <jengelh@...ozas.de>
To: Jay Vosburgh <fubar@...ibm.com>
cc: Brian Haley <brian.haley@...com>,
Andrey Borzenkov <arvidjaar@...l.ru>, "J.A. Magall"@us.ibm.com,
ón <jamagallon@....com>, netdev@...r.kernel.org,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
"Rafael J. Wysocki" <rjw@...k.pl>, bonding-devel@...ts.sourcefor
Subject: Re: [Bonding-devel] 2.6.29 regression? Bonding tied to IPV6 in
29-rc5
On Tuesday 2009-02-17 23:24, Jay Vosburgh wrote:
>Brian Haley <brian.haley@...com> wrote:
>
> I don't see any reason to change the IPv4 bits;
>
>there won't ever be a case of ipv4 not being loaded,
I would not be so sure of that.
>>> To answer your question, I have come across this (aliasing ipv6
>>> to nothing in modprobe.conf to disable IPv6) from time to time, but
>>> didn't think of it when the NA code was added to bonding.
>>
>>So I guess I'll start hacking the above, unless someone has a better
>>suggestion.
>
> Well, I think this is pretty heinous, but I don't have a better
>idea at the moment.
IMO, a better solution could be to add a dummy ipv6 module that returns
-EOPNOTSOPP or appropriate for most calls.
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists