Netduma Liam

There may still be some servers that we need to manually whitelist so you don't have to manually allow these in Geo-filter. If you do find servers that you need to do this with, let us know and we can amend that in a cloud update. If you disable strict mode, dedicated servers will no longer be filtered but peers will. As Destiny works via server-based matchmaking now, you will want to leave strict mode enabled.

Sorry to hear this! Are you seeing this issue in all browsers? If you open the interface in an incognito windows, are you still getting this error? Do you have any browser extensions enabled such as an adblocker? If so, could you please temporarily disable them to see if they're causing the problem?

Hey @Swgohlegend, that's great, thanks. We should be able to access it now and will let you know what we find.

OK, could you please put your R1 in the modem's DMZ and report back, that should mean we can then access it.

The devs still don't appear to be able to access your R1, could you please confirm that you've got access for remote support enabled and your R1 is in the upstream modem's DMZ?

That model is running a Broadcom SOC so you're all good there. Have you experienced any further crashed since Fraser's latest advice?

What the model of the Arris modem? I'll see if I can look it up.

Welcome to the forum! How do you mean you're not properly moving the files to the OpenVPN config file? Have you found and read through the below guide, it may be helpful for you: http://support.netduma.com/support/solutions/articles/16000087492--dumaos-optimal-settings-guide-hybrid-vpn

It may just be the servers in the UK go offline around that time as it's no longer considered peak playing hours, As Fraser mentions this will likely be a different story on weekends.

Welcome to the forum! I've responded to your email earlier today. To be totally clear, it's not a case of us not wanting to process a replacement, we just need to confirm that it's not something we can resolve through configuration changes. For a similar reason, It's also not always guaranteed that a replacement will be a solution, hence why we can seem apprehensive to do so.

Unfortunately I think this is present on both original release and beta firmware. I remember you saying you also have issues with the BT IGMP IPTV so I'll chase this up internally to see where we are with both of these issues.

The XR500 is capable of over 2.4gbps over Wi-Fi, but it still uses gigabit ethernet ports. The R2 is also limited to gigabit over wired and wireless.

I'm afraid not, 1000mbps is the maximum the ethernet ports on the R1 can do, this isn't something that can be increased through a software update.

Welcome to the forum! That should be fixed now, if not then please re-sync cloud from the three-line menu.

I spoke to one of the devs about this a couple of days ago, it's still in the works but unfortunately we don't have an ETA at this stage.

Sorry about that, we're pushing an update today that should resolve that.

Apologies this issue has taken so long to resolve, I'll follow up with the team now and see where we are with it. Last I heard we were able to replicate it but unforunately it's quite a complicated issue to resolve.

Sure thing, yes if it gets to that point I don't see why we won't be able to send a new one out to you.

Sorry to hear the beta firmwares didn't work out for you, we are still working on the 3.0 beta so there will be new versions and eventually a full release. Unfortunately it's difficult to give an ETA as to when this may be, but we are working hard at it!

Do you have another router that you can run behind the R2 as an access point and have all Wi-Fi devices connect to this? This will allow us to test if it's Wi-Fi/DHCP that could be causing the disconnections.

Do you have Share excess enabled in the Bandwidth Allocation Menu? Also, do you have any custom distribution configured in Bandwidth Allocation or is it just equally distributed?

We're working on it! Unfortunately as these are changes server-side it's hard for us to work around, we're currently testing but I don't yet have an ETA for a fix.

Hey! Not just yet, we're always working on it though so shouldn't be too long hopefully. Are you experiencing any issues with the current firmware?

Go to QoS -> Traffic Prioritisation -> Add device -> Select your iPhone and then 'Advanced' and use the below config: Source: 1-65535 Dest: 1-65535 Service: TCP&UDP Let us know if this solves the problem and we can then consider what a more elegant solution might be.

Could you add a rule to Traffic Prioritisation for the iPhone and see if this helps?