IPv6

[ZaltysZ]

I've learned about ipv6 the odd way. My system yielded poor networking performance for no apparent reason. It turned out it was due to delays between an ipv6 'call' and the system 'knowing' that my ISP does not support ipv6 (so it [my system] can fall back to ipv4).

 

This is one of the reasons why some pretty big web sites still do not support IPv6. User installs the OS, and OS comes with IPv6 enabled by default. User enters URL in the browser, browser makes a DNS query to get IP of the web server to which URL points to. DNS server returns bunch of IPs: IPv4 and IPv6. Browser prefers IPv6, so it uses IPv6 for connection to web server if browser OS supports IPv6. Unfortunately this is a fruitless effort, if ISP does not support IPv6 or there is no IPv6 over IPv4 tunneling present. After a while, IPv6 connection attempt timeouts and browser fallbacks to IPv4. This causes huge delays and makes you feel like your browser is crawling. Disabling IPv6 or telling your browser to prefer IPv4 solves the problem, however this is unknown or too cryptic for lots of users, so big websites simply drop IPv6, so that even clueless users won't get those delays, which may negatively affect how much users browse that website, and in turn, cause damage to revenue.

 

P.S: By the way, Win7 solved that issue on its own. If it sees that computer has only link local or Teredo IPv6 IPs, it resolves names only to IPv4, unless name does not have IPv4 IP at all.

Edited January 12, 2014 by ZaltysZ

[Seil]

PLEASE, under no circumstances try this in a Windows Server 2008 (R2) and later environment that uses Active Directory. You will run into trouble.

 

I must be in a lot of trouble :music_whistling:

 

I run a few fairly decent sized networks, windows, unix (LDAP) and a mix. IPv6 is no where to be seen. I only see improvements on the network because of which.

 

 

I'm not saying IPv6 is evil. But if you only need IPv4, then it is just additional overhead.

 

That's also why it's so hard to enable IPv6 across the world.... There are sooo many, an incredible amount of SoHo networks that aren't being managed, running only IPv4.

 

As far as WHEN it will "officially" come. hehehehehe well, they've been saying "a couple years" for over a decade.

 

-----------

 

Yes I disable IPv6 from the OS as well as any network devices.

 

On windows go into networking settings, change adapter, right click on adapter and goto properties and then properties (button). Uncheck the IPv6 protocol in the list and OK you're way out.

 

(I hate how M$ likes to bury that stuff.....)

 

---------

 

I understand why people are pushing for it right now and why NAT isn't the perfect solution for a lot of things right now.... But those are in fact mostly problems that come from protocol design and address registration issues.

 

And yes, for mobile, it makes the MOST sense to use all private space addresses on the mobile network. Your phone is a phone first, whether anyone remembers that or not. It's easy to route web access and such for those devices.

 

I've been in the industry for the last 20 years. Some things move fast, but IP addressing is the equivalent to the street addressing for your house. For everyone to switch is a staggering feat.

 

For end users that have turned it off: it is also easy enough to go enable the protocol when the time comes. I might have someone spend a whole hour to enable the protocol across an entire network... Even then however, if your edge devices can handle IPv4 / 6 conversion, there's still no reason for the internal network to be IPv6.

 

The internal networks are only built to what they NEED. That's why you see so many class C subnets (aka 255 addresses). Even fairly complex networks (class B and A) are divided into many class C subnets.

 

I would continue to quote and respond to everything else Bit, but I feel this is a topic well covered in other places and I don't need to write a book on these forums about it.

Edited January 12, 2014 by Seil

[BitMaster]

.....

 

I would continue to quote and respond to everything else Bit, but I feel this is a topic well covered in other places and I don't need to write a book on these forums about it.

 

You are right Seil,

 

I never wanted to have it this way, all I actually wanted is to start awareness of the change happening right now in one of DCS's biggest selling nations. Nothing else.....yeah,, a bit of help to get those showing interested into the matter so they are aware too.

 

 

Sure, for LANs that work the way they are, IPv6 is not of question. If you have compliancy rules,

public servives, Windows Active Directory etc.. this is a topic.

 

You said you run LDAP, well, that runs on IPv4 only I guess. AD doesn't anymore, which I regret too.

 

 

Bit