SKY setup on BTHH5 with lede help

Hi Guys,

wondering if I can get some pointers please.

I have a BTHH5 with the latest snapshot of lede 17.01.4 installed

I have tried different configurations, however I am unable get the DSL link to change the status "UP".

is there a network configuration that I am missing ? I have looked at a few forums & tried all the settings suggested without any luck.

Any help will be very much appreciated.

Thanks

Did you look into the instructions posted in the https://openwrt.ebilan.co.uk/viewtopic.php?f=7&t=266&sid=8b74291085644fbc31e050e168ce8bde thread?

Thanks Moellero.

I have yes, tried different things mentioned on it.

I can connect the HH5, if I piggy back it to the SR102 - so telephone line to SR102 - Ethernet out - Ethernet in to the red WAN on HH5. and it works perfectly.

I am trying to get the hub working with the telephone line directly connected to the HH5, this is where I cannot get the DSL line to get me a status "UP".

Have you read the Bill's manual yet? Look at pages 34-35 and then follow the relevant section depending on whether you have ADSL or VDSL contract.

Thanks Savostyanov,
That is the guide I have followed, without any luck

Well, could you post the result of:
cat /etc/config.network
(redact any unique usernames and passwords) as well as the output of:

/etc/init.d/dsl_control status

If I understand correctly you must be on an old ADSL-line...

1 Like

Regardless of the protocol, I would have thought the HH5a should show DSL Status as being 'UP' if the basic line parameters (Annex, Tone, VLAN, VPI/VCI, mux etc) are correctly configured for ADSL or VDSL.

1 Like

Thanks for the input guys.

Sorry, i should have mentioned - i am on Sky Fibre, that would be VDSL ?
If only i could get the DSL status UP, which isnt happening for me.

Here is the network & dsl status

config interface 'loopback'
        option ifname 'lo'
        option proto 'static'
        option ipaddr '127.0.0.1'
        option netmask '255.0.0.0'

config globals 'globals'
        option ula_prefix 'fd05:5ff2:47dc::/48'

config atm-bridge 'atm'
        option encaps 'llc'
        option payload 'bridged'
        option nameprefix 'dsl'
        option vci '38'
        option vpi '0'

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

config interface 'lan'
        option type 'bridge'
        option ifname 'eth0.1'
        option proto 'static'
        option ipaddr '192.168.1.1'
        option netmask '255.255.255.0'
        option ip6assign '60'

config device 'lan_dev'
        option name 'eth0.1'
        option macaddr 'c8:91:f9:05:cd:8a'

config interface 'wan'
        option proto 'dhcp'
        option ipv6 '1'
        option ifname 'dsl0.101'
        option macaddr '90:21:06:B9:E0:B4'
        option mtu '1500'

config device 'wan_dev'
        option name 'dsl0'
        option macaddr 'c8:91:f9:05:cd:8b'

config interface 'wan6'
        option ifname '@wan'
        option proto 'dhcpv6'

config switch
        option name 'switch0'
        option reset '1'
        option enable_vlan '1'

config switch_vlan
        option device 'switch0'
        option vlan '1'
        option ports '0 1 2 4 6t'

config switch_vlan
        option device 'switch0'
        option vlan '2'
        option ports '5 6t'


root@OpenWrt:~# /etc/init.d/dsl_control status
ATU-C Vendor ID:
ATU-C System Vendor ID:
Chipset:                                  Lantiq-VRX200
Firmware Version:                         5.7.9.9.0.6
API Version:                              4.17.18.6
XTSE Capabilities:                        , , , , , , ,
Annex:
Line Mode:
Profile:
Line State:                               DOWN [0x200: silent]
Forward Error Correction Seconds (FECS):  Near: 0 / Far: 0
Errored seconds (ES):                     Near: 0 / Far: 0
Severely Errored Seconds (SES):           Near: 0 / Far: 0
Loss of Signal Seconds (LOSS):            Near: 0 / Far: 0
Unavailable Seconds (UAS):                Near: 105 / Far: 104
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:                    L3 - No power
Latency [Interleave Delay]:               0.0 ms [Fast]   0.0 ms [Fast]
Data Rate:                                Down: 0 b/s / Up: 0 b/s
Line Attenuation (LATN):                  Down: 0.0 dB / Up: 0.0 dB
Signal Attenuation (SATN):                Down: 0.0 dB / Up: 0.0 dB
Noise Margin (SNR):                       Down: 0.0 dB / Up: 0.0 dB
Aggregate Transmit Power (ACTATP):        Down: 0.0 dB / Up: 0.0 dB
Max. Attainable Data Rate (ATTNDR):       Down: 0 b/s / Up: 0 b/s
Line Uptime Seconds:                      0
Line Uptime:                              down

If you are using LEDE 17.01.4, you should be using vlan 'ptm0.101', not 'dsl0.101', which is only applicable to snapshots from Oct 2017 onwards. (see section 7.17 of the guide)

Client ID and vendor class also appears to be missing. See section 7.5 of the install guide for Sky fibre specific info, which also refers to this link
OpenWRT on Sky fibre MER

2 Likes

Thanks Bill,

I am using the latest snapshot, thats why used dsl0.

I will try again using the Client ID & Vendor Id and see if does work.

Also the following two entries look interesting:

and

These IIRC are also not applicable to the 17.01.4 stable release, at least I do not see these in my otherwise pretty stock configuration for 17.01.4.

Perhaps, you could try to connect with stable LEDE 17.01.4 first before trying to do the same on snapshots? Sky config is not a simple one, so it may be worth taking baby steps.

Thanks Savostyanov.
I was on stable 17.01.4 since its release, and never been able to get the DSL up then. Thats why upgraded to the snapshots hoping it would trigger something that might be missing.

I tried downgrading, however the snapshot would not allow me to.

even tried the sysupgrade -f , but no joy with that too.