Unable to connect to ISP (PPPoE)

I recently connected my newly purchased GL-MT6000 router, which is running OpenWRT firmware version 4.6.2. I am using the first WAN interface for PPPoE (default configuration), but it continuously shows a "connecting" status and then indicates that the cable is disconnected. It appears that the interface shuts down, and then it goes back to "connecting" status repeatedly. No VLAN ID is required by my ISP.

Upon investigating through SSH and using the logread command, I observed the following log entries:

Mon Sep  2 18:11:44 2024 daemon.err insmod: module is already loaded - ppp_generic
Mon Sep  2 18:11:44 2024 daemon.err insmod: module is already loaded - pppox
Mon Sep  2 18:11:44 2024 daemon.err insmod: module is already loaded - pppoe
Mon Sep  2 18:11:44 2024 daemon.info pppd[32266]: Plugin rp-pppoe.so loaded.
Mon Sep  2 18:11:44 2024 daemon.info pppd[32266]: RP-PPPoE plugin version 3.8p compiled against pppd 2.4.8
Mon Sep  2 18:11:44 2024 daemon.notice pppd[32266]: pppd 2.4.8 started by root, uid 0
Mon Sep  2 18:11:59 2024 daemon.warn pppd[32266]: Timeout waiting for PADO packets
Mon Sep  2 18:11:59 2024 daemon.err pppd[32266]: Unable to complete PPPoE Discovery
Mon Sep  2 18:11:59 2024 daemon.info pppd[32266]: Exit.

Any suggestions or directions for investigation?

p.s. I do not know how to export configuration for community members to review.

BR,

What ISP do you use? What modem do you use if you are using xDSL?

The infrastructure and ISP are Bezeq, and the modem in use is a GoFiber GF25C (GPON) with factory default settings.

Are you sure you need PPPoE and do you entered the correct credentials if you need?
Are there any additional information provided by Bezeq?

Yes, I am certain that I am supposed to use PPPoE, as this has been the configuration I used for years with Bezeq (as confirmed by Bezeq). We also reset my ISP credentials and reconfigured the WAN interface - no change.

Additionally, they confirmed that the GPON is running the correct ISP-approved hardware and firmware. Apparently, I am the first customer to report this issue.

Do they lock their PPPoE to known routers, maybe?
Some ISPs do this to prevent custom devices. Sometimes there is a "cool down" phase then before a new PPPoE device may connect.

I conducted some sanity checks using another GPON model (ZTE F601) that is also approved by the ISP. The router connected almost instantly to the ISP.

Prior to this testing, I allowed my router to attempt reconnection for about an hour without success (using the GoFiber). It does not appear to be a cooldown issue, as reactivating the S/N of the ZTE F601 and attaching it to my Bezeq account connected to the ISP immediately.

Since both GPONs are ISP-approved and tested, my next step is to investigate the router. However, I acknowledge that the results of the initial checks suggest the GoFiber GPON may be the primary issue.

You could try to clone the MAC of the working router, just to check if this might be an issue.

Are you referring to copying the MAC address of the ZTE GPON and replacing it with the MAC address of the GoFiber, or are you asking about my old Asus router, which I have now replaced? The Asus router also experienced the same PADO issue with the GoFiber.

Ah, wait. You changed your GPON as well and now it does not work anymore?
This does not sound like an router issue then?

As mentioned earlier, I am the first person to report issues with the approved GoFiber GPON. Despite receiving a replacement GoFiber GPON, the router still fails to function with it.

Did any device work with the GoFiber GPON so far?
If yes: Copy this MAC address and set it on the GL router.

Testing has only been conducted with two routers so far. As the ISP has refused to investigate the issue, citing that it involves private equipment, if there are no further avenues for investigation or debugging on the router side, I would recommend avoiding undocumented GPONs and suggest closing this thread.

Even if it is approved by the ISP.

Well, ISPs are ... not your friend ... mostly :wink: