ipv6 - to disable or not to disable that is the question

OMG ipv4 is running out (again, and again …)!

I’ve always disabled ipv6 as it was supposed to choke up internet links
because there were some badly configured ipv6 devices out there but we’re
now being exhorted to move to ipv6 so …

What’s the current percieved wisdom as regards enabling/disabling ipv6?


Alan

On 05/23/2012 08:53 AM, Fudokai wrote:
> What’s the current percieved wisdom as regards enabling/disabling ipv6?

what works for me [TM] is enable IPv6 everywhere and and use a DNS known
to handle IPv6 well–so, i comment out my ISP’s broken DNS and use
8.8.8.8 and 8.8.4.4 in /etc/resolv.conf, like so:


#nameserver 192.168.1.1
#nameserver 208.67.222.222
#nameserver 208.67.220.220
nameserver 8.8.8.8
nameserver 8.8.4.4

NOTE: you are asking for an opinion…i gave you mine based on what
works here…you might expect both conflicting and better ones…ymmv


dd

Don’t disable ipv6 as it usually creates more problems then benefits.

Best regards,
Greg

One of the benifits here is that, though advertising the opposite, ISP’s are not (competely) ready for ipV6. If I turn it on, it takes a couple of hours before my router “hangs” from timed out requests. Using Google’s DNS’s does not solve that.

I’ve always had IPv6 enabled — and it has caused no prroblems – until I added a wired network whose routers would only respond to IPv4. So, unless you are encountering problems, stick with IPv6.

I bug reported IPV6 problems way back in 11.4 and the bug is still active or so it seems from this

https://bugzilla.novell.com/show_bug.cgi?id=684534

My report was merged with another. Note comment “people think”. I’m still running 11.4 and had exactly the same problem. Curious thing is that there is an ipv6 disable setting in yast network and setting that didn’t work. I then set google dns and things started to work. Many months later checking dns I found I wasn’t using google at all ??? It seems many isp do not support ipv6 anyway and probably don’t even support the tunneling protocol that should get round that. Many many routers definitely don’t support ipv6.

It’s an interesting area. I started using suse when it was suse.de not novel. Can’t remember the version number but it’s probably over 15 years ago. They issued ipv6 as an update and many peoples internet just stopped working. Mine was so slow that an ebay page for instance could take 1min plus to load. One day maybe it will be sorted out.

Why the action on the bug list now? I suspect it’s because I mentioned that windows appeared to be fully ready for it. ipv4 - ipv6 or both as needed. I think that was on XP on my wife’s laptop.

John
PS
11.4 as it’s dead stable. I may switch to 12 when that’s at 4.

On 2012-05-23 11:06, John 82 wrote:

I created the file /root/.curlrc with this contents:


--ipv4

I hope that with this zypper/yast will not try to use IPv6 addresses when
downloading things.

But other tools have problems there: I have glitches with svn and fetchnews
attempting ipv6.

> PS
> 11.4 as it’s dead stable. I may switch to 12 when that’s at 4.

Not going to happen. After 12.3 will come 13.1. The version numbering
system is fixed.


Cheers / Saludos,

Carlos E. R.
(from 11.4 x86_64 “Celadon” at Telcontar)

:wink: Maybe 6 months after 12.3 has been about then Saludos.

I mostly use my PC so always fear to tread where other may go far more quickly!

John

Or about 20 months after security updates for 11.4 have ceased?

I wait and see. It’s usually possible to find out how things are by nosing around on the web. Maybe wait for version 13.1 release - unlucky for some especially novel if the last 12 remains buggy. The world just doesn’t need another cutting edge distro.

Actually 11.4 gets a little lost in space at times. I will be interested to see if that changes following my update. Sometimes it’s a reboot to recover or just a log out log in which case is probably kde. Reboot though ??? Might be anywhere.

Some who get fed up with dodgy releases switch to Arch. Takes courage but it seems things get sorted rapidly there and often vanilla code is used. Apparently total time spent trying to sort out problems is low on a per year basis but for me now apart from upgrade problems it’s been virtually zero. I entire day lost on a nas now all down to the upgrade and who knows how many to go. Many days lost when I installed as 11.4. Largely down to old well out of date information. Early 11 was better but had problems

John

On 2012-05-24 01:56, John 82 wrote:
>
> I wait and see. It’s usually possible to find out how things are by
> nosing around on the web. Maybe wait for version 13.1 release - unlucky
> for some especially novel if the last 12 remains buggy. The world just
> doesn’t need another cutting edge distro.

Please remember that in openSUSE there is no such thing as the 12.x series
or 13.x series. The numbering goes 12.1, 12.2, 12.3, 13.1, etc, without any
meaning at all attached to the major/minor numbers. They are just nice numbers.

There was a vote on this.


Cheers / Saludos,

Carlos E. R.
(from 11.4 x86_64 “Celadon” at Telcontar)

To be consequent:


nameserver 2001:4860:4860::8888
nameserver 2001:4860:4860::8844