Devastate

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.

Unfortunately, it might just be Virgin Media. If you search the r/VirginMedia subreddit, you'll find multiple posts relating to increased ping compared to other providers.

Here's a Jam video of me reproducing the problem. Hopefully it's reproducible on your end. https://jam.dev/c/5639858f-ba78-44f8-918d-b69ee888f538

Hey @sw_mp @paul1987, This was the method that worked for me some time ago. I hope it can help for both of you too. https://forum.netduma.com/topic/55901-netduma-r3-server-line/?do=findComment&comment=415394

Could the issue above be the same issue you are having?

My suggestions would help streamline the processes to make it easier for the user. My inspiration for the suggestions comes a lot from the internet rules tab. 1. Yes, precisely that—a toggle switch so you don't have to delete and re-add device rules. 2. Yes, you can. However, if a user wants to remove or add an activity, they'll have to edit the existing rule. With suggestion 1 implemented and the activities separated by device rules, they could just hit the toggle to turn each activity on or off. 3. No, not for me anyways. 4. Yes, I've seen this now; sorry about that. Exactly the same idea. 5. That's great; thank you. 6. The ability to have multiple concurrent VPN connections.

I would like to suggest the following improvements to Hybrid VPN: 1. The ability to enable and disable the VPN connection per device rule. 2. The ability to have multiple rules per device. 3. The ability to apply the VPN connection to the entire network. 4. The ability to switch between VPN configuration files. 5. The ability to enable or disable a kill switch. Most of these improvements would decrease the amount of time spent editing VPN configuration files and device rules.

An easy way to check for tomorrow is when you are selecting kits. If your ping is around 4 ms, then you'll be on London servers, and if it's around 11 ms or above, then you're most likely not.