[Snap] IPv6 and Snap

Forums › 2degrees (including Slingshot, Orcon, Flip, Stuff Fibre, MyRepublic, 2talk and Vocus) › [Snap] IPv6 and Snap

Aaroona

3204 posts

Uber Geek
+1 received by user: 169

#141107 1-Mar-2014 15:16

So I thought I'd have a little look at IPv6 on my snap VDSL connection.

It looks like I got it up and running, but some sites, Geekzone included, won't respond to my requests.

For example, with IPv6 only enabled on my machine, I can view Google fine.

I can ping Google and Geekzone fine, it just never loads;

C:\Users\Aaron>ping geekzone.co.nz

Pinging geekzone.co.nz [2400:cb00:2048:1::a29f:f352] with 32 bytes of data:
Reply from 2400:cb00:2048:1::a29f:f352: time=330ms
Reply from 2400:cb00:2048:1::a29f:f352: time=265ms
Reply from 2400:cb00:2048:1::a29f:f352: time=266ms
Reply from 2400:cb00:2048:1::a29f:f352: time=265ms

Ping statistics for 2400:cb00:2048:1::a29f:f352:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 265ms, Maximum = 330ms, Average = 281ms

C:\Users\Aaron>ping google.co.nz

Pinging google.co.nz [2404:6800:4006:806::1018] with 32 bytes of data:
Reply from 2404:6800:4006:806::1018: time=220ms
Reply from 2404:6800:4006:806::1018: time=220ms
Reply from 2404:6800:4006:806::1018: time=221ms
Reply from 2404:6800:4006:806::1018: time=219ms

Ping statistics for 2404:6800:4006:806::1018:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 219ms, Maximum = 221ms, Average = 220ms

