All Activity

Hey thank you! That solved the issue nat type is now fixed!

If your Internet Service Provider (ISP) router gives you WiFi then you need to put the R2 WAN IP - found in the WAN Settings page on the R2 into the DMZ function on your ISP router. If you didn't do a factory reset after upgrading to the DumaOS 4 Early Access firmware then please do so and it will behave better after that. Do this first then the DMZ.

Hi thanks for replying, When ever i try to do anything in the settings. It will say " Pardon out mess " And it all ways makes me press retry. And i do not have any geo filter on. And i am on computer.

What is the model of the modem/router the R2 is connected to and how have you set that to ensure all traffic flows to the R2? E.g R2 in its DMZ, modem/bridge mode Have you done any port forwarding on the R2 or used the DMZ? What platform are you playing on? Are you using the Geo-Filter? Do you get an Open NAT with it disabled?

please help me solve this

Have you upgraded to this version yet? https://forum.netduma.com/topic/60946-new-r3-firmware-dumaos-401147/ If not I would highly recommend doing so to see if you get any of the same issues. The fact that you need to wiggle a cable around to make it work would indicate to me that it's probably a faulty cable and replacing that would likely fix it. Can you provide a screenshot of the LAN Settings page and the logs from when the issue happens if you still get the issue on that firmware please?

Hi I recently noticed that my Netduma keeping on disconnecting the devices connected to it, when I checked the router, its showing no networks, I have to phyiscally move the cable around on the router to make it work again, the other issues, I cannot see my devices no more on the device manager list, like the screenshot below, so I am not able to use filter, I tried to hard reset, factory reset, with no hope, I think there is a serious issue in the device, with sad expection, my last R1 I bought 10 years ago works fine, but this new version is not as expected !

So the Geo-Filter is measuring the latency to the server itself and the in game ping is showing that calculation + processing delay. All games have it but not all choose to show it in their ping calculations. As a rough guide up to ~30ms on top is okay though it can be lower so it can indicate that server is under a heavier load, in which case forcing a different server even if it has a slightly higher ping shown on the Geo-Filter might actually play better for you. It's essential the Geo-Filter is enabled before the game client (e.g. Steam etc) if on PC or the game have been launched. If you change Geo-Filter settings when you're on the game then you will need to restart the game for those changes to take effect, otherwise it will use the previous Geo-Filter settings and appear not to be working. Strict Mode should also be enabled & Fast Search should be disabled, they are by default so if you haven't changed them you can ignore it. If you have changed or want to check them can be found in the Geo-Filter menu that can be found by clicking ⋮ in the top right hand corner of the page and go to Settings. If you do these things then it will stick to the radius you've set, other than any servers on the global whitelist (for example Dublin usually) or manually allowed servers (like the Dublin servers).

What do you want it to be? I'll change it for you

I won't let me edit my name only email and password

Thank you. I will wait for the update.

Awesome. Will give it a go. I've noticed on the Duma os4 it would say the ping is like 23 ms to Dallas, but call of duty reads 48+ on the latency. Is this just because one's testing actual server latency. And one's testing something else? I noticed too that majority of the time, if I'm doing some testing for instance. Let's say Dublin. It will still put me into servers in the US. Despite having the location set over there. I would imagine how it's supposed to work is if I place my location at x. With a mile radius of x, it shouldn't connect to anything outside of that range. How it used to work if I recall, was it would keep rising your ping let's say it started at searching for a match with 36 latency, it would keep going up til it found a game. It doesn't do that now. I use the ping to determine if im connected to another location server, besides us. Because anywhere in the US since that's where I reside, it's under 100. So for some reason trying to connect to other servers in other countries, it still puts me in the US lobby.

Try with 70% as that's our suggested starting point and adjust from there based on how it feels/until you don't see any spikes - keep in mind that during peak times spikes like that are more likely to occur due to ISP peak time congestion. It will always try to connect to the Dublin server as its for authentication and required for online play so if you allow it you can play with the filter enabled but you will need to do so a few times as there will be multiple servers in that location. Once you've got all the ones that appear blocked there it will work. If you block a server it should keep you connected to it until that connection has been severed and then it would be blocked. It's nothing to do with Ping Heatmap, it has a pre-compiled list of servers, they have become out of date and when they do they're unable to be pinged, by default they then show N/A -1000ms because it timed out once it hit 1000ms without a response. Everyone with Ping Heatmap is seeing the same for CoD at the moment, myself included and it will stay that way until we've updated the pre-compiled list with an updated set until they inevitably get out of date again. Here are the server locations, they never change:

