PPoE does not reconnect automatically after VDSL retraining
Hi,
As the subject tells my dsl line gets retrained sometimes but after initializing a dsl connection, ppoe connection does not come up, and i need to reboot or manually retrain dsl connection to ppoe to work.
- Copy Link
- Subscribe
- Bookmark
- Report Inappropriate Content
Hi, thanks for posting question here. Does "DSL line gets retrained" mean your internet service provider rebooted the DSL line? Does it happen frequently?
- Copy Link
- Report Inappropriate Content
@Marvin_S most of the time because of crc errors ( i think its because of noises on my line). After initializing vdsl connection , ppoe connection does not automatically come up specially when dsl gets retraind in short time , ppoe stays in last ip address and does not get reconnected with new ip( dynamic ip). PPoE led stays up but dsl led is blinking this makes it stay on last ip address. Plus that sometimes in router's log i get pado packets with no padi response.
- Copy Link
- Report Inappropriate Content
Hi, thanks for your update.
If you reboot the Archer VR400 or unplug/replug DSL line, can PPPoE reconnect automatically?
As you mentioned "PPPoE led stays up but dsl led is blinking", do you mean the DSL LED keeps flashing after dsl in short time gets retrained ? If DSL LED is still flashing, which means the retraining did not finish yet, causing PPPoE failed to reconnect. And if the DSL led is still flashing, it is suggested to contact your ISP to confirm whether there is noise on the line and fix it.
- Copy Link
- Report Inappropriate Content
@Marvin_S hi agian marvin, i saw this on td-w9960 support page under firmware updates:
TD-W9960(EU)_V1.20_230705
Download
Published Date: 2024-03-19
Language: English
File Size: 8.27 MB
Improvements and Bug Fixes:
1. Fixed some security vulnerability.
2. Fixed the issue that PPPoE dial-up could not be reestablished in some cases.
I think my problem should be something like the second improvement "2.fixed the issue that PPPoE dial-up could not be re-established in some cases."
I want to ask you if you can report this to your software engineer to look at it and maybe release a firmware update for vr400 v3 eu version.
- Copy Link
- Report Inappropriate Content
Hi, thanks for you update.
As your firmware has been the latest, and we did not receive same feedback like your situation, it is suggested to answer my last reply. Then our senior support will take further analysis for your case. Thanks for your understanding.
- Copy Link
- Report Inappropriate Content
@Marvin_S "If you reboot the Archer VR400 or unplug/replug DSL line, can PPPoE reconnect automatically?"
Yes, PPPoE can reconnect automatically.
"As you mentioned "PPPoE led stays up but dsl led is blinking", do you mean the DSL LED keeps flashing after dsl in short time gets retrained ? If DSL LED is still flashing, which means the retraining did not finish yet, causing PPPoE failed to reconnect."
Dsl flashes about 20 seconds and cones back online but no automatic PPPoE reconnection takes place as it should cause of padi timeout messages.
- Copy Link
- Report Inappropriate Content
2024-06-17 00:34:37 [5] Httpd: Clear log.
2024-06-17 00:34:52 [3] PPP: ppp0 Timeout waiting for PADO packets
2024-06-17 00:34:52 [3] PPP: ppp0
2024-06-17 00:35:01 [5] System: DSL Link Down
2024-06-17 00:35:09 [5] System: DSL Training
2024-06-17 00:35:14 [5] System: DSL Link Down
2024-06-17 00:35:17 [5] System: DSL Training
2024-06-17 00:35:36 [5] System: DSL Link Up us/ds 19998/49996 kbps Type 64/65B PTM Annex B
2024-06-17 01:28:37 [5] DHCPD: Send OFFER with ip 192.168.0.100
2024-06-17 01:28:42 [5] DHCPD: Send OFFER with ip 192.168.0.100
2024-06-17 01:28:43 [5] DHCPD: Send ACK to 192.168.0.100
2024-06-17 01:53:38 [5] DHCPD: Send OFFER with ip 192.168.0.100
2024-06-17 01:53:38 [5] DHCPD: Send ACK to 192.168.0.100
2024-06-17 02:22:51 [5] DHCPD: Send OFFER with ip 192.168.0.100
2024-06-17 02:22:52 [5] DHCPD: Send ACK to 192.168.0.100
2024-06-17 04:52:16 [5] DHCPD: Send OFFER with ip 192.168.0.100
2024-06-17 04:52:16 [5] DHCPD: Send ACK to 192.168.0.100
2024-06-17 06:58:56 [5] System: DSL Link Down
2024-06-17 06:58:59 [5] System: DSL Training
2024-06-17 06:59:18 [5] System: DSL Link Up us/ds 19998/39977 kbps Type 64/65B PTM Annex B
2024-06-17 07:09:51 [5] System: DSL Link Down
2024-06-17 07:09:55 [5] System: DSL Training
2024-06-17 07:10:14 [5] System: DSL Link Up us/ds 19998/49991 kbps Type 64/65B PTM Annex B
2024-06-17 07:10:44 [3] PPP: ppp0 User request
2024-06-17 07:10:44 [3] PPP: ppp0 LCP down
2024-06-17 07:10:44 [4] PPP: ppp0 LCP down
2024-06-17 07:10:50 [3] PPP: ppp0 User request
2024-06-17 07:10:50 [3] PPP: ppp0
2024-06-17 07:11:48 [3] PPP: ppp0 Timeout waiting for PADO packets
2024-06-17 07:11:48 [3] PPP: ppp0
2024-06-17 07:12:43 [3] PPP: ppp0 Timeout waiting for PADO packets
2024-06-17 07:12:43 [3] PPP: ppp0
2024-06-17 07:13:37 [3] PPP: ppp0 Timeout waiting for PADO packets
2024-06-17 07:13:37 [3] PPP: ppp0
2024-06-17 07:14:32 [3] PPP: ppp0 Timeout waiting for PADO packets
2024-06-17 07:14:32 [3] PPP: ppp0
2024-06-17 07:15:18 [3] PPP: ppp0
2024-06-17 07:15:18 [5] System: DSL Link Down
2024-06-17 07:15:21 [5] System: DSL Training
2024-06-17 07:15:40 [5] System: DSL Link Up us/ds 19998/25008 kbps Type 64/65B PTM Annex B
2024-06-17 08:48:33 [5] System: DSL Link Down
2024-06-17 08:48:36 [5] System: DSL Training
2024-06-17 08:48:55 [5] System: DSL Link Up us/ds 19998/21232 kbps Type 64/65B PTM Annex B
2024-06-17 08:54:45 [5] System: DSL Link Down
2024-06-17 08:54:45 [3] PPP: ppp0 User request
2024-06-17 08:54:45 [3] PPP: ppp0 LCP down
2024-06-17 08:54:45 [4] PPP: ppp0 LCP down
2024-06-17 08:54:48 [5] System: DSL Training
2024-06-17 08:54:49 [3] PPP: ppp0 User request
2024-06-17 08:54:51 [3] PPP: ppp0
2024-06-17 08:55:07 [5] System: DSL Link Up us/ds 19998/17319 kbps Type 64/65B PTM Annex B
2024-06-17 10:59:31 [5] DHCPD: Send OFFER with ip 192.168.0.100
2024-06-17 10:59:32 [5] DHCPD: Send ACK to 192.168.0.100
2024-06-17 11:18:36 [5] DHCPD: Send OFFER with ip 192.168.0.100
2024-06-17 11:18:37 [5] DHCPD: Send ACK to 192.168.0.100
This is the log look out for timeout waiting for PADO packets
- Copy Link
- Report Inappropriate Content
@Marvin_S here is another log when it happens:
2024-06-17 18:59:04 [5] Httpd: Clear log.
2024-06-17 18:59:15 [3] PPP: ppp0 Timeout waiting for PADO packets
2024-06-17 18:59:15 [3] PPP: ppp0
2024-06-17 18:59:34 [6] PPP: ppp0 sent [PADI Host-Uniq(0x0000021f)]
2024-06-17 18:59:39 [6] PPP: ppp0 sent [PADI Host-Uniq(0x0000021f)]
2024-06-17 18:59:49 [6] PPP: ppp0 sent [PADI Host-Uniq(0x0000021f)]
2024-06-17 19:00:09 [3] PPP: ppp0 Timeout waiting for PADO packets
2024-06-17 19:00:09 [3] PPP: ppp0
2024-06-17 19:00:28 [6] PPP: ppp0 sent [PADI Host-Uniq(0x0000029e)]
2024-06-17 19:00:33 [6] PPP: ppp0 sent [PADI Host-Uniq(0x0000029e)]
2024-06-17 19:00:36 [6] DHCPD: Recv DISCOVER from 90:F0:52:54:22:80
2024-06-17 19:00:36 [5] DHCPD: Send OFFER with ip 192.168.0.100
2024-06-17 19:00:36 [7] DHCPD: Recv REQUEST from 90:F0:52:54:22:80
2024-06-17 19:00:36 [5] DHCPD: Send ACK to 192.168.0.100
2024-06-17 19:00:43 [6] PPP: ppp0 sent [PADI Host-Uniq(0x0000029e)]
2024-06-17 19:01:03 [3] PPP: ppp0 Timeout waiting for PADO packets
2024-06-17 19:01:03 [3] PPP: ppp0
2024-06-17 19:01:22 [6] PPP: ppp0 sent [PADI Host-Uniq(0x00000359)]
2024-06-17 19:01:27 [6] PPP: ppp0 sent [PADI Host-Uniq(0x00000359)]
2024-06-17 19:01:37 [6] PPP: ppp0 sent [PADI Host-Uniq(0x00000359)]
2024-06-17 19:01:57 [3] PPP: ppp0 Timeout waiting for PADO packets
2024-06-17 19:01:57 [3] PPP: ppp0
And this is my dsl stats:
- Copy Link
- Report Inappropriate Content
Hi, thanks for your update.
According to your reply and log, it suggested to contact your ISP to confirm there is noisy issue on the line and you may ask them to fix it.
Also,if you reboot Archer VR400 or unplug/replug DSL line, PPPoE can reconnect automatically, which means that PPPoE can reconnect normally after DSL retraining.
Thanks for your cooperation.
- Copy Link
- Report Inappropriate Content
@Marvin_S no modem can not restablish pppoe connection by itself after retraining the DSL connection.
It needs a hard reset or manual resync. Please forward this issue to someone that has a little knowledge in dsl and pppoe connection to look at it. I know what im talking about it is some sort of bug in the firmware of the modem
- Copy Link
- Report Inappropriate Content
Information
Helpful: 0
Views: 524
Replies: 10
Voters 0
No one has voted for it yet.