Problem Description
My new GL-A1300 router is unable to establish an internet connection. The system log consistently shows that the PPPoE discovery process fails with the error: Timeout waiting for PADO packets .
This issue is specific to the GL-A1300. I have an older GL-XE300 router that connects to the exact same internet line, using the exact same cables and PPPoE settings (username, password, VLAN 200), and it works perfectly.
Environment:
ISP Connection Type: PPPoE
Required VLAN ID: 200
ONT: Genexis Fibertwist P2411
Key Finding & Analysis
The critical difference between the two routers is the WAN port link speed:
- The GL-A1300 (failing) negotiates a 1Gbps link, but the PPPoE handshake never completes.
- The GL-XE300 (working) negotiates a 100Mbps link, and the PPPoE connection is established successfully.
This strongly suggests there is a hardware-level incompatibility or a firmware/driver bug on the GL-A1300 that prevents it from correctly handling PPPoE discovery packets over a tagged VLAN when the link speed is 1Gbps.
Troubleshooting Steps Performed
I have performed extensive troubleshooting to isolate the issue:
- Updated Firmware: The GL-A1300 is running the latest stable firmware.
- Factory Reset: I have performed multiple factory resets and configured the connection from scratch each time.
- MAC Cloning: I have cloned the MAC address from the working GL-XE300 onto the GL-A1300. The issue persists.
- Intermediate Switch: I placed a simple unmanaged gigabit switch between my ISP's modem and the GL-A1300's WAN port. This did not solve the problem.
- Forcing Link Speed: I attempted to manually force the WAN port (
eth1) to 100Mbps using theethtoolcommand via SSH. However, the router's network management daemon (netifd) overrides this setting on every connection attempt, forcing the link back to 1Gbps.
Conclusion
The problem is isolated to the GL-A1300 router. All evidence points to a bug in the firmware or network driver that affects PPPoE negotiation on a tagged VLAN at 1Gbps speeds.
Could you please investigate this issue?