
Devastate
R3 Early Access-
Posts
41 -
Joined
Everything posted by Devastate
-
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?
-
Hybrid VPN - Improvements
Devastate replied to Devastate's topic in Feature Ideas & Improvements for DumaOS
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.
-
Not connecting to my nearest server
Devastate replied to ShinyShelvey's topic in NETGEAR Nighthawk Support (XR range)
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. -
Not connecting to my nearest server
Devastate replied to ShinyShelvey's topic in NETGEAR Nighthawk Support (XR range)
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? -
Not connecting to my nearest server
Devastate replied to ShinyShelvey's topic in NETGEAR Nighthawk Support (XR range)
Do you ever connect to that peer connection? -
Not connecting to my nearest server
Devastate replied to ShinyShelvey's topic in NETGEAR Nighthawk Support (XR range)
When you tried reducing the filter circle to include only the London servers, were you just infinitely searching for a game? -
Not connecting to my nearest server
Devastate replied to ShinyShelvey's topic in NETGEAR Nighthawk Support (XR range)
This is about Ultimate Team, right? If so, when I found an opponent on Division Rivals, then the server would appear. -
Not connecting to my nearest server
Devastate replied to ShinyShelvey's topic in NETGEAR Nighthawk Support (XR range)
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.
-
My hope was to be able to see the DSL status and statistics without having to lose access to the internet whilst looking, due to only one LAN port on the modem. So to bring up my previous reply, is it right to assume the R3 isn't capable of doing either of them?
-
The user guide doesn't mention Wi-Fi anywhere in it, and it is titled "Vigor130 Series VDSL2/ADSL2/2+ Modem User’s Guide." Also, 192.168.2.1 is unreachable whilst behind the R3.
-
I wish it was that simple. Unfortunately, that doesn't seem to be the case with this modem, as I've searched this forum and others have had difficulties accessing the web user interface as well albeit not through the R3. The modem is the Vigor 130.
-
Thank you for the response. I am trying to access the modem's web user interface from behind the R3. The solution from the manufacturer's website is to create an untagged virtual WAN interface. Or a different solution from the web is to create a static route from the modem's LAN port to the router's WAN port and vice versa. Is it possible to do either of these with the R3?
-
Does the WAN port of the R3 have an IP address, or can you assign one to it?