Is there anything being done about the @hsiservice logins that is having congestions issues?

I recently switched to my @teksavvy.com from my @hsiservice login because of the huge congestions issues with the latter and I am still getting my IPv6 address. Has teksavvy enabled IPv6 for standard logins now? Or is this an oddity?

Well, according to Cisco it does not support IPv6CP, so their claim of IPv6 support is false, to be blunt.

The router demands the default gateway be entered, so I'm stalled at this point. I'm not going to keep dropping $150 routers playing a guessing game.

WAN IPv6 Address: 2607:f2c0:a000:aa::1
WAN Prefix Length: 64
WAN IPv6 Gateway: 2607:f2c0:a000:aa::1 (same as your address)

N66u is easy to configure with TekSavvy.

Yes, you do use "Static IPv6". In the future hopefully this will move to automatic with DHCPv6-PD but for now static is the way it's done.

Configure your PPPoE connection for your @hsiservice.net login first and verify that regular IPv4 works fine, then...

Assuming TekSavvy assigned you:

IPV6 /64: 2607:f2c0:a000:aa::/64
IPV6 /56: 2607:f2c0:f00f:bb::/56

You would fill in the following on your 66u:

WAN IPv6 Address: 2607:f2c0:a000:aa::1
WAN Prefix Length: 64
WAN IPv6 Gateway: 2607:f2c0:a000:aa::1 (same as your address)

LAN IPv6 Prefix: 2607:f2c0:f00f:bb::
LAN Prefix Length: 56
LAN IPv6 Address : 2607:f2c0:f00f:bb::1

So, the WAN is your /64 address with "1" on the end (or could be anything, it's just an assignment you give) and a 64 prefix (hence /64).

The LAN prefix is your /56 without any address (so ending in ::), 56 as the prefix lenght, and your prefix with "1" at the end (or whatever you want) as the LAN address.

You can leave the DNS servers blank as TSI's v4 name servers resolve AAAA without issue and I've found TSI's v6 name servers be a little unreliable.

Once this is done you can go to »test-ipv6.com

If it shows the following:

Your IPv6 address on the public Internet appears to be XXXX

then it works. Hope that helps.

So it appears the new userid is both IPv4 and IPV6 which I didn't appreciate.

So it appears the new userid is both IPv4 and IPV6 which I didn't appreciate.

I now have the IPV6 setup as static with the addresses in.

>Configure your PPPoE connection for your @hsiservice.net login first and verify that regular IPv4 works fine, then...

I'm still running on the old login not the @hsiservice.net so how do I change this?

Thanks John

iOS supported v6 over HSPA already. The issue was with LTE only on the iPad and Wifi must have been with the iPad only too since it already worked with the iPod and iPhone with 5.x

re: Android our app tests all show it works well in the lab. This is SLAAC configured and with IPv4 DNS servers that will return AAAA records, hence why we never see issues with it I suppose. I do know there are "v6 only" issues with Android for sure.

Unfortunately that is not true. Android has somewhat big warts with its v6 support. No DHCPv6 support, no RFC6106 support, it can't connect to v6-only networks over wireless, no UI support for displaying v6 info, it seems to have issues dropping RA packets/ICMP more than enough to cause problems, issues with its wireless (as in 3G/4G) support. AFAIK all of these issues do not exist with iOS. Apple over all has done a much better job (although they're not 100% perfect).

360 does NOT use Windows. It along with the original Xbox use their own custom OS. That seems to be a common misconception. It doesn't even use DirectX either but a derivative API.

An additional portion of this problem is that there still isn't a very well defined port management system for IPV6 firewalls.

With V4 we have NAT-PMP and UPnP (gross) to handle this. V6 still doesn't really have a counterpart to tell the firewall to open ports as needed by opening/closing applications.

The port problem is compounded by address randomization on V6 networks by default in most OS's in SLAAC environments. DHCPv6 can solve this to some extent in that you can configure your router manually to always give your computer a specific address and then manually open ports needed but that's a pretty lousy solution compared to the relatively transparent operating of a NAT with PMP/UPnP support.

This is one area where Apple can show some real leadership - updating NAT-PMP to work well with IPv6 and really push it as a standard. Alas, Apple seems to care about 0% about IPv6, as evidenced by their V6 stack on OS X (happy eyeballs always on and can't be disabled) and their routers (PPPoE IPv6 completely unsupported).

Android both support V6 without issue

Console wise I don't expect Sony or Nintendo to be really -with it- on this issue given their lineage. Since the 360 (and theoretical 720) are Windows based I can see them getting V6 "for free" as part of the operating system stack, but Sony and Nintendo would have to bake V6 in by choice and I don't really see either of them having the foresight.

re: vendors - V6 support doesn't depend on hardware. If the device was Wifi or a cell radio and supports V4 it can support V6 via software without issue and almost always does.

re: tablets/smartphones etc - this is quite untrue. Basically all smartphones and tablets (which basically all run iOS or Android) support IPv6 natively and without issue.

Unfortunately so true.

Although that is true there is also a good percentage of tablets, smartphones and some appliances that do have IPv6 support as well especially if based on iOS, Android, Blackberry 10/Tablet OS's, Symbian, Windows Phone 8.

Skype not support v6 yet is a pain. That is one of the most visible services still holding out.

I am also interested to see how Nintendo, Sony and Microsoft handle rolling out v6 for their consoles and online gaming especially with Wii U being out and PS4 / Xbox (Durango) coming out soon.

Another area that will benefit greatly from IPv6 is VoIP. SIP is a total pain with NAT.

Since much of it is a chicken-and-the-egg problem (ISPs/incumbents are being lazy implementing IPv6 because few consumer modem/routers/devices support it) and consumer equipment manufacturers were being lazy doing IPv6 because no ISP/incumbents/routers supported it, things should start running a lot more smoothly now that the first IPv6 chickens have hatched.

We have finally reached the stage where people at least starting to notice IPv6 as a checkbox feature (they may not know what it does but they do notice that router/service A advertises support while router/service B does not) when buying routers and some other devices or services.

I'm curious to see whether or not Sony and Microsoft will choose to check the box or not. Considering how many router-related problems IPv6 would eliminate, it would be a shame if they decided to skip it completely. (As in neither at launch nor future patch.)

I am also interested to see how Nintendo, Sony and Microsoft handle rolling out v6 for their consoles and online gaming especially with Wii U being out and PS4 / Xbox (Durango) coming out soon.

The point was that we should have been at this point at least half a decade ago. If consumer hardware and devices had started supporting IPv6 10 years ago, the transition would be practically over by now.

Today, many devices (tablets, smartphones, smart appliances, etc.) are still IPv4-only.

Carriers are basically the hold-up at this point. If Rogers started doing native IPV6 on their cable network tomorrow the usage of IPV6 on their network would probably hit double digit% on the first day I'd guess, just from people who have it enabled / supported by default and aren't getting addresses.

Given that -everyone- seems to peer through HE right now I'd guess that Rogers isn't sure that their peering can handle a wide deployment though. TekSavvy is maybe in the same boat.

At this point it's really not consumer manufacturers that are the hold up anymore.