When I do an IPv6 test (via a website that detects the IP's), it tells me that I have an IPv6 address etc (albeit 6to4).

Bearing in mind that I have very little IPv6 knowledge - why is it that we are using 6to4? When I tried to use PPPoE, it wouldn't respond.
Interestingly, my ping has increased dramatically. Normally on IPv4 I get 4ms to google... Ipv6.. over 200...

1 | 2

904 posts

Ultimate Geek
+1 received by user: 336

Trusted

#997203 1-Mar-2014 18:01

What type of router are you using, and how is it configured?
Snap offers a native v6 connection via DHCPv6-PD. This is in addition to PPPoE for authentication and IPv4, as well as VLAN 10 tagging.
It seems to me that what you have working above is teredo tunnelling. I've had this happen before when testing IPv6. Windows defaults to using this until you receive a valid IPv6 address.

If you have configured your router + clients correctly you should have an IPv6 address somewhere in the 2406:e000:: range. You should be able to see it in ipconfig /all, and it should show up when you visit an IPv6 test page.

For comparison some pings via Snap VDSL to geekzone over v6 and v4:
Note that both are resolving to Cloudflare IPs in Sydney.

Pinging geekzone.co.nz [2400:cb00:2048:1::a29f:f252] with 32 bytes of data:
Reply from 2400:cb00:2048:1::a29f:f252: time=44ms
Reply from 2400:cb00:2048:1::a29f:f252: time=43ms
Reply from 2400:cb00:2048:1::a29f:f252: time=43ms
Reply from 2400:cb00:2048:1::a29f:f252: time=43ms

Ping statistics for 2400:cb00:2048:1::a29f:f252:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 43ms, Maximum = 44ms, Average = 43ms

C:\Users\Lorenceo>ping -4 geekzone.co.nz

Pinging geekzone.co.nz [162.159.243.82] with 32 bytes of data:
Reply from 162.159.243.82: bytes=32 time=43ms TTL=56
Reply from 162.159.243.82: bytes=32 time=44ms TTL=56
Reply from 162.159.243.82: bytes=32 time=43ms TTL=56
Reply from 162.159.243.82: bytes=32 time=43ms TTL=56

Ping statistics for 162.159.243.82:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 43ms, Maximum = 44ms, Average = 43ms

hio77

'That VDSL Cat'
13036 posts

Uber Geek
+1 received by user: 3896

ID Verified

Trusted

Lizard Networks

Subscriber

#997207 1-Mar-2014 18:21

Lorenceo: What type of router are you using, and how is it configured?
Snap offers a native v6 connection via DHCPv6-PD. This is in addition to PPPoE for authentication and IPv4, as well as VLAN 10 tagging.
It seems to me that what you have working above is teredo tunnelling. I've had this happen before when testing IPv6. It defaults to using this until you receive a valid IPv6 address.

If you have configured your router + clients correctly you should have an IPv6 address somewhere in the 2406:e000:: range. You should be able to see it in ipconfig /all, and it should show up when you visit an IPv6 test page.

For comparison some pings via Snap VDSL to geekzone over v6 and v4:
Note that both are resolving to Cloudflare IPs in Sydney.

Pinging geekzone.co.nz [2400:cb00:2048:1::a29f:f252] with 32 bytes of data:
Reply from 2400:cb00:2048:1::a29f:f252: time=44ms
Reply from 2400:cb00:2048:1::a29f:f252: time=43ms
Reply from 2400:cb00:2048:1::a29f:f252: time=43ms
Reply from 2400:cb00:2048:1::a29f:f252: time=43ms

Ping statistics for 2400:cb00:2048:1::a29f:f252:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 43ms, Maximum = 44ms, Average = 43ms

C:\Users\Lorenceo>ping -4 geekzone.co.nz

Pinging geekzone.co.nz [162.159.243.82] with 32 bytes of data:
Reply from 162.159.243.82: bytes=32 time=43ms TTL=56
Reply from 162.159.243.82: bytes=32 time=44ms TTL=56
Reply from 162.159.243.82: bytes=32 time=43ms TTL=56
Reply from 162.159.243.82: bytes=32 time=43ms TTL=56

Ping statistics for 162.159.243.82:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 43ms, Maximum = 44ms, Average = 43ms

much the same as what i conclude.

for your own interest, running on dual stack,

heres how a duel stack connection tends to look to GZ.

#include <std_disclaimer>

Any comments made are personal opinion and do not reflect directly on the position my current or past employers may have.

Aaroona

3204 posts

Uber Geek
+1 received by user: 169

#1000328 6-Mar-2014 19:04

Hmm, I'll have to do some more testing at a later date. I don't know why I couldnt get it to work using the native stack. Would only connect over 6to4.

I've loaded DDWRT onto my router now, so IPv6 is pretty much out of the question at this stage, but I'll look at loading up OpenWRT soon or something to try again.

WolfmanNZ

148 posts

Master Geek
+1 received by user: 41

#1000534 7-Mar-2014 09:20

On this subject - straight after I was connected to Snap, I started getting problems searching on Google. I would have to search, wait for 20 seconds while nothing happened, then hit the search icon again and then everything would load. I switched to the SSL Google search engine and that fixed the Google search, but then Gmail started flaking out - it would load, I might be able to view one or two messages, then it would freeze. I spent a lot of time researching forums to do with Google/Gmail issues, having initially thought it was a browser issue (Firefox, but then had same issues using IE or Chrome)
Dropped Google SSL to see if that was somehow affecting Gmail - no and now searches broken as well. Had to start using Bing. The horror.

Then loaded Wireshark in a vain attempt to see if I could spot something meaningful from a capture file. One entry stuck out, an error relating to my network card and IPv6. Disabled IPv6 on the card - EVERYTHING WORKS AGAIN!

Sorry I dont have any meaningful or empirical data to post up to support this but thought I'd add in case someone else with similar issues stumbles across this looking for a fix.

We went like this. he went like that. I say "Where'd he go?" Hollywood says "Where'd WHO go?!"

NZGamingIcon

66 posts

Master Geek
+1 received by user: 12

#1000607 7-Mar-2014 10:59

This was discussed on this thread here - http://www.geekzone.co.nz/forums.asp?forumid=90&topicid=139010

The conclusion was Snap IPv6 is broken. I even called Snap and a CSR told me that I shouldn't be using IPv6 and should keep it disabled, he also stated that they are aware of the issues surrounding it and they are investigating it.

WolfmanNZ

148 posts

Master Geek
+1 received by user: 41

#1000652 7-Mar-2014 11:35

NZGamingIcon: This was discussed on this thread here - http://www.geekzone.co.nz/forums.asp?forumid=90&topicid=139010

The conclusion was Snap IPv6 is broken. I even called Snap and a CSR told me that I shouldn't be using IPv6 and should keep it disabled, he also stated that they are aware of the issues surrounding it and they are investigating it.

Ah cool yeah that would have helped but when I was searching for clues I was looking for Google and Gmail issues not IPv6 so probably just breezed past that thread - oh well I got there in the end.

We went like this. he went like that. I say "Where'd he go?" Hollywood says "Where'd WHO go?!"

HP

Shop now for HP laptops and other devices (affiliate link).

Lorenceo

904 posts

Ultimate Geek
+1 received by user: 336

Trusted

#1000686 7-Mar-2014 12:17

FWIW IPv6 is working fine here. I'm not using a Fritzbox, though.

hio77

'That VDSL Cat'
13036 posts

Uber Geek
+1 received by user: 3896

ID Verified

Trusted

Lizard Networks

Subscriber

#1000739 7-Mar-2014 13:43

Lorenceo: FWIW IPv6 is working fine here. I'm not using a Fritzbox, though.

exactly this. personally, on a 7390 running 5.21. not sure why some are having the issues and others of us arent though..

few people have tested, with the exact same setup as me..

#include <std_disclaimer>

Any comments made are personal opinion and do not reflect directly on the position my current or past employers may have.

vexxxboy

4336 posts

Uber Geek
+1 received by user: 2072

#1000749 7-Mar-2014 13:59

case in point, i tried to connect to Netflix , nothing happened . It didnt time out it just wouldnt open . i turned ipv6 off in the Fritzbox and tried again , no problem. I went back and turned it back on and it wouldnt connect again . So the conclusion i came to is That ipv6 isnt working , unless someone can come up with a better reason why this is happening.

Common sense is not as common as you think.

hio77

'That VDSL Cat'
13036 posts

Uber Geek
+1 received by user: 3896

ID Verified

Trusted

Lizard Networks

Subscriber

#1000750 7-Mar-2014 14:00

vexxxboy: case in point, i tried to connect to Netflix , nothing happened . It didnt time out it just wouldnt open . i turned ipv6 off in the Fritzbox and tried again , no problem. I went back and turned it back on and it wouldnt connect again . So the conclusion i came to is That ipv6 isnt working , unless someone can come up with a better reason why this is happening.

considering your using ipv6 to netflix, ild say it would bypass whatever dns redirector your using if it resolves using snaps ipv6 rather than via the redirector.

#include <std_disclaimer>

Any comments made are personal opinion and do not reflect directly on the position my current or past employers may have.

vexxxboy

4336 posts

Uber Geek
+1 received by user: 2072

#1000757 7-Mar-2014 14:10

hio77:
vexxxboy: case in point, i tried to connect to Netflix , nothing happened . It didnt time out it just wouldnt open . i turned ipv6 off in the Fritzbox and tried again , no problem. I went back and turned it back on and it wouldnt connect again . So the conclusion i came to is That ipv6 isnt working , unless someone can come up with a better reason why this is happening.

considering your using ipv6 to netflix, ild say it would bypass whatever dns redirector your using if it resolves using snaps ipv6 rather than via the redirector.

this is not the first time it has happened and usually i just leave it for a few hours and everything is fine when i try it again. why doesnt it happen everytime , it can be fine for days and then problems occur . It is annoying that i have to turn ipv 6 off to get it working.

Common sense is not as common as you think.

Geekzone support

Support Geekzone with one-off or recurring donations Donate via PressPatron.

hio77

'That VDSL Cat'
13036 posts

Uber Geek
+1 received by user: 3896

ID Verified

Trusted

Lizard Networks

Subscriber

#1000758 7-Mar-2014 14:10

vexxxboy:
hio77:
vexxxboy: case in point, i tried to connect to Netflix , nothing happened . It didnt time out it just wouldnt open . i turned ipv6 off in the Fritzbox and tried again , no problem. I went back and turned it back on and it wouldnt connect again . So the conclusion i came to is That ipv6 isnt working , unless someone can come up with a better reason why this is happening.

considering your using ipv6 to netflix, ild say it would bypass whatever dns redirector your using if it resolves using snaps ipv6 rather than via the redirector.

this is not the first time it has happened and usually i just leave it for a few hours and everything is fine when i try it again. why doesnt it happen everytime , it can be fine for days and then problems occur . It is annoying that i have to turn ipv 6 off to get it working.

difference between ipv6 resolution and ipv4 ild say.

if the dns redirector is a dnsmasq implementation, it could easily simply be matching certain requests, and forwarding the rest to google, if google got your request for netflix, they will hand over the ipv6 address too, which wouldnt be going via the proxy server.

#include <std_disclaimer>

Any comments made are personal opinion and do not reflect directly on the position my current or past employers may have.

jarledb

Webhead
3319 posts

Uber Geek
+1 received by user: 1983

Moderator

ID Verified

Trusted

Lifetime subscriber

#1000759 7-Mar-2014 14:14

Thanks for the tip, have turned off ipv6 in the Fritz box today. Not sure what has been going on, seems like ipv6 was disabled somewhere (on the network) for a while and was back in the last few days - with all the problems I think was connected to ipv6 last round.

So now its permanently turned off in the router.

Jarle Dahl Bergersen | Referral Links: Want $50 off when you join Octopus Energy? Use this referral code
Are you happy with what you get from Geekzone? Please consider supporting us by making a donation or subscribing.

sorceror

163 posts

Master Geek
+1 received by user: 47

#1000949 7-Mar-2014 18:25

keep in mind that even though you have turned it off on the router, windows still will try and use ipv6 over teredo

i always turn off ipv6 in windows 8 - it's flaky and tends to cause certain software to behave strangely (as windows 8 prefers v6 over v4)

hio77

'That VDSL Cat'
13036 posts

Uber Geek
+1 received by user: 3896

ID Verified

Trusted

Lizard Networks

Subscriber

#1000950 7-Mar-2014 18:27

sorceror: keep in mind that even though you have turned it off on the router, windows still will try and use ipv6 over teredo

i always turn off ipv6 in windows 8 - it's flaky and tends to cause certain software to behave strangely (as windows 8 prefers v6 over v4)

strangely? such as? i haven't seen any strange acting in windows 8..

#include <std_disclaimer>

Any comments made are personal opinion and do not reflect directly on the position my current or past employers may have.

1 | 2