cancel
Showing results for 
Search instead for 
Did you mean: 
10megaton
Beginner
5,491 Views
Message 1 of 15

IPv6 with third-party routers

I've read on ISP review that IPv6 is now enabled everywhere on BT Infinity Broadband, however does anyone know if it works with third-party routers?

 

I can't get an IPv6 address using PPPoE on both Sophos UTM and PfSense, however if I use the Smart Hub 6 I get an IPv6 address every time. I'm assuming that at present IPv6 is not blanket-enabled and it must detect if you are using a Smart Hub 6, hence third-party routers do not work at this time?

 

Can anyone confirm this, and if it is the case when will we be able to use IPv6 on third-party equipment?

 

Cheers, 10M

Tags (4)
0 Ratings
Reply
14 REPLIES 14
Liam_
Expert
5,480 Views
Message 2 of 15

Re: IPv6 with third-party routers

Hi,

I read that article as well.  But the jury is still out on the actual live coverage.  Some folks report in the forum that they can't get IPv6 working in their area.  However to answer your question, yes works fine or rather should work fine on third party kit.

IPv6 enabled for me, (Alexandria, Dunbartonshire) since April 8.

Been running my FTP server exclusively on IPv6 for a while now.  I think the coverage is still a little spotty.  If the Hub 6 gets one I can see no reason for the third party kit not to.  Subject to firmware issues that is, as reported on at least one device in the forum.

Here:

https://community.bt.com/t5/Connected-Devices-Other/Infinity-2-and-Tenda-AC15-Router/m-p/1657915#M12...

 

No problems here using a Fritzbox.

0 Ratings
Reply
Distinguished Sage
Distinguished Sage
5,473 Views
Message 3 of 15

Re: IPv6 with third-party routers

Not sure what the situation is at the moment, I have yet to get IPv6 working on a TP Link TD-W9980.

There are a couple threads https://community.bt.com/t5/Connected-Devices-Other/IPv6-settings-for-TP-Link-Archer-C6/td-p/1682377 and https://community.bt.com/t5/Connected-Devices-Other/IPv6-on-Tp-Link-TD-W9980/m-p/1672827#M128882

0 Ratings
Reply
10megaton
Beginner
5,403 Views
Message 4 of 15

Re: IPv6 with third-party routers

I'm pretty sure that there is something that is only allowing IPv6 for connections coming from a Smart Hub 6. It would be good to get an 'official' response but I'll not hold my breath. I know some users have managed to get IPv6 running on third-party kit, but there are plenty of others that have failed using a wide variety of devices.

 

Is IPv6 just disabled or hidden on the previous versions of the Smart / Home Hubs, which BT will eventually enable remotely when they add support for earlier versions of their CPE?

 

 

0 Ratings
Reply
Highlighted
kanthamohan
Aspiring Contributor
5,306 Views
Message 5 of 15

Re: IPv6 with third-party routers

The PPP layer (PPPoE)  reports a successful IPV6CP layer being UP. However I believe DHCP6 is not setup to issue ipv6 addresses to CPEs that BT believes are not yet HH6.  

 

My DHCP6C client reports that IPV6 addresses not being available,  in the IPV6 council meet in Oct 2016 the guy from BT claimed that customers using 3rd party CPEs should get it now, but it would appear that BT have to do something to enable it for customers. It is a shame that it is only enabled for customers with BT HH6 

0 Ratings
Reply
Liam_
Expert
5,297 Views
Message 6 of 15

Re: IPv6 with third-party routers

Hi,

Sorry guys, but you do not need a HH6 to get IPv6.  Just a proper router with IPv6 enabled.  Screen shot today 16:48.

IPv6.jpg

0 Ratings
Reply
Distinguished Sage
Distinguished Sage
5,296 Views
Message 7 of 15

Re: IPv6 with third-party routers

@kanthamohanThat would appear to be consistent with my findings. I can see a Link Local Gateway address on the BRAS but don't get served an IPv6 address on either a TP-Link Router, a directly connected to anOpenreach modem PC or directly connected Linux box.

0 Ratings
Reply
Distinguished Sage
Distinguished Sage
5,291 Views
Message 8 of 15

Re: IPv6 with third-party routers


@Liam_ wrote:

Hi,

Sorry guys, but you do not need a HH6 to get IPv6.  Just a proper router with IPv6 enabled.  Screen shot today 16:48.

IPv6.jpg


I think that must depend on how BT have enabled the BRAS.

0 Ratings
Reply
smf22
Recognised Expert
5,281 Views
Message 9 of 15

Re: IPv6 with third-party routers

Agreed that it's not just Hub 6 that can get an IPv6 address. No GUI, but still IPv6 running as of today:

 

 

