IPv6 connectivity

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?

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


Anyone got this working with pfsense? I'm trying to get it working but not having any success.


the current solution says no ipv6.  How is ipv6 coming along?  How come telus modems dont automatically do ipv6?  Zyxtel, Alcatel, etc.


IPv6 is here in Alberta but I don't know anywhere else.


For any one using the TRENDnet TEW-812DRU and hoping to bridge it to the internet and rock some IPv6 your in for some heart ache. At least the standard firmware does not support IP6 DHCP, only static routing. There is a dd-wrt firmware version available from the trendnet site that I haven't loaded yet. But the documentation from dd-wrt about enabling IP6 makes it clear that the firmware doesn't come with iptablesv6 so if you did get it going your internal network would effectively be right on the internet.  There are ways to load iptablesV6 but it is going to be way out side of the comfort zone of 99% of users. The doc is here if you want to read it.




I am probably going to take a run at it in the near future and will post if I have success. I hope this saves some one some time.

ok, so ipv6 has been working great for me since i got it working good except for i still havnt been able to get my router its own ipv6 address, and i cant see the /56 subnet, but i can see the /64 i have assigned to my switch, really , i dont need my router to have its own ipv6 address, but i would like to figure this out...

here is my interface setup

interfaces {
    ethernet eth0 {
        description Local
        duplex auto
        firewall {
            in {
            local {
        speed auto
    ethernet eth1 {
        address dhcp
        description Internet
        dhcp-options {
            default-route update
            default-route-distance 210
            name-server update
        dhcpv6-pd {
            pd 0 {
                interface switch0 {
                    host-address ::1
                    prefix-id :1
                    service dhcpv6-stateless
                prefix-length 56
            rapid-commit enable
        duplex auto
        firewall {
            in {
                ipv6-name WANv6_IN
                name WAN_IN
            local {
                ipv6-name WANv6_LOCAL
                name WAN_LOCAL
        ipv6 {
            address {
            dup-addr-detect-transmits 1
        mac 44Man Very Happy9:E7:07:73:B5
        speed auto
    ethernet eth2 {
        description Local
        duplex auto
        speed auto
    ethernet eth3 {
        description Local
        duplex auto
        speed auto
    ethernet eth4 {
        description Local
        duplex auto
        poe {
            output pthru
            watchdog {
                failure-count 3
                interval 15
                off-delay 5
                start-delay 300
        speed auto
    loopback lo {
    switch switch0 {
        description Local
        ipv6 {
            address {
            dup-addr-detect-transmits 1
        mtu 1500
        switch-port {
            interface eth2
            interface eth3
            interface eth4

this is what the interfaces are getting assigned

i dont know why i cant see the /56

admin@ERX:~$    show interfaces
Codes: S - State, L - Link, u - Up, D - Down, A - Admin Down
Interface    IP Address                        S/L  Description
---------    ----------                        ---  -----------
eth0                    u/u  Local
eth1                 u/u  Internet
eth2         -                                 u/u  Local
eth3         -                                 u/u  Local
eth4         -                                 u/D  Local
lo                        u/u
switch0                    u/u  Local



I don't know what type of networking stack you use on your router, and especially what is your DHCPv6 client, but from the listing of interface states it seems that your router gets assigned prefix 2001:569:741e:9900::/56. You chose the subnet 01 for switch0 so your LAN will have 2001:569:741e:9901::/64, as you can see from the two IPv6 addresses the route assigns itself. What is not clear is what happens on eth1. Your listing does not show any link-local addresses. 


You say you don't need your router to have public IPv6 addresses, but Actiontec does it, so I would go with it too, at least at first, until you have everything working OK. Then you may want to experiment and deviate from the standard behaviour. There is no shortage of addresses in IPv6!


Actiontec has two addresses, one for WAN and one for LAN, on subnets FF and 00, respectively. The latter can be configured to a different value, but the former not. Your router has also two addresses, but both on the switch side, subnet 01 (one fixed by configuration to ::1, another auto configured). You need to assign a global-scope address to eth1 that is on the same subnet as the upstream router. As I said, Actiontec uses FF for that subnet, I would stick wit it. Note that you never get an IPv6 address assigned from Telus, only prefix, so make sure that your DHCPv6 client does not ask for address assignment but just configures itself from the prefix. Some clients cannot do that.

@Paeonius Ok so yes after remembering i came to the conclusion that what the actiontecs are showing as WAN ipv6 address is not a wan ipv6 address

Its more technically a lan ipv6 address then a wan address because its assigned to the lan interface, and when i have tried putting the same address on wan jnstead of lan it doesnt work so telus actiontecs are refering to the lan ipv6 address as the wan ipv6 address

As for a link local ipv6 address on eth0 i have on and my devices pick it up as default gateway and a dns server

I dont get what you mean about i have 2 ipv6 addresses the short one isnt a full public address if i understand correct??

ok so just to clarify, is telus technically using SLAAC? or Stateless DHCPv6

because both work for me

  • Static (manual) address assignment – exactly like with IPv4, you can go on and apply the address yourself. I believe this is straight forward and therefore I am not going to demonstrate that.
  • Stateless Address Auto Configuration (SLAAC) – nodes listen for ICMPv6 Router Advertisements (RA) messages periodically sent out by routers on the local link, or requested by the node using an RA solicitation message. They can then create a Global unicast IPv6 address by combining its interface EUI-64 (based on the MAC address on Ethernet interfaces) plus the Link Prefix obtained via the Router Advertisement. This is a unique feature only to IPv6 which provides simple “plug & play” networking. By default, SLAAC does not provide anything to the client outside of an IPv6 address and a default gateway. SLAAC is greatly discussed in RFC 4862.
  • Stateless DHCPv6 – with this option SLAAC is still used to get the IP address, but DHCP is used to obtain “other” configuration options, usually things like DNS, NTP, etc. The advantage here is that the DHCP server is not required to store any dynamic state information about any individual clients. In case of large networks which has huge number of end points attached to it, implementing stateless DHCPv6 will highly reduce the number of DHCPv6 messages that are needed for address state refreshment.
  • Stateful DCHPv6 – functions exactly the same as IPv4 DHCP in which hosts receive both their IPv6 address and additional parameters from the DHCP server. Like DHCP for IPv4, the components of a DHCPv6 infrastructure consist of DHCPv6 clients that request configuration, DHCPv6 servers that provide configuration, and DHCPv6 relay agents that convey messages between clients and servers when clients are on subnets that do not have a DHCPv6 server. You can learn more about DHCP for IPv6 in RFC 3315.

NOTE: The only way to get a default gateway in IPv6 is via a RA message. DHCPv6 does not carry default route information at this time.


Just to clarify: none of the above. The world of IPv6 is richer than that. The options above are for regular nodes, but for routers there are more possibilities, and Telus uses one of those. If your router software supports only the options you listed, then you are out of luck. You better replace the software or get a different router which can do what is required. It tested three different DHCPv6 clients before finding one that could do what was required here, and got it working only after significant customization with hook scripts.


Now the problem:

Telus does not use SLAAC to configure on-premises networks. RA messages are broadcast around quite infrequently, and they do not contain the prefix option. Telus prefixes are leased out, which makes the protocol stateful. Also, the M bit (managed) in RA is cleared, which means that the client should not attempt to obtain a Non-temporary Address (NA) through DHCPv6. It you request NA anyway, you just get error "No addresses available" back. Also the O bit (other information) in RA is cleared, which I believe is technically not correct (because you can get DNS servers through DHCPv6) but inconsequential. You get DNS addresses delivered anyway when you do a PD request, besides DNS is the least of your problems now. My guess is that Telus sets the O bit to zero just not to trick clients to assume that stateless DHCPv6 is the way to go with the prefix just temporarily missing.


So, to summarize: no RA-based SLAAC, and no stateless DHCPv6.


Telus uses stateful DHCPv6, but only for Prefix Delegation (PD), and not for Non-temporary Address (NA). This distinction is important, as many DHCPV6 clients assume that once you use stateful DHCPv6, you will get a global scope address from a NA request. This is a wrong assumption and will not work with Telus. The client must only request a PD, and then use this prefix to configure its interfaces, both LAN and WAN. It appears that your client does it correctly for the LAN side, most of them do. What it does is it takes the prefix assigned from Telus, (in your case it is 2001:569:741e:9900/56), completes it with a subnet number (in your case 01, probably because you specified prefix-id :1 in your configuration) which creates prefix 2001:569:741e:9901/64, and then generates two global scope IPv6 addresses on switch0. One is 2001:569:741e:9901::1, (because you hard-coded host-address to ::1), another one is EUI-64-generated 2001:569:741e:9901:46d9:e7ff:fe07:73be/64 (because you requested autoconf on switch0). So yes, you do have now two global scope IPv6 addresses on the LAN interface. One would be enough.


So far so good. What is missing is the address on the WAN interface (eth1). If your router is expecting an address on eth1 from Telus through SLAAC (is that the meaning of autoconf on eth1?) then it will never get configured. If it uses DHCPv6 NA requests, it will never get configured either. What it should do instead is exactly the same what it did on switch0: create a subnet (use FF), and an arbitrary host ID, (based on EUI-64 like Actiontec, or simply ::1 will be probably OK too), and use this to assign an IPv6 address to eth1. For instance, in your case it could  be 2001:569:741e:99FF::1/64, assuming you sill lease the same prefix as in your previous post. To test it, you may try temporarily assigning this address statically to eth1 and see whether you get connectivity. Caveat: we haven't discussed routing yet, and routing configuration with Telus also poses its own challenges. For now, just in case you do not get connectivity right away, just wait a few hours (without rebooting your router) to get one of the heartbeat RA and try again.

well my connectivity is actually working perfectly so there is really no need to change anything but you are probably right in that i only need one address, no idea why i would need a wan address....

ive figured everything out now and i have full ipv6 connectivity no problems im using SLAAC

i am not sending ia-na requests, they cause a 100% cpu problem, edgeos has a prefix-only option, and when i turned autoconf on it messed up everything  but yes by default slaac will send ia-na request

TELUS Employee

Hmm what you are showing is interesting, and something doesn't seem to be working right.  The dhcp options won't have anything to do with if a RA gets sent or not (or they shouldn't).

Do you know if you are on GPON or DSL?

I may need some more info to take a look into this, I will send you a PM this week.



Thanks for explaining that RS will never be answered; so I did not waste time chasing that path.

Instead of that, I spent some time in the search for the ever-elusive out-of-schedule RA after the DHCPv6 exchange. RA was not coming. Then I realized that on reboot my prefix lease is still valid (it has a preferred lifetime 2 days, and maximum 4 days) so my router did not do the full binding procedure, it just picked up the valid lease and did the quick rebind (request-reply exchange). So in another attempt I forced the dhclient to do the full solicit-adverise-request-reply, maybe that is what the edge router needs for RA. RA was not coming.

My normal sequence is DHCPv4 first, then DHCPv6. So I played with that: DHCPv6 first, then DHCPv4. No RA. Then only DHCPv6, without DHCPv4. No RA.

Here is a complete IPv6 packet sequence for the first 5 minutes after link up. No RA in sight.

No.     Time    Source                Destination           Protocol Length Info
      1 0.00    ::                    ff02::16              ICMPv6   130    Multicast Listener Report Message v2
      2 0.08    ::                    ff02::1:ff3b:7992     ICMPv6   78     Neighbor Solicitation for fe80::21f:e2ff:fe3b:7992
      3 0.18    fe80::21f:e2ff:fe3b:7992 ff02::16              ICMPv6   150    Multicast Listener Report Message v2
      4 0.18    fe80::21f:e2ff:fe3b:7992 ff02::2               ICMPv6   70     Router Solicitation from 00:1f:e2:3b:79:92
      5 0.19    fe80::21f:e2ff:fe3b:7992 ff02::16              ICMPv6   150    Multicast Listener Report Message v2
      6 0.28    fe80::21f:e2ff:fe3b:7992 ff02::16              ICMPv6   150    Multicast Listener Report Message v2
      7 0.79    fe80::21f:e2ff:fe3b:7992 ff02::16              ICMPv6   90     Multicast Listener Report Message v2
      8 0.81    fe80::21f:e2ff:fe3b:7992 ff02::1:2             DHCPv6   112    Solicit XID: 0x3f8650 CID: 000100011dfd1b55001fe23b7992
      9 1.89    fe80::21f:e2ff:fe3b:7992 ff02::1:2             DHCPv6   112    Solicit XID: 0x3f8650 CID: 000100011dfd1b55001fe23b7992
     10 1.92    fe80::225:baff:fe51:93d0 fe80::21f:e2ff:fe3b:7992 DHCPv6   179    Advertise XID: 0x3f8650 CID: 000100011dfd1b55001fe23b7992
     11 1.92    fe80::21f:e2ff:fe3b:7992 ff02::1:2             DHCPv6   155    Request XID: 0x285e91 CID: 000100011dfd1b55001fe23b7992
     12 2.22    fe80::225:baff:fe51:93d0 fe80::21f:e2ff:fe3b:7992 DHCPv6   179    Reply XID: 0x285e91 CID: 000100011dfd1b55001fe23b7992
     13 2.38    fe80::21f:e2ff:fe3b:7992 ff02::16              ICMPv6   150    Multicast Listener Report Message v2
     14 2.54    ::                    ff02::1:ff3b:7992     ICMPv6   78     Neighbor Solicitation for 2001:569:be10:c2ff:21f:e2ff:fe3b:7992
     15 2.56    fe80::21f:e2ff:fe3b:7992 ff02::16              ICMPv6   150    Multicast Listener Report Message v2
     16 4.19    fe80::21f:e2ff:fe3b:7992 ff02::2               ICMPv6   70     Router Solicitation from 00:1f:e2:3b:79:92
     17 8.19    fe80::21f:e2ff:fe3b:7992 ff02::2               ICMPv6   70     Router Solicitation from 00:1f:e2:3b:79:92
     18 143.51  fe80::225:baff:fe51:93d0 fe80::21f:e2ff:fe3b:7992 ICMPv6   86     Neighbor Solicitation for fe80::21f:e2ff:fe3b:7992 from 00:25:ba:51:95:17
     19 143.51  fe80::21f:e2ff:fe3b:7992 fe80::225:baff:fe51:93d0 ICMPv6   78     Neighbor Advertisement fe80::21f:e2ff:fe3b:7992 (rtr, sol)
     20 148.52  fe80::21f:e2ff:fe3b:7992 fe80::225:baff:fe51:93d0 ICMPv6   86     Neighbor Solicitation for fe80::225:baff:fe51:93d0 from 00:1f:e2:3b:79:92
     21 148.53  fe80::225:baff:fe51:93d0 fe80::21f:e2ff:fe3b:7992 ICMPv6   86     Neighbor Advertisement fe80::225:baff:fe51:93d0 (rtr, sol, ovr) is at 00:25:ba:  51:95:17

What is strange is that Actiontec does get its IPv6 route set right after boot, so it is getting its RA somehow. I wonder what is the difference. Some specific DHCPv6 options required by the edge router?

TELUS Employee


Glad to see you got things working!

Now to your other issue.  After the dhcp process is completed, our router will send out a RA right after the dhcp reply so you should see something like:

      1 0.000000       fe80::1               ff02::1:2             DHCPv6   209    Relay-forw L: :: Solicit XID: 0x90 CID: 000200000d800001
      2 0.068277       fe80::221:5ff:fec3:c424 fe80::1               DHCPv6   236    Relay-reply L: :: Advertise XID: 0x90 CID: 000200000d800001
      3 1.000588       fe80::1               ff02::1:2             DHCPv6   223    Relay-forw L: :: Request XID: 0x91 CID: 000200000d800001
      4 1.412554       fe80::221:5ff:fec3:c424 fe80::1               DHCPv6   236    Relay-reply L: :: Reply XID: 0x91 CID: 000200000d800001
      5 2.195250       fe80::221:5ff:fec3:c424 fe80::1               ICMPv6   86     Router Advertisement from 00:21:05:6c:9d:ac

For the RS messages those don't get responded to, that is a security function of the edge network.  We are looking to see if there are possible enhancements that can be made in this area, but no idea currently on timing for that.

I'm trying to get my pfsense router working with native ipv6. I'm not getting anywhere, despite setting it for prefix delegation. I haven't been able find out why it's not working. However, I've been reading several RFCs, specifically RFC 3633, which seems to be written specifically for this particular application. It pretty clearly states that when a requesting router sends a solicit message, the delegating router is supposed to respond with an advertise message. Unless I've completely misunderstood your comment, it seems that the edge routers are bug compatible with the Actiontec, rather than being compliant with standards written for the specific purpose. It's not like any of this is new technology. RFC 3633 is dated 2003. I can't imagine what the reason would be to not use standards-based methods to allow subscribers to connect their routers using native ipv6.


Additionally, it appears that it's not possible for a host to acquire an ipv6 address. At least it didn't work for me. Not sure why this wouldn't be supported either.



Assigning a shorter prefix to be prepared for future is a smart move. I hope that it means the prefixes we are getting assigned now will turn out to be pretty stable.

As for my IPv6 connectivity I want to to report a success. Based on your advice, I configured my router to only request Prefix Delegation (PD) without Non-temporary Address (NA), and it worked! I played with several DHVPv6 capable clients, but eventually settled on the standard dhclient from Internet Systems Consortium (ISC). The same I use for DHCPv4. Works like a charm, and fast too, an order of magnitude faster than DHCPv4. The DHCPv6 reply contains a /56 prefix and as a bonus two IPv6 addresses of Telus recursive DNS servers. Based on the prefix and following what Actiontec does, I assign to the WAN interface address of my router an address on subnet prefix+FF/64 (with interface ID based on MAC, following RFC 2464), and the LAN address on subnet prefix+00/64, with a custom host ID. Further down the line, all LAN hosts get Router Advertisement messages from my router with the LAN prefix (/64) and auto configure themselves accordingly. And it works! I get full IPv6 connectivity form all my devices.

There is only one problem remaining: routing. DHCPv6, unlike DHCPv4, does not carry routing information. In the IPv6 world, routing is configured by ICMPv6 message type 134: Router Advertisement (RA). Telus Edge router does send out RA messages at regular intervals (ca. 22 min), with a valid route to a link-local address of the edge router. The route is valid for 75 minutes, but will be refreshed long before it expires. My router does autoconfiguration of its default route when it receives RA from the Edge router and everything works fine after that. The problem is on booting: it may take up to 22 minutes for my router to receive RA from the Edge router, and until then IPv6 Internet connection is not working. The canonical solution to this problem is sending a Router Solicitation message (RS), ICMPv6 type 133, as described in RFC 4861, to the all-routers multicast address ff02::2, to which the Edge router should reply with an out-of-schedule RA message. However, despite my sending of tons of RS messages, the Edge router never replies with an RA message; it always sends them according to its own schedule. Am I missing something here again? Do I need to register my MAC or DUID somewhere so that the Telus router will listen to my solicitations? If so, where? What am I doing wrong?



Hi, how in the world did you configure ISC dhclient to request IA_PD only? I can't find any documentation or examples on the internet. It seems my google-fu is too weak. May I ask that you share your configuration?


Also, how did you configure radvd (I'm assuming you're using this? If you're using ISC dhcpd then I am convinced you are some sort of higher-dimensional being) to use the prefix info from dhclient?


Finally, I saw your comment about the O flag in the Telus RA notification being incorrectly cleared but I read on this website (https://wikispaces.psu.edu/display/ipv6/DHCPv6) that the M and O flags are independent of each other. The website says that the M flag enables/disables stateful dhcpv6 and the O flag enables/disables stateless dhcpv6. It also mentions that it is possible to use both stateful and stateless dhcpv6 and that it is a common misconception that the M flag refers to SLAAC specifically (at least that was my understanding).


If my understanding is correct, the M flag is set to indicate that we require IA PD and DNS addresses (stateful dhcpv6 or M flag == 1) and that we do not need any other info from the dhcpv6 server for stateless autoconfig (stateless dhcpv6 disabled or O flag == 0). This is true because we are given an entire /56 subnet and therefore need no other parameter for stateless dhcpv6 other than our own MAC address for LAN ipv6 and (I'm assuming) some sort of algorithm that is built into Linux for ipv6 privacy extensions that we use for our global ipv6 address


EDIT: I also want to add that I'm aware of dhclient -6 -P command but I assumed you edited your dhclient.conf to request for IA_PD and DNS addresses. I have absolutely no idea how to setup the dhclient.conf properly and it all seems like pig latin to me. All the examples of dhclient.conf I've found are for ipv4.


Thanks in advanced!

@ckim44, I've just noticed your post. 


You are correct to use dhclient -P command to obtain PD. The contents of dhclient.conf is of little importance as it seems that Telus router ignores most (if not all) options passed. I suspect it is due to their system security policy. So you should be already getting a prefix from Telus. If you enable the verbose mode (option -v) on dhclient, you should be seeing something like:



Internet Systems Consortium DHCP Client 4.3.3
Copyright 2004-2015 Internet Systems Consortium.
All rights reserved.
For info, please visit https://www.isc.org/software/dhcp/

Listening on Socket/eth1
Sending on   Socket/eth1
PRC: Confirming active lease (INIT-REBOOT).
XMT: Forming Rebind, 0 ms elapsed.
XMT:  X-- IA_PD e2:3b:79:92
XMT:  | X-- Requested renew  +3600
XMT:  | X-- Requested rebind +5400
XMT:  | | X-- IAPREFIX 2001:569:xxxx:xxxx::/56
XMT:  | | | X-- Preferred lifetime +7200
XMT:  | | | X-- Max lifetime +7500
XMT:  V IA_PD appended.
XMT: Rebind on eth1, interval 990ms.
RCV: Reply message on eth1 from fe80::225:baff:fe51:93d0.
RCV:  X-- IA_PD e2:3b:79:92
RCV:  | X-- starts 1496634852
RCV:  | X-- t1 - renew  +7200
RCV:  | X-- t2 - rebind +10800
RCV:  | X-- [Options]
RCV:  | | X-- IAPREFIX 2001:569:xxxx:xxxx::/56
RCV:  | | | X-- Preferred lifetime 14400.
RCV:  | | | X-- Max lifetime 86400.
RCV:  X-- Server ID: 00:03:00:01:00:25:ba:51:93:d0
PRC: Bound to lease 00:03:00:01:00:25:ba:51:93:d0.


Look for the line RCV:  | | X-- IAPREFIX 2001:569:xxxx:xxxx::/56, this is your prefix.


After that, dhclient is supposed to configure the local host accordingly. This is where the fun begins, because dhclient, out of the box, does not support configuration based on prefix only.


Since it is over a year from your question, I don't know whether you are still interested in the answer, maybe you have figured it out in the meantime. But I am happy to share with you my solution, just let me know.


As for the O flag: you are right that it is independent from M. When the O flag is set it means that the server can provide "other" stateless information, like nameservers, which Telus does provide. 

Thanks for the reply. The problem is that Telus' edge routers don't respond to RS with an RA until after the DHCP solicit message is sent. In the case of pfsense, by design, it sends the RS first and waits for an RA before sending the DHCP solicit. According to Telus, the reason for this is "security". Some other ISPs have their edge routers configured similarly, and fortunately one of the pfsense users developed a fix for this, which also works on the Telus network.


ok, so your saying fe80::46d9:e7ff:fe07:73b5/64  is my IPV6 WAN link local address?

i agree

but on the telus router the IP address that the device it assigns itself, it used the last digits from the IPV6 WAN link local address

wheras my router uses the last digits from my IPV6 LAN link local address

so i guess my router is placing its own IPV6 address on the LAN simply because ipv6 can work like this wheras the actiontec puts its own IPV6 as being on the wan because this is how things typically making sense

as normally lan ips are private and wan ips are not

so is it that the edgerouter is taking its own IP and placing it in the lan wheras the actiontec is taking it and putting it on the wan?

so where you say

"Devices in your home that connect to your router would most likely have a default gateway of


the default gateway on my devices is the IPV6 WAN link local address, and not the IPV6 LAN link local address like it would be on the actiontec


but yes i believe my gateway should be fe80::46d9:e7ff:fe07:73be

its wierd my routers IPV6 address is 2001:569:7419:e101:46d9:e7ff:fe07:73be/64 unding with BE (my IPV6 LAN link local address) instead of ending with the WAN IPV6 link local address and having fe80::46d9:e7ff:fe07:73be as my default gateway..

TELUS Employee

I have never played with that device but looking at your output I think:

This address would be your ipv6 WAN address (on eth0):

inet6 fe80::46d9:e7ff:fe07:73b5/64 

And that is what would be talking to our Edge router.  The default gateway for your router would also be a link local address that should show up in the router's route table.

Devices in your home that connect to your router would most likely have a default gateway of


And I assume they are all getting addressing in the 2001:569:7419:e101::/64 range?

It looks like your router has assigned itself this IP out of that range:


and I would assume is using that for it's own IPv6 internet connectivity, similar to what the Actiontec calls the IPv6 WAN Address.  These addresses are used for the RG to communicate with the internet, but they aren't a WAN address used for routing traffic to and from clients connected behind them out to the internet.