Netduma Liam

Last I checked, you should still be able to filter which of the SDR servers you connect to. This may be slightly different from the actual game server, but it should be close enough. If you set your filter area for Western Europe, it would make sense that you're unable to connect to a US server, unless I've misunderstood you there?

I'd suggest signing up for the Early Access beta as Fraser mentioned, you can then try a newer firmware with bug fixes.

If you add your Xbox to Geo-filter, but select "Choose manually" when prompted to pick a service, it'll then automatically filter any games you play, including Destiny. Let us know if you need anything else!

Can you try a different LAN cable from the R2 to the device you're watching YouTube on? If Wi-Fi is fine, it suggest we may just be dealing with a fault cable here.

Have you got Share Excess disabled when you go to QoS -> Bandwidth Allocation -> Click the three-line menu in the top left of the panel? If so, that would explain it, please re-enable that and it should work fine afterwards. We receive a lot of DMs and they're hard to track so it's not really feasible to provide support over DM.

Can you run a speedtest through a third-party such as speedtest.net, are the speeds what you'd expect? Can you also provide a screenshot of how you've currently got QoS setup? We can likely find a solution to the problem by making some tweaks there.

Maybe we're dealing with some Wireless contention here. Could you try downloading a Wi-Fi Analyser (there's one on the Microsoft store called Wi-Fi Analyser) and run a couple tests. Find which channels are least congested and switch your Wi-Fi on the R2 to use those. I know you mentioned you'd experimented with some different ones, but this test actually tells us which are the best to use. Now the R2 is back in the network, you've currently got ALL devices connected to it again, is that right? Have you still got the Traffic Prioritisation rule we added for your games console, and you're still seeing occasional stutters and ping spikes with this? Is this occuring when the network is very busy (downloads, updates, etc) or do you get this regardless of how busy the network is?

I'll let the team know the big release is today and we'll see if we can get it on Ping Heatmap! Are ALL devices on the network connected to your XR1000 or do some still connect to the upstream router/modem? What device are you playing on? How is it connected to the XR1000? Do you know anything inbetween your gaming device and the XR such as powerline extenders, Wi-Fi boosters, etc?

It may take a little longer than you are expecting, but we're working on it and we'll resolve it, when we do, we'll push an update.

Yeah I think it's more a case of how HybridVPN reads the config files, it clearly has issues with the first one and not the second. We're still investigating so we hope to have it fixed for then next update. Feel free to send the config files you've got over to us, it may also help our developer in debugging the issue.

It's proving harder than expected, we're getting very mixed results each time we try to capture new data for the game. We're going to have to get some developer input on this one and see if we can work it out. If so, we'll push a cloud update!

We believe there may be an issue with the R2s throughput when it comes to PPPoE. Hence why Fraser suggested using the XR500 to handle this. You can then disable any and all DumaOS features on the XR500 and configure all of this on the R2 if that's what you'd rather use. Just be sure to put the R2s WAN IP in the DMZ of the XR500, you can find this setting in Settings -> Setup -> WAN Setup -> Default DMZ server. Test your throughputs then through the R2 and it should all be good.

Sure, I'll speak with the team again and see if this as easy as we suspect and get it done as soon as possible if that's the case.

I don't believe so as yet, I'll chase up the team. To be clear, it may still show them as peer connections, but you should be able to filter them correctly afterwards.

Since the reset, can you access the DumaOS interface if you use an incognito/private window in your browser?

I'm afraid not, I asked about it this morning, there's is one bug which is now fixed, but I believe there's still a separate issue. We'll get an early access/beta firmware built when we've got more information on the issue and hopefully we can give it to some people such as yourself and you can test it. I don't have any kind of an ETA for such a fix as we're not sure whether we're going to be able to do that yet, but in an ideal world that's how we'll proceed.

We had some issues with our original cloud updates so we're going to be pushing another one. I'll remind the team again today just to get it through a little quicker and we'll see if that helps.

Can you clear your browsers cache now that you've completed the update and see if it works after that?

I'm pretty sure the issue actually sits on the WAN side of the R2 so we are looking into how we can resolve this, unfortunately it's quite a complicated issue (as always seems to be the case with IPv6). We'll keep at it, but in the mean time you'll need to use IPv4 with the Xbox.

OK, let me check with the team if there's a newer version we can get you on. I'm intrigued that a specific device(s) cause this problem. Do you have any QoS, Geo-filter or Traffic Controller configuration that apply to these devices? If so, are you able to disable these when they're next over and see if the issue still occurs. Is there any option for you to connect these PCs to the modem via wired as opposed to wireless and check if the issue still occurs?

Not just yet, still testing and improving it. We'll likely post on our Twitter when we ready to share more info on it so that would be the best place to keep an eye out!

We are still working on it for the moment, as the new FIFA is coming out soon we're also doing captures on that and testing it with Ping Heatmap and Geo-filter, so rest assured we're still working on it.

I see what you mean, displaying it's current IP address as well as adding the option to rename it from there would be handy! I'll add it to the roadmap and let the team know. Thanks Bernard.

Thanks for your feedback! We've actually been doing a lot of research and work into more accurate detection of device types. Doing this will also then enable us to give them all their own icons as you mention. I'm not sure exactly when we're going to be introducing that as there's still quite a few variables involved. Perhaps we can just make icons user changeable though, that's a nice idea. I'll add it to the roadmap!

Not as yet I'm afraid, I chased up the developers about it this morning and they're going to see if they can allocate more time to debugging this issue today/this week.