I just tried to connect my new OpenWRT (BT Home Hub 5a) router to the internet, but that doesn't seem to work. In the system log i always find the error message "Timeout waiting for PADO packets". I just tried to set the wan interface to PPPoE and inserted my username/password, but that doesn't do the trick. I'm from germany and my provider is O2.
Does anyone have expierience with it or know how I can configure that router corretly?
System log:
kern.warn kernel: [ 3223.704641] enter showtime
daemon.notice netifd: Network device 'dsl0' link is up
daemon.notice netifd: Interface 'wan' has link connectivity
daemon.notice netifd: Interface 'wan' is setting up now
kern.warn kernel: [ 3223.711695] enter showtime
daemon.err insmod: module is already loaded - slhc
daemon.err insmod: module is already loaded - ppp_generic
daemon.err insmod: module is already loaded - pppox
daemon.err insmod: module is already loaded - pppoe
daemon.info pppd[10377]: Plugin rp-pppoe.so loaded.
daemon.info pppd[10377]: RP-PPPoE plugin version 3.8p compiled against pppd 2.4.7
daemon.notice pppd[10377]: pppd 2.4.7 started by root, uid 0
kern.warn kernel: [ 3239.061282] leave showtime
daemon.notice netifd: Network device 'dsl0' link is down
daemon.notice netifd: Interface 'wan' has link connectivity loss
daemon.warn pppd[10377]: Timeout waiting for PADO packets
daemon.err pppd[10377]: Unable to complete PPPoE Discovery
daemon.info pppd[10377]: Exit.
daemon.err dnsmasq[1940]: failed to send packet: Permission denied
daemon.err dnsmasq[1940]: failed to send packet: Permission denied
General Information (shown on "overview"):
Model: BT Home Hub 5A
Architecture: xRX200 rev 1.2
DSL Status
Line State: UP [0x0]
Line Mode: G.993.2 (VDSL2)
Line Uptime: 16m 23s
Annex: B
Profile: 17a
Data Rate: 20.205 Mb/s / 1.643 Mb/s
Max. Attainable Data Rate (ATTNDR): 21.703 Mb/s / 1.732 Mb/s
Latency: 0.14 ms / 10.0 ms
Line Attenuation (LATN): 5.2 dB / 2.2 dB
Signal Attenuation (SATN): 5.2 dB / 2.2 dB
Noise Margin (SNR): 6.0 dB / 10.7 dB
Aggregate Transmit Power(ACTATP): 12.8 dB / 14.2 dB
Forward Error Correction Seconds (FECS): 0 / 0
Errored seconds (ES): 0 / 3
Severely Errored Seconds (SES): 0 / 0
Loss of Signal Seconds (LOSS): 0 / 0
Unavailable Seconds (UAS): 163 / 163
Header Error Code Errors (HEC): 0 / 0
Non Pre-emtive CRC errors (CRC_P): 0 / 0
Pre-emtive CRC errors (CRCP_P): 0 / 0
ATU-C System Vendor ID: Broadcom 193.218
Power Management Mode: L0 - Synchronized
thanks, maybe that will do it. I will definetly try it.
But one more question, where to set dsl0.7? I don't see it on the GUI, so i guess directly on the config file rigt?.... thanks in advance (^^)
Thank you so much moeller0, bill888 and slh. I managed to get a connection am I cam pretty happy with it!
Still things aren't perfect, I booked a 50 Mbit contract, but as you can see the Home Hub only detects a ~20 MBit rate. I know this is the fallback if something goes wrong, but the guy who measured the line said he measured 100 Mbit (guess the 17a profile). Any ideas how to correct that too?
That could be the so called vectoring fallback profile which is used if the DSLAM believes the modem is not vectoring capable. This restricts the use to the first 2.2 MHz that are typically exempted from vectoring, so that the ISP does not need to replace all old ADSL1/2/2+ equipment in the field. Could you copy and paste the DSLs report from the GUI?
Added:
If you run /etc/init.d/dsl_control status on the router, what is the output for "Line Mode:'
I see G.993.5 (VDSL2 with down- and upstream vectoring), but only since I installed a vectoring capable firmware (in my case from the fritzbox 7490 firtzos 7.12, but that is not terribly stable). I believe in the fall back profile the "vectoring' references should be missing...
Here is my full output as for reference
root@BTHH5A:~# /etc/init.d/dsl_control status
ATU-C Vendor ID: Broadcom 193.218
ATU-C System Vendor ID: Broadcom
Chipset: Lantiq-VRX200
Firmware Version: 5.9.1.4.0.7
API Version: 4.17.18.6
XTSE Capabilities: 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x0, 0x2
Annex: B
Line Mode: G.993.5 (VDSL2 with down- and upstream vectoring)
Profile: 17a
Line State: UP [0x801: showtime_tc_sync]
Forward Error Correction Seconds (FECS): Near: 0 / Far: 153
Errored seconds (ES): Near: 1041 / Far: 10988
Severely Errored Seconds (SES): Near: 242 / Far: 2325
Loss of Signal Seconds (LOSS): Near: 6 / Far: 0
Unavailable Seconds (UAS): Near: 1390 / Far: 1390
Header Error Code Errors (HEC): Near: 0 / Far: 0
Non Pre-emtive CRC errors (CRC_P): Near: 49 / Far: 0
Pre-emtive CRC errors (CRCP_P): Near: 0 / Far: 0
Power Management Mode: L0 - Synchronized
Latency [Interleave Delay]: 0.15 ms [Fast] 0.0 ms [Fast]
Data Rate: Down: 109.981 Mb/s / Up: 36.995 Mb/s
Line Attenuation (LATN): Down: 11.5 dB / Up: 9.4 dB
Signal Attenuation (SATN): Down: 11.5 dB / Up: 9.3 dB
Noise Margin (SNR): Down: 13.1 dB / Up: 10.6 dB
Aggregate Transmit Power (ACTATP): Down: 0.3 dB / Up: 14.5 dB
Max. Attainable Data Rate (ATTNDR): Down: 135.364 Mb/s / Up: 38.885 Mb/s
Line Uptime Seconds: 27981
Line Uptime: 7h 46m 21s
root@BTHH5A:~#
These two are strong indicators for @bill888's hypothesis. With luck all you need is a vectoring capable firmware blob for the dsl part of your router (if you are unlucky, you might also need to get a line reset, but I would try the vectoring capable firmware first)
Note you could use/have used https://github.com/moeller0/lantiq_dsl_parser to look at the bitloading per frequency bin, and with the fall-back profile you would only see bitloading up to bin 512 (IIRC) with the higher frequencies not carrying any bits.