[SOLVED] BT HomeHub 5a and BT Infinity can't connect

Hello everyone,

I have already been hammering the irc channel with my problem but unfortunately as of today I am still unable to connect the modem to my BT Infinity Broadband.

I am using PPoE, Annex B, VDSL and tone a.

As login credentials... here comes the fun stuff. If I use: "username bthomehub@btinternet.com; password bt", it seems like the modem does authenticate and connect with the cabinet, acquires CGN IP and Public IP but hang up few ms later.

Instead if I use my BT login credentials, the modem connects to a sort of testings environment which does not serve any internet traffic whatsoever and default every requests to 62.6.38.125, which if you open it via browser it will tell you that you are connected to a testing environment kind of like.

Following is my current setup as well as useful logs:

config dsl 'dsl'
        option annex 'b'
        option xfer_mode 'ptm'
        option line_mode 'vdsl'
        option ds_snr_offset '0'
        option tone 'a'

config interface 'wan'
        option proto 'pppoe'
        option delegate '0'
        option ifname 'dsl0.101'
        option username 'bthomehub@btinternet.com'
        option password 'bt'

config device 'wan_dev'
        option name 'dsl0'
        option macaddr '34:8a:ae:96:e5:eb'
root@OpenWrt:~# ifstatus wan
{
        "up": false,
        "pending": true,
        "available": true,
        "autostart": true,
        "dynamic": false,
        "proto": "pppoe",
        "device": "dsl0.101",
        "data": {

        },
        "errors": [
                {
                        "subsystem": "pppoe",
                        "code": "HANGUP"
                }
        ]
}
root@OpenWrt:~#
root@OpenWrt:~# /etc/init.d/dsl_control status
ATU-C Vendor ID:                          Infineon 178.6
ATU-C System Vendor ID:                   45,43,49,20,74,65,6C,65
Chipset:                                  Lantiq-VRX200
Firmware Version:                         5.7.9.9.0.6
API Version:                              4.17.18.6
XTSE Capabilities:                        0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x2
Annex:                                    B
Line Mode:                                G.993.2 (VDSL2)
Profile:                                  17a
Line State:                               UP [0x801: showtime_tc_sync]
Forward Error Correction Seconds (FECS):  Near: 19 / Far: 3544
Errored seconds (ES):                     Near: 0 / Far: 83
Severely Errored Seconds (SES):           Near: 0 / Far: 0
Loss of Signal Seconds (LOSS):            Near: 0 / Far: 373
Unavailable Seconds (UAS):                Near: 35 / Far: 35
Header Error Code Errors (HEC):           Near: 0 / Far: 0
Non Pre-emtive CRC errors (CRC_P):        Near: 0 / Far: 0
Pre-emtive CRC errors (CRCP_P):           Near: 0 / Far: 0
Power Management Mode:                    L0 - Synchronized
Latency [Interleave Delay]:               8.0 ms [Interleave]   5.0 ms [Interleave]
Data Rate:                                Down: 55.000 Mb/s / Up: 9.999 Mb/s
Line Attenuation (LATN):                  Down: 8.6 dB / Up: 6.2 dB
Signal Attenuation (SATN):                Down: 8.6 dB / Up: 6.1 dB
Noise Margin (SNR):                       Down: 13.3 dB / Up: 16.0 dB
Aggregate Transmit Power (ACTATP):        Down: -4.0 dB / Up: -3.9 dB
Max. Attainable Data Rate (ATTNDR):       Down: 95.473 Mb/s / Up: 26.621 Mb/s
Line Uptime Seconds:                      109
Line Uptime:                              1m 49s
root@OpenWrt:~#
Sun Mar 18 03:25:37 2018 daemon.notice netifd: Interface 'wan' is now down
Sun Mar 18 03:25:37 2018 daemon.notice netifd: Interface 'wan' is disabled
Sun Mar 18 03:25:37 2018 daemon.notice netifd: Interface 'wan' is enabled
Sun Mar 18 03:25:37 2018 daemon.notice netifd: Interface 'wan' is setting up now
Sun Mar 18 03:25:37 2018 daemon.err insmod: module is already loaded - slhc
Sun Mar 18 03:25:37 2018 daemon.err insmod: module is already loaded - ppp_generic
Sun Mar 18 03:25:37 2018 daemon.err insmod: module is already loaded - pppox
Sun Mar 18 03:25:37 2018 daemon.err insmod: module is already loaded - pppoe
Sun Mar 18 03:25:37 2018 daemon.err dnsmasq[5076]: bad address at /etc/hosts line 2
Sun Mar 18 03:25:37 2018 daemon.err dnsmasq[5076]: bad address at /etc/hosts line 3
Sun Mar 18 03:25:37 2018 daemon.err dnsmasq[5076]: bad address at /etc/hosts line 4
Sun Mar 18 03:25:37 2018 daemon.info dnsmasq[5076]: read /etc/hosts - 1 addresses
Sun Mar 18 03:25:37 2018 daemon.info dnsmasq[5076]: read /tmp/hosts/dhcp.cfg01411c - 1 addresses
Sun Mar 18 03:25:37 2018 daemon.info dnsmasq-dhcp[5076]: read /etc/ethers - 0 addresses
Sun Mar 18 03:25:38 2018 daemon.info pppd[17577]: Plugin rp-pppoe.so loaded.
Sun Mar 18 03:25:38 2018 daemon.info pppd[17577]: RP-PPPoE plugin version 3.8p compiled against pppd 2.4.7
Sun Mar 18 03:25:38 2018 daemon.notice pppd[17577]: pppd 2.4.7 started by root, uid 0
Sun Mar 18 03:25:38 2018 daemon.info pppd[17577]: PPP session is 6305
Sun Mar 18 03:25:38 2018 daemon.warn pppd[17577]: Connected to a4:7b:2c:2d:17:63 via interface dsl0.101
Sun Mar 18 03:25:38 2018 kern.info kernel: [  211.991695] pppoe-wan: renamed from ppp0
Sun Mar 18 03:25:38 2018 daemon.info pppd[17577]: Using interface pppoe-wan
Sun Mar 18 03:25:38 2018 daemon.notice pppd[17577]: Connect: pppoe-wan <--> dsl0.101
**Sun Mar 18 03:25:38 2018 daemon.info pppd[17577]: CHAP authentication succeeded: CHAP authentication success**
**Sun Mar 18 03:25:38 2018 daemon.notice pppd[17577]: CHAP authentication succeeded**
Sun Mar 18 03:25:38 2018 daemon.notice pppd[17577]: peer from calling number A4:7B:2C:2D:17:63 authorized
Sun Mar 18 03:25:38 2018 daemon.err pppd[17577]: IPv6 socket creation failed: Address family not supported by protocol
Sun Mar 18 03:25:38 2018 daemon.err pppd[17577]: IPv6 socket creation failed: Address family not supported by protocol
**Sun Mar 18 03:25:38 2018 daemon.notice pppd[17577]: local  IP address 109.156.246.196**
**Sun Mar 18 03:25:38 2018 daemon.notice pppd[17577]: remote IP address 172.16.18.175**
**Sun Mar 18 03:25:38 2018 daemon.notice pppd[17577]: primary   DNS address 81.139.56.100**
**Sun Mar 18 03:25:38 2018 daemon.notice pppd[17577]: secondary DNS address 81.139.57.100**
Sun Mar 18 03:25:38 2018 daemon.info pppd[17577]: LCP terminated by peer
Sun Mar 18 03:25:38 2018 daemon.info pppd[17577]: Connect time 0.0 minutes.
Sun Mar 18 03:25:38 2018 daemon.info pppd[17577]: Sent 0 bytes, received 0 bytes.
**Sun Mar 18 03:25:38 2018 daemon.notice pppd[17577]: Modem hangup**
**Sun Mar 18 03:25:38 2018 daemon.notice pppd[17577]: Connection terminated.**
Sun Mar 18 03:25:38 2018 daemon.info pppd[17577]: Sent PADT
root@OpenWrt:~# 

