IPv6 connectivity

SOLVED
Friendly Neighbour

IPv6 connectivity

Is there a public roadmap to when Telus will provide IPv6 connectivity to residential and/or mobile customers?

Will there be any DSLAM compatibilty issues as an ADSL customer?

0 Likes
Reply
1 ACCEPTED SOLUTION
TELUS Employee

Hi @mtylerb​ and @skyblaster​,


I am happy to share that we are in the midst of enabling IPv6 for eligible TELUS Internet subscribers. To be eligible you must be on our Converged Edge network (true of most TELUS Internet subscribers) and have an Actiontec gateway. Zyxel gateways will be enabled with a firmware update, likely in 2016. I hope you enjoy the addition of IPv6 connectivity coming soon to you!

View solution in original post

0 Likes
Reply
31 REPLIES 31
Organizer

thats so odd, on my Ubiquiti EdgeRouterX it seems to be showing up the other way around

my equivalent to what your claiming is the IPV6 WAN address is on switch0 which is my lan

my equivalent to what your claiming is the IPV6 WAN link local address is on switch0 which is my lan

my equivalent to what your claiming is IPV6 LAN link local address is on eth1 which is my WAN and is kinda confusing

i determined this because there essentially is no "IPV6 LAN address" according to you ,other then the local

the "IPV6 WAN address" is always common to the "IPV6 WAN address"

so because the equivalent of the "IPV6 WAN address" is on my LAN (switch0) then i know that what you are claiming is "IPV6 WAN address" and "IPV6 WAN link local address" will be on the same interface (WAN) and the last 4 sets of colins will match

also my default gateway is the ipv6 link local wan address i believe and that is on switch0 which is my lan

admin@ERX:~$ show interfaces ethernet eth1
eth1:  mtu 1500 qdisc htb state UP qlen 1000
    link/ether 44:d9:e7:07:73:b5 brd ff:ff:ff:ff:ff:ff
    inet 162.156.10.91/22 brd 162.156.11.255 scope global eth1
       valid_lft forever preferred_lft forever
    inet6 fe80::46d9:e7ff:fe07:73b5/64 scope link
       valid_lft forever preferred_lft forever
    Description: Internet

    RX:  bytes    packets     errors    dropped    overrun      mcast
    3396004608    2729626          0          0          0          0
    TX:  bytes    packets     errors    dropped    carrier collisions
     636239107    1506452          0          0          0          0
admin@ERX:~$ show interfaces switch switch0
switch0:  mtu 1500 qdisc pfifo_fast state UNKNOWN qlen 1000
    link/ether 44:d9:e7:07:73:be brd ff:ff:ff:ff:ff:ff
    inet 192.168.1.1/24 brd 192.168.1.255 scope global switch0
       valid_lft forever preferred_lft forever
    inet6 2001:569:7419:e101:46d9:e7ff:fe07:73be/64 scope global dynamic
       valid_lft 86134sec preferred_lft 14134sec
    inet6 2001:569:7419:e101::1/64 scope global
       valid_lft forever preferred_lft forever
    inet6 fe80::46d9:e7ff:fe07:73be/64 scope link
       valid_lft forever preferred_lft forever
    Description: Local

    RX:  bytes    packets     errors    dropped    overrun      mcast
     645390831    1556292          0          0          0          0
    TX:  bytes    packets     errors    dropped    carrier collisions
    3461080703    2802887          0          0          0          0
admin@ERX:~$ ^C

Wireless LAN adapter Wireless Network Connection 6:

   Connection-specific DNS Suffix  . : ERX
   Description . . . . . . . . . . . : Intel(R) Wireless-N 7260
   Physical Address. . . . . . . . . : 0C-8B-FD-2B-D1-A3
   DHCP Enabled. . . . . . . . . . . : Yes
   Autoconfiguration Enabled . . . . : Yes
   IPv6 Address. . . . . . . . . . . : 2001:569:7419:e101:d4db:460f:3469:bddf(Preferred)
   Temporary IPv6 Address. . . . . . : 2001:569:7419:e101:d8aa:b6e0:2f97:5a4e(Preferred)
   Link-local IPv6 Address . . . . . : fe80::d4db:460f:3469:bddf%5(Preferred)
   IPv4 Address. . . . . . . . . . . : 192.168.1.14(Preferred)
   Subnet Mask . . . . . . . . . . . : 255.255.255.0
   Lease Obtained. . . . . . . . . . : Monday, December 21, 2015 1:34:40 AM
   Lease Expires . . . . . . . . . . : Tuesday, December 22, 2015 11:45:15 AM
   Default Gateway . . . . . . . . . : fe80::46d9:e7ff:fe07:73be%5
                                       192.168.1.1
   DHCP Server . . . . . . . . . . . : 192.168.1.1
   DHCPv6 IAID . . . . . . . . . . . : 504138749
   DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-1A-BA-C9-AE-00-26-B9-01-F8-26
   DNS Servers . . . . . . . . . . . :  192.168.1.1
   NetBIOS over Tcpip. . . . . . . . : Enabled