Okay so an issue with your ISP or game perhaps. Click your name top right of the forum and go to account settings, you can change it there

looks like the Server IP for Dublin might be 185.34.106.103

Congestion Control was likely set to Always, and the 50/50 was just whatever it defaulted to — I didn't manually set that. The main issue I want to focus on is the Geo-filter itself. When the Geo-filter is enabled, I cannot get into a Call of Duty match at all and have to disable it just to connect. I have my location set to Oklahoma, but even with that set it was still trying to connect through the Dublin server. Also, I want to make sure I understand this correctly — if I'm already in a match and I click block on a server showing in the Geo-filter, does that drop me from the match since I'm blocking an active connection? Just want to understand the right way to use it so I'm blocking servers before matchmaking rather than during. So we have looking at a few issues. One being that connection error when trying to login to the server in itself, two is the packet loss. There should be 0% loss. Reason i say 0 is because there's no latency spike on anther router. But i can assume that's due to how the duma os handles routing. So that might worth checking into, because that still doesn't explain still If you click the heat map, ping the call of duty servers every singel one get's NA/ on the latency test. so we can't actually see were the servers are, it's notforcing the geo filter by just limiting me to the oklahoma servers, and it's failing to connect if, geofilter is enabled. a lot of back and forth having to turn it on and off, connect, disconnect to get it to even allow the connection.

Yea the same issue happens

Is Congestion Control set to Always or Auto? Have you found 50/50 gives you the best results or just randomly set? SmartBOOST should be used so the devices/applications you care about get prioritized above traffic you don't care about as much, if there was something impacting your ping results then this would help it. Given the ping statistics you provided, you had a maximum of 442ms but over 232 successful packets your ping averaged 22ms which indicates that you only experienced a couple of quick spikes rather than a consistently high ping and so it was relatively stable overall with 2 packets lost at just under 1% that's quite acceptable and I assume they would have happened with those couple of spikes which makes sense. So far then it indicates it's more of an isolated incident of spikes rather than a persistent one. The logs contain entries that can look like issues but are normal processes, that's why it's best for a user not to try to diagnose issues solely based on logs, if issues are occurring that can't be diagnosed through normal means then logs can be looked at for more information by the devs but its very rare this is needed and the entries you've mentioned aren't anything I haven't seen before. For example the hostapd entry can occur when Ping Optimizer fails and that could occur for any number of reasons such as the server times out and so it can't set the correct Congestion Control percentages etc. Some can appear when it's not using a certain setting but it looks like an issue because that setting isn't active and fails, that's what I mean by verbose, we're not heavily restricting the output to the log, normal processes appear there that can seem troubling if you're not used to them. cfront & RTNETLINK errors weren't in the logs you provided but again they're not necessarily any immediate cause for concern.

Check direct to your ISP modem/router to see if you get the same issue because if you do then nothing you do on the R3 would make a difference as it wouldn't be the cause

To clarify my setup: The Arris SB8200 (DOCSIS 3.1) feeds directly into the R2. The R2 is my main router for all wired/ethernet devices. I have a second router connected to the R2, but that is only used for WiFi devices — all gaming and primary devices are on ethernet directly through the R2, so all relevant traffic is going through it. To answer your questions: - Speeds: 120 down / 20 up, and yes those are entered into the router - Congestion Control: set at 50/50 for both upload and download - SmartBOOST: not currently enabled - The R2 is not in DMZ or bridge mode as it is the primary router — the SB8200 is a modem only I also want to flag some errors from my system logs that weren't addressed: hostapd is throwing "Failed to set beacon parameters" repeatedly every few seconds, cfront bottomch is constantly reloading interface IPs, and QoS is generating RTNETLINK errors. These seem like they could be contributing to instability and I'd appreciate those being looked at as well.

I factory reset my R3 and the problem still there lol I don't even know what to do at this point. I just wanted to shoot my gun. ggs only

If you've fully disabled the Geo-Filter and it's still occurring then check direct to your ISP modem/router to see if you get the same issue Yeah it's getting outdated very quickly at the moment, the team are aware and will push another cloud when they can

Falar nisso os servidores ainda não aparecem no ping.

I removed the Geo-Filter from now but still the same issues

Very likely an authentication server is getting blocked, look on the map when that error appears, look for a blocked icon and allow it. Repeat the process as it may take a few times then it will work. If you could provide the IDs also we can get them globally whitelisted.