Also, when I try to connect with the actual BT username and password one should use for PPoE, this message "[ 756.062794] pppoe-wan: renamed from ppp0" is spammed endlessly in serial console. Instead if I use my BT credentials it will just be displayed once and after connection is established.

So far login with my BT credentials is the only way to keep the modem connected, but than again I have no use of it as it is a testing environment.

I have been onto this for the past 3 days and I am very close to give up, sadly. At least I want to know whether BT is at blame, if there is a configuration issue, or if openwrt is not compatible with BT Infinity or what. Oh yes, I used both latest realest and latest snapshot but made no difference.

Lastly I tried few fws with vectoring enabled from here https://xdarklight.github.io/lantiq-xdsl-firmware-info but made no difference.

Any help is greatly appreciated. Thanks

Do you see the same symptoms if you use LEDE 17.01.4 stable instead of the OpenWRT snapshot currently installed on your hub ?

No I did not, though I can honestly give it a go later today.

Thanks for the suggestion.

In the end flashing LEDE Reboot 17.01.4 r3560-79f57e422d fixed the issue. At this point I am not sure whether the issue resides in the dsl renaming patch or on the PPPoE stack in the kernel.

Anyways, here is my network + firewall + igmpproxy configs for the BT HomeHub 5a with LEDE Reboot 17.01.4 r3560-79f57e422d which works with BT Infinity BroadBand and the BT YouView box.