C:\Users\Connor>

ps i have no dns set on my dhcpv6-pd so that the telus ipv4 addresses are all my router uses and all my lan clients use 192.168.1.1 running an adblocker on dnsmasq





0 Likes
Reply
Organizer

what i dont get is that the actiontec is set to prefix only but it shows a wan ipv6 address with a /56

maybe thats just the prefix its getting and not the wan address? my edgerouterx doesnt show wan address?


admin@ERX:~$ show interfaces
Codes: S - State, L - Link, u - Up, D - Down, A - Admin Down
Interface    IP Address                        S/L  Description
---------    ----------                        ---  -----------
eth0         192.168.2.3/24                    u/u  Local
eth1         162.156.10.91/22                  u/u  Internet
eth2         -                                 u/u  Local
eth3         -                                 u/u  Local
eth4         -                                 u/u  Local
lo           127.0.0.1/8                       u/u
             ::1/128
switch0      192.168.1.1/24                    u/u  Local
             2001:569:7419:e101:46d9:e7ff:fe07:73be/64
             2001:569:7419:e101::1/64
admin@ERX:~$

i have a nat destination rule for 192.168.2.3 routing back to my telus router at 192.168.2.1 so i can log into it from my bridged setup 😉

what i dont get is why my computer, my phone, and my router all seem to get different default gateways yet all be on the same /64 and none of the default gateways are like my routers address

IP Route Table for VRF "default"
K      ::/0 [0/1024] via fe80::2d0:f6ff:fe3c:2788, eth1, 08:14:54
C      ::1/128 via ::, lo, 08:18:00
C      2001:569:7419:e101::/64 via ::, switch0, 08:14:54
C      fe80::/64 via ::, eth0, 07:37:25

admin@ERX:~$


0 Likes
Reply

@Paeonius​

The reason we are handing out a /56 right now is to hopefully future proof things. We don't know what will be required in say 5 years but we can prepare for it (will there be some requirement that has all of your Kitchen appliances on one /64, your TVs on another etc etc?)

@Connor​

What you should see on the Actiontec is something like the following (IPs have been changed for this example)

IPv6 Prefix of Delegated: 2001:56a:1234::/56
IPv6 WAN Status: Connected
IPv6 WAN Address: 2001:56a:1234:ff:123:4ff:fe00:1234/64
IPv6 WAN Link Local Address: fe80::123:4ff:fe00:1234
IPv6 LAN Link Local Address: fe80::123:4ff:fe00:1233

This shows the /56 that has been delegated to the Actiontec, it also shows the IP that the Actiontec has assigned itself for it's own internet needs (2001:56a:1234:ff:123:4ff:fe00:1234/64), plus the Link Local addresses.

The IPv6 WAN Address is only used by the Actiontec itself if it needs to get to the internet, it is not used for anything else.

The IPv6 WAN Link Local address is what is used by the Actiontec and our Edge router to route packets between them.

In the example above if there was a PC with IP 2001:56a:1234:ff:10be:aff:fe00:f234 then our edge router would not forward traffic to that destination address, what it would do is look in it's route table and see that to reach 2001:56a:1234::/56 it needs to forward traffic to fe80::123:4ff:fe00:1234 (which is essentially the point to point addressing between our edge router and the RG).

Likewise for traffic from that PC to the internet, the Actiontec would forward traffic to our Edge router's link local address fe80::(something). You can see this in your example for your

gateway: K ::/0 [0/1024] via fe80::2d0:f6ff:fe3c:2788, eth1, 08:14:54

I would guess that devices in your home would be using your devices LAN Link Local address as their default gateway.

With the actiontec this would be the IPv6 LAN Link Local Address.
0 Likes
Reply
Connector

@Dan_Seibel


