[Snap] How to get IPV6 to work on Snap?

Forums › 2degrees (including Slingshot, Orcon, Flip, Stuff Fibre, MyRepublic, 2talk and Vocus) › [Snap] How to get IPV6 to work on Snap?

sbaird

81 posts

Master Geek

#116374 27-Apr-2013 09:20

Got a new Snap VDSL connection but cant seem to get the IPV6 to work.
Modem is the Fritzbox 7390.
The modem gets a IPV6 address and my computer picks it up and sets the Fritz box as the default route,
But can't ping anything outside my network,

traceroute6 ipv6.google.com
traceroute to ipv6.l.google.com (2404:6800:4006:803::1011) from 2406:e000:c15d:1:6da5:2d7:9e05:defe, 30 hops max, 24 byte packets
1 2406:e000:c15d:1:9ec7:a6ff:fe1d:f3c0 (2406:e000:c15d:1:9ec7:a6ff:fe1d:f3c0) 2.508 ms 0.554 ms 0.387 ms
2 2406:e000:97:1::1 (2406:e000:97:1::1) 20.676 ms 20.388 ms 21.682 ms
3 * * *
4 * * *

ip -6 route
2406:e000:c148:1::/64 dev eth0 proto kernel metric 256 expires 6088sec
2406:e000:c15d:1::/64 dev eth0 proto kernel metric 256 expires 7180sec
fe80::/64 dev vmnet1 proto kernel metric 256
fe80::/64 dev vmnet8 proto kernel metric 256
fe80::/64 dev eth0 proto kernel metric 256
default via fe80::9ec7:a6ff:fe1d:f3c0 dev eth0 proto kernel metric 1024

Unique Local Address of your FRITZ!Box: fd00::9ec7:a6ff:fe1d:f3c0/64

Any suggestions?

billgates

4705 posts

Uber Geek

Trusted

#806268 27-Apr-2013 10:42

On the fritz!box, under internet click account information then click IPv6 tab and make sure IPv6 support enabled checkbox is ticked

Do whatever you want to do man.

quakeguy

111 posts

Master Geek

Trusted

#806272 27-Apr-2013 10:53

So ping doesn't return a response? You only show a traceroute.
Some of the hops in Snap's network don't reply (this is expected at the moment). If you leave it going, does your traceroute complete? It looks like you're getting outside your own network in your traceroute, so it should be working.

Can you traceroute6 to 2406:e000::1 ?

tim@hivemind9:~$ ip -6 route
2406:e000:xxxx::/64 dev eth0 proto kernel metric 256 expires 2592185sec
fe80::/64 dev eth0 proto kernel metric 256
fe80::/64 dev eth1 proto kernel metric 256
default via fe80::20c:42ff:fef3:8166 dev eth0 proto kernel metric 1024 expires 1661sec

tim@hivemind9:~$ ping6 ipv6.google.com
PING ipv6.google.com(2404:6800:4006:801::1012) 56 data bytes
64 bytes from 2404:6800:4006:801::1012: icmp_seq=1 ttl=54 time=42.9 ms
64 bytes from 2404:6800:4006:801::1012: icmp_seq=2 ttl=54 time=43.3 ms

tim@hivemind9:~$ traceroute6 ipv6.google.com
traceroute to ipv6.l.google.com (2404:6800:4006:801::1012) from 2406:e000:[removed], 30 hops max, 16 byte packets
1 2406:e000:xxxx:: (2406:e000:xxxx::) 0.661 ms 0.354 ms 0.314 ms
2 2406:e000:98:1::1 (2406:e000:98:1::1) 23.15 ms 8.009 ms 25.136 ms
3 2405:f900:0:1::1 (2405:f900:0:1::1) 5.046 ms 5.381 ms 6.743 ms
4 * * *
5 * * *
6 * * *
7 23655.syd.equinix.com (2001:de8:6::2:3655:1) 42.959 ms 43.087 ms 43.989 ms
8 2406:e000:400::3 (2406:e000:400::3) 42.258 ms 42.233 ms 42.697 ms
9 2001:4860::1:0:43bb (2001:4860::1:0:43bb) 42.74 ms 43.725 ms 42.478 ms
10 2001:4860:0:1::1ff (2001:4860:0:1::1ff) 43.568 ms 44.147 ms 43.911 ms
11 2404:6800:8000:8:92e6:baff:fe53:a15a (2404:6800:8000:8:92e6:baff:fe53:a15a) 43.266 ms 43.546 ms 43.282 ms

“I do not think there is any thrill that can go through the human heart like that felt by the inventor as he sees some creation of the brain unfolding to success... Such emotions make a man forget food, sleep, friends, love, everything.” - Nikola Tesla

Disclaimer: Views expressed in my posts do not necessarily reflect those views of my employer.

sbaird

81 posts

Master Geek

#806290 27-Apr-2013 11:25

IPV6 is enabled and set on "Always use a native IPv4 connection (recommended)"

Under the homenetworking its set as
"
Define how the Unique Local Addresses (ULA) should be defined to the devices in the network.
Assign unique local addresses (ULA) as long as no IPv6 connection exists (recommended)
Disable DHCPv6 server in the FRITZ!Box:
There are no other DHCPv6 servers in the home network.

Devices in the home network should use automatic configuration (SLAAC) to determine their own IPv6 address.
"

traceroute6 2406:e000::1
traceroute to 2406:e000::1 (2406:e000::1) from 2406:e000:c15d:1:6da5:2d7:9e05:defe, 30 hops max, 24 byte packets
1 2406:e000:c15d:1:9ec7:a6ff:fe1d:f3c0 (2406:e000:c15d:1:9ec7:a6ff:fe1d:f3c0) 3.198 ms 0.506 ms 0.585 ms
2 2406:e000:97:1::1 (2406:e000:97:1::1) 21.369 ms 20.065 ms 25.501 ms
3 * * *
4 * * *
(5-29 are * * *)
30 * * *

sbaird

81 posts

Master Geek

#806296 27-Apr-2013 11:45

Turns out the problem is most likely on snap's end,
They are looking into it,