Devastate

You are welcome. In my specific scenario, the disconnection would still occur. Your scenario could be different. My DSL line would drop or resync, causing a brief disconnection of approximately 45 seconds. Other routers would automatically reconnect approximately 45 seconds after the disconnect, but the disconnections still occurred. The R3 no longer automatically reconnects after a factory reset if you are running a version later than 4.0.41. You could try your ISP's router, if you have one, and see if the issue persists. However, unless you are actively using time-sensitive applications, it will be harder to notice. For the workaround, you should be able to upgrade to any newer firmware if you factory reset while on v4.0.41, and then avoid any further factory resets.

It is my understanding that the disconnection isn’t caused by the R3. The issue is the failure to reconnect. I never noticed any time-based disconnects. The disconnects I did notice were when my DSL line resynced or when I restarted the modem, requiring me to restart the R3 to regain connectivity. If this bug did not exist, the source of the disconnect would likely still affect most online games, resulting in disconnections from servers. This, of course, is all if it is the same bug I experienced.

When I was experiencing the R3 WAN not reconnecting, I looked into handling PPPoE on the HG612 but saw reports of poor performance, so I opted not to bother. I did discover a workaround to remediate the bug. I have shared the solution with others, but it has proved to be a hassle. You could try daisy-chaining them together: HG612 > Replacement Router > R3.

Your issue sounds like it could be a known bug with PPPoE on the R3, where if the connection is lost, the R3 WAN stays disconnected. If this bug is what you are experiencing, then using the HG612 to handle PPPoE should be a solution.

Does 'setup' here refer to the HG612 and R3? Have you factory reset the R3, and if so, did it start occurring afterwards?

MAC address cloning can be found by navigating to Settings > WAN > Advanced > MAC Address Cloning.

Thank you; I now know that the solution does, in fact, work for others, albeit with some bypassing involved. I have suggested the solution to others in the past, but I don't think anyone has actually persevered until the end. I have promptly used the latest firmware versions, as they are released, with the solution. I am currently using firmware version 4.0.645. The only slight problem I have encountered, which may be unrelated to the solution, is that the '--' fails to load occasionally. This problem has only started to occur more recently, and it resolves itself after some time without any intervention. One last question: do the 24-hour disconnects still occur but automatically reconnect afterwards, or do they no longer occur altogether?

From my testing, my solution only works if the factory reset is on firmware version 4.0.41. Firmware version 4.0.41 was the last firmware with PPPoE working. Any factory reset after that firmware will break it again. The solution was to automatically reconnect when a disconnect occurs. I'm unsure whether it will prevent your disconnections from happening altogether.

These are the steps I just took to make PPPoE automatically reconnect. Uploaded the firmware v4.0.41. Performed a factory reset through the GUI. I was unable to reconnect to the router through LAN or Wi-Fi. Performed multiple factory resets through the pinhole in the back of the router until I was able to connect, trying different ideas such as removing the residual power. Removing all cables before factory resetting was what seemed to allow me to connect afterwards. Since I was next to the router at the time, I skipped the setup wizard through the mobile app via Wi-Fi, and everything went smoothly. Uploaded the latest firmware via LAN. Configured PPPoE. Afterwards, I disabled and re-enabled the LAN1 port from the modem connected to the WAN port of the R3, and the R3 automatically detected the Internet Port status.

Would this have been your first factory reset on a firmware after v4.0.41? I believe factory resetting after downgrading is the most important part.

This sounds like the problem (linked below) that I reported nearly two years ago on the 11th of June 2024. https://forum.netduma.com/topic/55787-wan-pppoe/ Yes, this is an issue in v4.0.540, and I am fairly certain that it is also an issue in every firmware version starting from v4.0.219. I have tested most, if not all, firmwares from v4.0.219 to v4.0.645 for the issue. Netduma Samuel confirmed they were able to reproduce the issue (linked below) on the 17th of June 2024. https://forum.netduma.com/topic/55787-wan-pppoe/#findComment-415179 Firmware v4.0.41 didn't have this issue for me; however, this firmware is from the 31st of January, 2024, and is very outdated. This is the solution I discovered to use the latest firmware without the PPPoE issue. 1. Downgrade to v4.0.41 (linked below). https://forum.netduma.com/topic/53938-new-r3-firmware-4041/ 2. Perform a factory reset and completely set it up. 3. Upgrade to the firmware of your choice. 4. Don't perform another factory reset. If you need to perform a factory reset at any point, you'll have to do all the steps again. I am unaware of any recent firmware without the PPPoE issue.

The workaround I use is this . I am able to successfully upgrade to the latest version with these steps, replacing step 3 with the latest firmware. This solves that PPPoE issue for me.

From what I read on the subreddit, it's dependent on how the broadband is being delivered, with DOCSIS causing the higher latency.

You should test to see if the ping is similar using only the Virgin Media equipment.

If everything is working correctly, other than switching ISPs, I think you are out of luck.