IPV6 on UFB

Forums › 2degrees (including Slingshot, Orcon, Flip, Stuff Fibre, MyRepublic, 2talk and Vocus) › IPV6 on UFB

1 | 2 | 3 | 4

3919 posts

Uber Geek
+1 received by user: 752

Trusted

#1748921 27-Mar-2017 19:32

kiwifidget:

From an end-user perspective, what is the benefit of being on ipv6?

I have a Putty session open to a virtual server in Switzerland, one in Aus and one in the USA without public IPv4 without eneding to run triple concurrent VPNs right now...

Speedtest 2019-10-14

Sounddude

I fix stuff!
1929 posts

Uber Geek
+1 received by user: 615

Trusted

2degrees

Lifetime subscriber

#1749231 28-Mar-2017 10:29

jamesrt:

Sadly, no sign of IPV6 working yet; rebooted the router this morning "just in case", but nope.

Hopefully not too much longer...

Hi Guys

Yes sorry for the late communications from me, I went to implement it and ran into some complex configuration issues which we need to work through first.

Will have some more news on that soon.

Sorry for the muck around!

jamesrt

1625 posts

Uber Geek
+1 received by user: 855

ID Verified

Trusted

Lifetime subscriber

#1749352 28-Mar-2017 12:52

Sounddude: Yes sorry for the late communications from me, I went to implement it and ran into some complex configuration issues which we need to work through first.

Will have some more news on that soon.

Sorry for the muck around!

Thanks for the update; I'm sure we'll all agree that having it working correctly is more important that meeting a specific date...

MadEngineer

4381 posts

Uber Geek
+1 received by user: 2375

Trusted

#1749353 28-Mar-2017 12:53

dt:

also interested to know the benefit for home user that does pretty regular stuff.. browsing.. gaming.. iptv etc..

There maybe some benefit for the likes of xbox where it would no longer rely on upnp or the creation of a teredo tunnel. Sometimes xbox thinks it has a working IPv6 network as provided by the router, tries to set up communications using it but fails, blocking some in-game functions. I guess it would reduce latency by a few ms.

You're not on Atlantis anymore, Duncan Idaho.

dt

1152 posts

Uber Geek
+1 received by user: 371
Inactive user

#1749795 28-Mar-2017 21:49

MadEngineer:

There maybe some benefit for the likes of xbox where it would no longer rely on upnp or the creation of a teredo tunnel. Sometimes xbox thinks it has a working IPv6 network as provided by the router, tries to set up communications using it but fails, blocking some in-game functions. I guess it would reduce latency by a few ms.

hmm no xbox at home :)

thanks for taking the time to explain mate

Sounddude

I fix stuff!
1929 posts

Uber Geek
+1 received by user: 615

Trusted

2degrees

Lifetime subscriber

#1767709 20-Apr-2017 09:10

Hi Guys

Just an update, we are still progressing.

Last night we enabled the Hamilton BNG so the following regions now have IPV6 access on UFB tails

Hamilton

Tauranga

Rotorua

Levin

Gisborne

Kiwiprobie

155 posts

Master Geek
+1 received by user: 1
Inactive user

#1767944 20-Apr-2017 15:35

Looks like we have it here in Tok as well.

AliExpress

Shop now on AliExpress (affiliate link).

Sounddude

I fix stuff!
1929 posts

Uber Geek
+1 received by user: 615

Trusted

2degrees

Lifetime subscriber

#1770728 26-Apr-2017 15:25

Wellington and surrounding areas tonight for you guys which have been waiting!

Jarno

270 posts

Ultimate Geek
+1 received by user: 50

#1770996 27-Apr-2017 01:02

Hello IPv6 badge from Nelson!

Gwilson

136 posts

Master Geek
+1 received by user: 42

#1771012 27-Apr-2017 07:01

Working in Wellington, no router reboot required.

jamesrt

1625 posts

Uber Geek
+1 received by user: 855

ID Verified

Trusted

Lifetime subscriber

#1771096 27-Apr-2017 09:45

Technically, it is working for me (Porirua), in that my Orcon-White (slight dyslexic tendencies mean I hate trying to guess/remember the model number!) has an IPV6 on the WAN connection.

However, a quick test this morning from an end-user device (iPad) was unsuccessful in making an IPV6 connection to the "real world". I guess I've got some settings to adjust somewhere.

The router's "Device Status" page currently doesn't show any LAN IPv6 address, which is probably NOT a good start....

I did had a quick fiddle before I needed to leave the house, and I managed to get the router to show an IPV6 LAN address starting "fd12:"; but given that the WAN address starts "2404:" and my understanding is that IPV6 doesn't do/need NAT, then I'm fairly sure that isn't correct.

If anyone could be kind enough to post their settings from an Orcon White for me to double-check, that would be appreciated. "Advanced Settings/LAN/IPv6 Autoconfig" is probably what I need to double-check first; but the "WAN Service" settings for eth4.1 would also be useful to have.

Ta!

Sounddude

I fix stuff!
1929 posts

Uber Geek
+1 received by user: 615

Trusted

2degrees

Lifetime subscriber

#1771103 27-Apr-2017 10:04

James

Int he WAN config, make sure "Request IPv6 Address" is ticked.

For IPV6 to work the modem needs both a NA (Network Address) and a PD (Prefix Delegation) address.

Some of the White modems don't have the NA ticked (which we are working on). Ticking that should fix your issue.

jamesrt

1625 posts

Uber Geek
+1 received by user: 855

ID Verified

Trusted

Lifetime subscriber

#1771121 27-Apr-2017 10:26

Sounddude: Int he WAN config, make sure "Request IPv6 Address" is ticked.

For IPV6 to work the modem needs both a NA (Network Address) and a PD (Prefix Delegation) address

This is looking better!

# ping -6 www.geekzone.co.nz
PING www.geekzone.co.nz(2400:cb00:2048:1::6818:20e (2400:cb00:2048:1::6818:20e)) 56 data bytes
64 bytes from 2400:cb00:2048:1::6818:20e (2400:cb00:2048:1::6818:20e): icmp_seq=1 ttl=60 time=13.7 ms
64 bytes from 2400:cb00:2048:1::6818:20e (2400:cb00:2048:1::6818:20e): icmp_seq=2 ttl=60 time=13.2 ms

(That's from my Synology NAS; so I'm assuming that other devices will also work; but I didn't bother leaving anything useful for remote-access online when I left the house this morning)

Interestingly, the NAS is still reporting an "fe80:"-prefixed address as it's default IPV6 gateway; whereas I would have expected a "2404:"-prefixed address. The NAS does, however, pick up a "2404:"-prefix IPV6 address via (presumably) DHCP (it's IPV6 config just says "auto"); I guess I've still got a little learning to do on how IPV6 works.

Which is why I wanted to play with it, to be honest!

Thanks, @Sounddude!

Sounddude

I fix stuff!
1929 posts

Uber Geek
+1 received by user: 615

Trusted

2degrees

Lifetime subscriber

#1771122 27-Apr-2017 10:27

The whitebox will be sending out RA's onto the LAN for autoconfiguration. Part of that will be the fe80: prefix for the default gateway (Its called a link local address).

Its perfectly valid as the IPV6 PD/NA could technically change, so keeps the GW the same.

MadEngineer

4381 posts

Uber Geek
+1 received by user: 2375

Trusted

#1771126 27-Apr-2017 10:31

Curious to know the firewall behaviour of the NF4V: paste your NAS unit's IPV6 address HERE and see if it's reachable

You're not on Atlantis anymore, Duncan Idaho.

1 | 2 | 3 | 4