Thanks for your explanation. It it very encouraging. I understand now why Port 1 option was not working for me and will give it another try with just DHCP6-PD.


As for Actiontec not willing to sub-delegate any longer prefixes to its clients, I hope it will be supported at some time, otherwise what's the point of assigning /56 per customer?

0 Likes
Reply
Connector

@Matthew_Wilder,


A couple of weeks ago I was happy to discover that my Actiontec T1200H got IPv6 connectivity. I got prefix length 56, which is OK. I allows for 256 subnets, of which subnet 00 is used by the LAN side on the router and FF on the WAN side, which leaves 254 subnets for home use.


My happiness was short-lived, however, as I quickly discovered that Actiontec will not route anything to any of the assigned subnets (except for its own 00 subnet). The routing table is read-only, and the router will disregard any Router Advertisements from any other routers on the LAN side that carry routing information for other subnets.


Putting own router on PORT 1 in bridge mode as a workaround does not work either: it gets only IPv4 address, and no IPv6 address. So I had to go back to my SixXS tunnel.


It seems that the IPv6 deployment is half-working and half-broken. Or is it still more upgrade coming soon?

0 Likes
Reply

@Paeonius​

Hopefully this will help clear things up for you:

We (TELUS) are using dhcp6-pd to assign an IPv6 Prefix to the requesting router (usually an Actiontec RG). As you have noticed the prefix is /56 is size and the Actiontec is using two /64 prefixes out of that at this time (In theory those prefixes don't have to be a /64, they could be anything within that /56). The Actiontec "owns" the entire /56 prefix, so you can't just arbitrarily pick say a /64 out of that and start using it. The only way that could work is if the Actiontec in turn delegated a prefix to a requesting router on the LAN side (a feature that currently is not supported on it).

Now if you want to use your own router, you can do what you mentioned by using the port 1 bridge mode on the Actiontec and connecting your device into this. It will work fine, however there are a few issues with a majority of 3rd party devices. In order for it to work your device must:

1. Only request a dhcp6-pd (So only send IA-PD in the dhcp6 solicit message). This is what the Actiontecs actually do.

2. If the device does request both an IA-NA, and an IA-PD in the solicit message, then it must conform to RFC 7550. We are not using IA-NA so in our dhcp Advertise message there will be a NoAddrAvail message for the IA-NA, and a prefix for the IA-PD.

#2 is where most of the 3rd party devices have issues. They don't handle this case and will usually reject the dhcp advertise message that is sent down and just go into and endless solicit loop.
Reply
TELUS Employee

Hi @mtylerb​ and @skyblaster​,


I am happy to share that we are in the midst of enabling IPv6 for eligible TELUS Internet subscribers. To be eligible you must be on our Converged Edge network (true of most TELUS Internet subscribers) and have an Actiontec gateway. Zyxel gateways will be enabled with a firmware update, likely in 2016. I hope you enjoy the addition of IPv6 connectivity coming soon to you!

View solution in original post

0 Likes
Reply
Good Samaritan

Hi there!

 

IPv6 is a technology protocol.  As such, there will not be a specific IPv6 service.  Existing services will be enhanced to support IPv6 and new services will be developed which leverage the capabilities that IPv6 provides.

Today, no services offer IPv6 as an option. However, TELUS supports the move to IPv6 and have been operating experimental IPv6 networks for years. 

TELUS is making TELUS.com and TELUSMOBILITY.com available via IPv6 addressing.

To connect to our websites with IPv6, an IPv6 tunnel broker will be required.  These free brokers can be installed on personal computers from the following tunnel broker providers:

http://gogonet.gogo6.com/

http://tunnelbroker.net/register.php

Test IPv6 Connectivity:  http://test-ipv6.com/

 

Hope that helps!

0 Likes
Reply

No, unfortunetely that doesn't help as you didn't answer either of my questions.

I'm already using a free tunnel to the IPv6 Internet courtesy of Hurricane Electric. I don't mean to single Telus out. Most Canadian ISPs are behind in this transition. I just so happen to be a Telus customer and that's why I'm asking here.

0 Likes
Reply

Sorry but there's no ETA yet as to when TELUS will provide the IPv6 & no info yet for the DSLAM compatibility but stay tune for updates.

0 Likes
Reply
Friendly Neighbour

Sorry to resurface an old thread.  Any updates on this?  It's been a year and I'm really anxious to get IPv6 up and running natively.  So many issues trying to use tunnels.

0 Likes
Reply