To get BT YouView working you will need kmod-bridge and imgpproxy. Do not forget to enable imgpproxy at the end of the setup.

# /etc/config/network

config dsl 'dsl'
        option annex 'b'
        option xfer_mode 'ptm'
        option line_mode 'vdsl'
        option ds_snr_offset '0'
        option tone 'a'
        option firmware '/etc/ppp_firmware/vr9-B-dsl.bin'

config interface 'lan'
        option type 'bridge'
        option ifname 'eth0.1'
        option proto 'static'
        option ipaddr '172.12.0.1'
        option netmask '255.255.255.0'
        option dns '8.8.8.8 208.67.222.222'
        option igmp_snooping '1'

config device 'lan_dev'
        option name 'eth0.1'
        option macaddr '33:AA:ae:AA:15:ea'

config interface 'wan'
        option proto 'pppoe'
        option delegate '0'
        option ifname 'ptm0.101'
        option username 'bthomehub@btbroadband.com'
        option password ' '

config device 'wan_dev'
        option name 'ptm0'
        option macaddr '33:AA:ae:AA:15:eb'
     
config interface 'iptv'
        option proto 'static'
        option ipaddr '10.22.22.1'
        option netmask '255.255.255.0'
        option _orig_ifname 'pm0.101'
        option _orig_bridge 'false'
        option ifname 'ptm0.101'

# /etc/config/firewall

config zone
        option name             wan
        list   network          'wan'
        list   network          'iptv'
        option input            REJECT
        option output           ACCEPT
        option forward          REJECT
        option masq             1
        option mtu_fix          1

config rule
        option name 'IGMP'
        option src 'wan'
        option proto 'igmp'
        option target 'ACCEPT'

config rule
        option name 'config rul Multicast'
        option src 'wan'
        option dest 'lan'
        option dest_ip '224.0.0.0/4'
        option proto 'udp'
        option family 'ipv4'
        option target 'ACCEPT'

# /etc/config/igmpproxy

config igmpproxy
        option quickleave 1

config phyint
        option network iptv
        option direction upstream
        list altnet 0.0.0.0/0           # allow everything
#       list altnet 109.159.247.0/24    # BT's IPTV sources

config phyint
        option network lan
        option direction downstream

Bonanza, if you have Infinity broadband, the vr9-B-dsl.bin fw has been extracted from the FRITZ.Box_7490.113.06.93.image, is one of the latest versions for the Lantiq and comes with Vectoring enabled. Get it here.

# /etc/init.d/dsl_control status

ATU-C Vendor ID:                          Infineon 178.6
ATU-C System Vendor ID:                   45,43,49,20,74,65,6C,65
Chipset:                                  Lantiq-VRX200 Unknown
Firmware Version:                         5.9.0.12.1.7
API Version:                              4.17.18.6
XTSE Capabilities:                        0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x2
Annex:                                    B
Line Mode:                                G.993.2 (VDSL2)
Profile:                                  17a
Line State:                               UP [0x801: showtime_tc_sync]
Forward Error Correction Seconds (FECS):  Near: 179 / Far: 11486
Errored seconds (ES):                     Near: 0 / Far: 83
Severely Errored Seconds (SES):           Near: 0 / Far: 0
Loss of Signal Seconds (LOSS):            Near: 0 / Far: 539
Unavailable Seconds (UAS):                Near: 38 / Far: 38
Header Error Code Errors (HEC):           Near: 0 / Far: 0
Non Pre-emtive CRC errors (CRC_P):        Near: 0 / Far: 0
Pre-emtive CRC errors (CRCP_P):           Near: 0 / Far: 0
Power Management Mode:                    L0 - Synchronized
Latency / Interleave Delay:               Down: Interleave (8.0 ms) / Up: Interleave (5.0 ms)
Data Rate:                                Down: 55.000 Mb/s / Up: 9.999 Mb/s
Line Attenuation (LATN):                  Down: 8.7dB / Up: 6.3dB
Signal Attenuation (SATN):                Down: 8.7dB / Up: 6.2dB
Noise Margin (SNR):                       Down: 13.2dB / Up: 16.0dB
Aggregate Transmit Power (ACTATP):        Down: -4.1dB / Up: -4.0dB
Max. Attainable Data Rate (ATTNDR):       Down: 79.642 Mb/s / Up: 26.191 Mb/s
Line Uptime Seconds:                      39148
Line Uptime:                              10h 52m 28s

:sunglasses:

This topic was automatically closed 6 days after the last reply. New replies are no longer allowed.