Netduma Liam

It won't turn off during a reset. Are you now able to connect to the R2 Wi-Fi network and complete the setup wizard?

OK, could you please do the following: Unplug the WAN cable from the R2 (the blue port) Hold the reset pin on the back of the R2 for thirty seconds Wait 5-10 minutes If it hasn't already, connect your laptop to the R2 via either wired or Wi-Fi Got 192.168.77.1 from an incognito window in Chrome and complete the setup wizard again, make sure the WAN cable remains unplugged. That should allow you to get to the interface normally, after that connect the WAN cable and reboot the R2.

OK great, so we know the cabling is correct. What also won't be helping here is that DumaOS isn't yet optimised for Safari, which I believe you are using. Could you please instead open a Chrome browser and go to 192.168.77.1 in the browser. Complete the setup wizard from here, skipping the WAN setup as I mentioned previously.

Welcome to the forum! The first thing to do is to complete the setup. On the screen you show in your first screenshot, please click 'WAN Setup' then 'Skip' and you can complete the setup wizard. Once completed and you're in the interface, give the R2 a quick reboot, that may resolve the issue. If that doesn't resolve the issue, can you confirm that the R2 is connected to one of the LAN ports on the back of the ISP router? It may be easier to provide a picture to confirm this, though I would think that your ISP would've also confirmed this was correct when you spoke to them.

We're still working on it, are you still able to use the config files manually? Thanks for your patience.

That's a good suggestion and it's already on our roadmap so it's certainly something we're looking into in future.

Welcome to the forum! Are you holding the reset pin for at least 30 seconds, then leaving the R2 a few minutes to reset? If so, you might just need to clear your browsers cache when accessing the interface again.

You are running a slightly older firmware, it might be worth downloading the latest version here and installing it: https://www.dropbox.com/s/8z4kcynmo3glplp/DumaOS-R1-3.0.207.sig?dl=0

We have a list of games we need to test and capture, then run through some internal tools to see if we can identify it's traffic. We're working through this list and I've added DBD to it.

As far as I'm aware there isn't another way to do that. You could experiment with using a VPN, but that'll likely result in much higher ping.

How do you mean exactly? To play on servers outside of the the region you're located in? This is possible with Geo-filter, though if your ping is too high (i.e. the server is too far away) you'll probably find you're not able to get in to a game.

Did you factory reset after installing the upgrade? Could you confirm that you're now upgraded to version 2.3.2.130?

It's possible they're not located properly in Geo-filter. We'd need to test it and add proper support for it, as clearly it's not working great at the moment. I'll message the team and ask them to do this.

We don't have the servers whitelisted, I just though we might've done because you had strict mode disabled. It looks as though server is essential for gameplay, as if it's an authentication server perhaps. If you manually allow that server, do you then just consistently play on that server? What ping are you getting?

When you add the console to Geo-filter, could you please make sure you're selecting the 'Choose manually' option when prompted?

OK apparently it's not whitelisted, so there shouldn't be any issues. If you go to the three-line menu in the Geo-filter map, do you have strict mode disabled? If so, please enable it. Then you'll only get connected to servers within your polygon.

That's very odd, so when crossplay is enabled, you're then seeing a blocked icon on the map for these peers? Could you remind me what platform you're playing on please?

Looks like it's whitelisted in DumaOS, I'll pass the ID on to the team and see if there's a reason for this.

So you're able to block the servers in DumaOS when you have crossplay disabled? That's bizarre, are they definitely the same servers? Can you compare the IDs?

Thank you, I've passed this onto the App dev and will let you know once I've heard more.

Je ne sais pas encore avec certitude, cela dépend vraiment du temps qu'il faut pour passer les tests. Si c'est assez rapide alors oui peut-être !

It would probably be best to yeah, just to make sure you don't get connected to it again in the next game.

The servers you're seeing in the server browser aren't located in your radius, so they're getting blocked. What are you now seeing on the Geo-filter map when you search for a game regularly?

It's something we can do without needing to release a new firmware, so hopefully soon. The team member who looks after this will be back in the office this week so he should be able to update it then, provided it doesn't require any developer input.

We're still working on improving how Geo-filter and Ping Heatmap work with Battlefield. What about Geo-filter doesn't seem to be working for you? How do you currently have it configured?