smf22@erx:~$ show interfaces
Codes: S - State, L - Link, u - Up, D - Down, A - Admin Down
Interface    IP Address                        S/L  Description
---------    ----------                        ---  -----------
eth0         -                                 u/u  WAN via Huawei HG612 LAN 1
[snip]
lo 127.0.0.1/8 u/u ::1/128 pppoe0 217.XXX.XXX.36 u/u switch0 192.168.1.254/24 u/u Home LAN 2a00:23c5:5501:bd01::1/64

 

The IPv6 address is requested by the router using IPv6 DHCPv6 Prefix Delegation and then clients on the LAN get address within the prefix via Stateless Autoconfiguration (SLAAC).

 

 

What I did notice when I was using the HH6 is that upon WAN link establishment it would sometimes get an IPv6 address, and other times not, leading me to believe that not all BRAS were enabled. To be fair to BT, that was before the "formal" announcement that all BT broadband lines were IPv6 enabled. I've had no problems with IPv6 over recent weeks.

0 Ratings
Reply
smf22
Recognised Expert
5,277 Views
Message 10 of 15

Re: IPv6 with third-party routers


@kanthamohan wrote:

The PPP layer (PPPoE)  reports a successful IPV6CP layer being UP. However I believe DHCP6 is not setup to issue ipv6 addresses to CPEs that BT believes are not yet HH6.  

 

My DHCP6C client reports that IPV6 addresses not being available 


As per my other post, the router MUST run DHCPv6-PD (Prefix Delegation) as per RFC 3633. The DHCP messages are the same format etc., as standard DHCPv6 client, but PD is a different option, that being option 25.

 

Here's what the request looks like within Wireshark etc.

 

[snip]
User Datagram Protocol, Src Port: 546 (546), Dst Port: 547 (547) Source Port: 546 Destination Port: 547 Length: 93 Checksum: 0x706e [validation disabled] [Good Checksum: False] [Bad Checksum: False] [Stream index: 0] DHCPv6 Message type: Solicit (1) Transaction ID: 0xf61d35 Client Identifier Option: Client Identifier (1) Length: 14 Value: 000100011fbf414d44d9e7505b7e DUID: 000100011fbf414d44d9e7505b7e DUID Type: link-layer address plus time (1) Hardware type: Ethernet (1) DUID Time: Nov 16, 2016 16:09:49.000000000 GMT Link-layer address: 44:d9:e7:50:5b:7e Rapid Commit Option: Rapid Commit (14) Length: 0 Elapsed time Option: Elapsed time (8) Length: 2 Value: 0000 Elapsed time: 0 ms Option Request Option: Option Request (6) Length: 4 Value: 00170018 Requested Option code: DNS recursive name server (23) Requested Option code: Domain Search List (24) Identity Association for Prefix Delegation Option: Identity Association for Prefix Delegation (25) Length: 41 Value: 000000000000000000000000001a0019ffffffffffffffff... IAID: 00000000 T1: 0 T2: 0 IA Prefix Option: IA Prefix (26) Length: 25 Value: ffffffffffffffff38000000000000000000000000000000... Preferred lifetime: infinity Valid lifetime: infinity Prefix length: 56 Prefix address: ::

And here's the reply:

 

User Datagram Protocol, Src Port: 547 (547), Dst Port: 546 (546)
    Source Port: 547
    Destination Port: 546
    Length: 93
    Checksum: 0x7dce [validation disabled]
        [Good Checksum: False]
        [Bad Checksum: False]
    [Stream index: 1]
DHCPv6
    Message type: Reply (7)
    Transaction ID: 0xf61d35
    Server Identifier
        Option: Server Identifier (2)
        Length: 10
        Value: 0003000100233e6ee650
        DUID: 0003000100233e6ee650
        DUID Type: link-layer address (3)
        Hardware type: Ethernet (1)
        Link-layer address: 00:23:3e:6e:e6:50
    Client Identifier
        Option: Client Identifier (1)
        Length: 14
        Value: 000100011fbf414d44d9e7505b7e
        DUID: 000100011fbf414d44d9e7505b7e
        DUID Type: link-layer address plus time (1)
        Hardware type: Ethernet (1)
        DUID Time: Nov 16, 2016 16:09:49.000000000 GMT
        Link-layer address: 44:d9:e7:50:5b:7e
    Rapid Commit
        Option: Rapid Commit (14)
        Length: 0
    Identity Association for Prefix Delegation
        Option: Identity Association for Prefix Delegation (25)
        Length: 41
        Value: 0000000000093a8000127500001a001912cc030012cc0300...
        IAID: 00000000
        T1: 604800
        T2: 1209600
        IA Prefix
            Option: IA Prefix (26)
            Length: 25
            Value: 12cc030012cc0300382a0023c55501bd0000000000000000...
            Preferred lifetime: 315360000
            Valid lifetime: 315360000
            Prefix length: 56
            Prefix address: 2a00:23c5:5501:bd00::

 

Regards

0 Ratings
Reply