[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]
Re: pkg/44689: IPv6 support disabled by default in chat/irssi
The following reply was made to PR pkg/44689; it has been noted by GNATS.
From: Francois Tigeot <ftigeot%wolfpond.org@localhost>
Cc: pkg-manager%NetBSD.org@localhost, gnats-admin%NetBSD.org@localhost,
Subject: Re: pkg/44689: IPv6 support disabled by default in chat/irssi
Date: Sun, 6 Mar 2011 13:18:20 +0100
On Sun, Mar 06, 2011 at 10:10:06AM +0000, Thomas Klausner wrote:
> The following reply was made to PR pkg/44689; it has been noted by GNATS.
> From: Thomas Klausner <wiz%NetBSD.org@localhost>
> To: NetBSD bugtracking <gnats-bugs%NetBSD.org@localhost>
> Subject: Re: pkg/44689: IPv6 support disabled by default in chat/irssi
> Date: Sun, 6 Mar 2011 11:08:25 +0100
> On Sat, Mar 05, 2011 at 09:05:00PM +0000, ftigeot%wolfpond.org@localhost
> > By default, IPv6 support is disabled in chat/irssi
> NetBSD enables the inet6 option by default since USE_INET6 is set in
> /usr/share/mk somewhere, and that gets translated to the inet6 option
> (with a deprecation warning) in mk/ somewhere.
> Perhaps we should get rid of this automatic translation and just
> enable inet6 by default on all platforms, so we don't get more of this
> kind of bug report in the future?
My point is there should not be an 'inet6' option anymore.
We're only month from IPv4 depletion in RIR pools and some organizations are
deploying IPv6-only network right now.
Heck, I figured out this issue trying to connect to an IPv6-only server.
If some people want to disable IPv6, they could use a 'noinet6' option but
in 2011, IPv6 support should be enabled by default.
The only exceptions should be for brain-damaged software such as Java, where
enabling IPv6 disables IPv4 support.
Main Index |
Thread Index |