help with OpenWRT on HubOne

AOR1 · ‎25-04-2025

.@MisterW logread | grep pppd gives nothing

MisterW · ‎30-07-2007

(I didn't look via ssh as I don't know where the logs are stored/ what file to look for)

You dont need to know where the logs are stored, just run 'logread'

The only thing I can see that's definitely wrong with your config is that ipv6 shouldnt be enabled (Plusnet dont currently support ipv6) but I wouldnt think that is the cause of the problem

Change

option ipv6 '1' to option ipv6 '0'

Does the dsl0 interface come up ? i.e synchronise

Superusers are not staff, but they do have a direct line of communication into the business in order to raise issues, concerns and feedback from the community.

MisterW · ‎30-07-2007

@AOR1 logread | grep pppd gives nothing

That means that its not even trying to setup the pppoe connection.

It wont attempt it until the dsl link is up , is the dsl link synching ? ( I've no idea how you check that though )

This is the sort of log you'd expect for a successful pppoe setup

Tue Mar 10 10:20:44 2026 daemon.info pppd[7308]: Plugin pppoe.so loaded.
Tue Mar 10 10:20:44 2026 daemon.info pppd[7308]: PPPoE plugin from pppd 2.5.2
Tue Mar 10 10:20:44 2026 daemon.notice pppd[7308]: pppd 2.5.2 started by root, uid 0
Tue Mar 10 10:20:44 2026 daemon.info pppd[7308]: PPP session is 6745
Tue Mar 10 10:20:44 2026 daemon.warn pppd[7308]: Connected to F8:13:08:41:6F:D2 via interface eth1
Tue Mar 10 10:20:44 2026 daemon.info pppd[7308]: Using interface pppoe-wan
Tue Mar 10 10:20:44 2026 daemon.notice pppd[7308]: Connect: pppoe-wan <--> eth1
Tue Mar 10 10:20:44 2026 daemon.info pppd[7308]: CHAP authentication succeeded
Tue Mar 10 10:20:44 2026 daemon.notice pppd[7308]: CHAP authentication succeeded
Tue Mar 10 10:20:44 2026 daemon.notice pppd[7308]: peer from calling number xxxxxx authorized
Tue Mar 10 10:20:44 2026 daemon.notice pppd[7308]: local IP address xxx.xxx.xxx.xxx
Tue Mar 10 10:20:44 2026 daemon.notice pppd[7308]: remote IP address 195.166.130.251
Tue Mar 10 10:20:44 2026 daemon.notice pppd[7308]: primary DNS address 212.159.13.49
Tue Mar 10 10:20:44 2026 daemon.notice pppd[7308]: secondary DNS address 212.159.6.9

albeit in your case I would expect this line

Tue Mar 10 10:20:44 2026 daemon.notice pppd[7308]: Connect: pppoe-wan <--> eth1

to show

Tue Mar 10 10:20:44 2026 daemon.notice pppd[7308]: Connect: pppoe-wan <--> dsl0

Superusers are not staff, but they do have a direct line of communication into the business in order to raise issues, concerns and feedback from the community.

AOR1 · ‎25-04-2025

.@MisterW In reply to "Does the dsl0 interface come up ? i.e synchronise" - the interface is there but it has error message 'Network device is not present'. Occasionally the error message is 'connection attempt failed' but I can't work out how to get this reproducibly. I've attached a screenshot so it's clear what I mean.

As for the change you suggested to the /etc/config/network file - I haven't done that yet as I need to work out how to do this, maybe with vi. Sorry I'm not much of a Linux user.

MisterW · ‎30-07-2007

@AOR1

Does the dsl0 interface come up ? i.e synchronise" - the interface is there but it has error message 'Network device is not present'

That's the WAN interface and its basically saying that the dsl0 device isnt available. I had sort of expected to see a dsl0 interface on that screen but (as I said) I've never used Openwrt in a DSL situation.

Does the dsl0 interface come up ? i.e synchronise" - the interface is there but it has error message 'Network device is not present'

You dont need to edit the file , you can change it from LUCI. Edit the WAN interface, goto Advanced settings and change 'Obtain IPV6 address' from Manual to Disabled.

Just a thought, does 'logread | grep dsl0' show anything ?

Superusers are not staff, but they do have a direct line of communication into the business in order to raise issues, concerns and feedback from the community.

MisterW · ‎30-07-2007

@AOR1 just had a quick search...

try connecting via SSH and running the command /etc/init.d/dsl_control status post the output

Superusers are not staff, but they do have a direct line of communication into the business in order to raise issues, concerns and feedback from the community.

AOR1 · ‎25-04-2025

.@MisterW

Thanks I changed the 'Obtain IPv6 address' setting.

'logread | grep dsl0' gives zero output

'/etc/init.d/dsl_control' gives me '-ash: dsl_control not found'. There IS a file called dsl_control in that directory. I tried going to the directory and running it with 'dsl_control' and '.dsl_control'. Neither work. I'm sure there's something obvious I should be doing to get it to run... sorry about my level of command-line skills

MisterW · ‎30-07-2007

@AOR1

I'll fire up my Openwrt Hub 1 and have a look see around the dsl interface...

Superusers are not staff, but they do have a direct line of communication into the business in order to raise issues, concerns and feedback from the community.

MisterW · ‎30-07-2007

@AOR1 ok so I fired up my Hub 1 and it definitely has a dsl_status command, see below

root@OpenWrt:~# /etc/init.d/dsl_control
Syntax: /etc/init.d/dsl_control [command]

Available commands:
start Start the service
stop Stop the service
restart Restart the service
reload Reload configuration files (or restart if service does not implement reload)
enable Enable service autostart
disable Disable service autostart
enabled Check if service is started on boot
dslstat Get DSL status information
running Check if service is running
status Service status
trace Start with syscall trace
info Dump procd service info

tried 'status' and it reported

root@OpenWrt:~# /etc/init.d/dsl_control status
Inactive

now this may be because my config doesnt have a WAN interface which uses it.

Anyway I had a look at the dsl tab in LUCI and noticed there was nothing in the firmware file box

So I looked where the firmware was and added the file

then ran start & status again, this time it reported running

root@OpenWrt:~# /etc/init.d/dsl_control start
root@OpenWrt:~# /etc/init.d/dsl_control status
running

then tried dslstat and got

root@OpenWrt:~# /etc/init.d/dsl_control dslstat
{
"api_version": "4.17.18.6",
"firmware_version": "5.8.1.8.1.6",
"chipset": "Lantiq-VRX200",
"driver_version": "1.5.17.6",
"state": "Silent",
"state_num": 3,
"up": false,
"uptime": 0,
"atu_c": {

},
"power_state": "L3 - No power",
"power_state_num": 3,
"upstream": {

},
"downstream": {

},
"olr": {
"downstream": {
"bitswap": {
"requested": 0,
"executed": 0,
"rejected": 0,
"timeout": 0
},
"sra": {
"requested": 0,
"executed": 0,
"rejected": 0,
"timeout": 0
},
"sos": {
"requested": 0,
"executed": 0,
"rejected": 0,
"timeout": 0
}
},
"upstream": {
"bitswap": {
"requested": 0,
"executed": 0,
"rejected": 0,
"timeout": 0
},
"sra": {
"requested": 0,
"executed": 0,
"rejected": 0,
"timeout": 0
},
"sos": {
"requested": 0,
"executed": 0,
"rejected": 0,
"timeout": 0
}
}
},
"errors": {
"near": {
"es": 0,
"ses": 0,
"loss": 0,
"uas": 15,
"lofs": 0,
"fecs": 0,
"cv_c": 0,
"fec_c": 0,
"hec": 0,
"ibe": 0,
"crc_p": 0,
"crcp_p": 0,
"cv_p": 0,
"cvp_p": 0
},
"far": {
"es": 0,
"ses": 0,
"loss": 0,
"uas": 13,
"lofs": 0,
"fecs": 0,
"cv_c": 0,
"fec_c": 0,
"hec": 0,
"ibe": 0,
"crc_p": 0,
"crcp_p": 0,
"cv_p": 0,
"cvp_p": 0
}
}
}

which makes sense since I've got no dsl connection

does your dsl_control file start with ?

what version of Openwrt do you have ?

Superusers are not staff, but they do have a direct line of communication into the business in order to raise issues, concerns and feedback from the community.

AOR1 · ‎25-04-2025

.@MisterW

OpenWRT version 24.10.6

root@OpenWrt:/etc/init.d# cat dsl_control
#!/bin/sh /etc/rc.common
# Copyright (C) 2012 OpenWrt.org

I added the firmware file entry to the DSL menu and /etc/init.d/dsl_control is now working 🙂
The only difference I see between your output and mine is in the following fields:
"firmware_version"
"errors" "near" "uas"
"errors" "far" "uas"

root@OpenWrt:~# /etc/init.d/dsl_control status
running
root@OpenWrt:~# /etc/init.d/dsl_control dslstat
{
"api_version": "4.17.18.6",
"firmware_version": "5.8.0.11.1.1",
"chipset": "Lantiq-VRX200",
"driver_version": "1.5.17.6",
"state": "Silent",
"state_num": 3,
"up": false,
"uptime": 0,
"atu_c": {

},
"power_state": "L3 - No power",
"power_state_num": 3,
"upstream": {

},
"downstream": {

},
"olr": {
"downstream": {
"bitswap": {
"requested": 0,
"executed": 0,
"rejected": 0,
"timeout": 0
},
"sra": {
"requested": 0,
"executed": 0,
"rejected": 0,
"timeout": 0
},
"sos": {
"requested": 0,
"executed": 0,
"rejected": 0,
"timeout": 0
}
},
"upstream": {
"bitswap": {
"requested": 0,
"executed": 0,
"rejected": 0,
"timeout": 0
},
"sra": {
"requested": 0,
"executed": 0,
"rejected": 0,
"timeout": 0
},
"sos": {
"requested": 0,
"executed": 0,
"rejected": 0,
"timeout": 0
}
}
},
"errors": {
"near": {
"es": 0,
"ses": 0,
"loss": 0,
"uas": 210,
"lofs": 0,
"fecs": 0,
"cv_c": 0,
"fec_c": 0,
"hec": 0,
"ibe": 0,
"crc_p": 0,
"crcp_p": 0,
"cv_p": 0,
"cvp_p": 0
},
"far": {
"es": 0,
"ses": 0,
"loss": 0,
"uas": 207,
"lofs": 0,
"fecs": 0,
"cv_c": 0,
"fec_c": 0,
"hec": 0,
"ibe": 0,
"crc_p": 0,
"crcp_p": 0,
"cv_p": 0,
"cvp_p": 0,
"rx_corrupted": 0,
"rx_uncorrected_protected": 0,
"rx_retransmitted": 0,
"rx_corrected": 0,
"tx_retransmitted": 0
}
}
}
root@OpenWrt:~#

MisterW · ‎30-07-2007

@AOR1

this is the crunch now then

"up": false,
"uptime": 0,

I'm assuming that means the DSL link isnt up (synched)

Superusers are not staff, but they do have a direct line of communication into the business in order to raise issues, concerns and feedback from the community.

MisterW · ‎30-07-2007

@AOR1

did you get any further with this ?

Superusers are not staff, but they do have a direct line of communication into the business in order to raise issues, concerns and feedback from the community.

AOR1 · ‎25-04-2025

.@MisterW

No, no progress.

I'm wondering if it would ever work or if it is faulty. Thinking of returning the item to ebay

MisterW · ‎30-07-2007

@AOR1 sorry I cant help any further, I've just got no way of testing mine on an ADSL connection.

Have you tried posting on the Openwrt forum https://forum.openwrt.org/latest ?

Superusers are not staff, but they do have a direct line of communication into the business in order to raise issues, concerns and feedback from the community.

AOR1 · ‎25-04-2025

.@MisterW Thanks for all your help anyway. I'll look at the Openwrt forum next as you advise

help with OpenWRT on HubOne

Re: help with OpenWRT on HubOne

Re: help with OpenWRT on HubOne

Re: help with OpenWRT on HubOne

Re: help with OpenWRT on HubOne

Re: help with OpenWRT on HubOne

Re: help with OpenWRT on HubOne

Re: help with OpenWRT on HubOne

Re: help with OpenWRT on HubOne

Re: help with OpenWRT on HubOne

Re: help with OpenWRT on HubOne

Re: help with OpenWRT on HubOne

Re: help with OpenWRT on HubOne

Re: help with OpenWRT on HubOne

Re: help with OpenWRT on HubOne

Re: help with OpenWRT on HubOne