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.

I believe it might be. The labels aren't always correct, so sometimes they can be misidentified and sometimes the server/peer mislocated. This is what mine looks like when connecting to EA servers. When clicked on, does yours display the city/town as London?

Do you ever connect to that peer connection?

When you tried reducing the filter circle to include only the London servers, were you just infinitely searching for a game?

This is about Ultimate Team, right? If so, when I found an opponent on Division Rivals, then the server would appear.

I am able to connect to the London servers just fine, so the servers aren't currently down. When using filtering mode, try reducing the filter size of the circle to exclude the non-London servers.

Thanks for trying to help; however, I am currently using bridge mode on a modem. That's fantastic. Hopefully, the issue can be fixed and released soon.

Hey, I'm just checking to see if the team was able to reproduce this or if this is an isolated issue.

I have an issue with the R3 WAN connected via PPPoE. When the modem resyncs or restarts, the R3 doesn't automatically reconnect to the modem. This requires me to manually reconnect the connection via changing connection type and changing back, disconnecting and reconnecting the WAN Ethernet cable from the R3, or restarting the R3. I believe this issue is related to the latest firmware (v4.0.219). To my knowledge, this didn't affect me on the previous firmware (v4.0.41). I have tried factory resetting the R3 to resolve the issue, but it still occurs when I restart the modem.

When I tried, the error message said, "Gateway is not reachable on the LAN network," which I assume isn't reachable because I was trying to reach it through the WAN port. Could the ability to static route through the WAN port be added to the R3 in the future?

I have a bug with features that require you to choose a device by the device's name and IP address, such as hybrid VPN, internet rules, etc. If the device has a local link address, this takes priority over the private IP address, resulting in the features not working on the device. Additionally, is a device supposed to have that many IPv6 addresses? Edit: Restarting the R3 has fixed the issue by removing the local link address and reducing the IPv6 addresses to two.