Sergejs Kotovs
R3 Early Access-
Posts
25 -
Joined
-
Last visited
Everything posted by Sergejs Kotovs
-
Hi, quick update after applying the changes. At the moment everything is stable: no dropouts, no random disconnects, the router stays online and devices don’t lose connection. What made the biggest difference for stability: Manually setting the correct MTU (Telekom PPPoE: 1492). I’m not sure why it wasn’t applied automatically, but after setting MTU manually, stability and packet loss improved a lot. Fully manual Wi-Fi setup (separate SSIDs for 2.4 GHz and 5 GHz, manual channel/band settings) DHCP reservations added for the main devices After any change, even a small one (SmartBOOST rule, device settings, etc.), it’s important to reboot the router. Otherwise the changes don’t always apply cleanly. Since doing this and then leaving the settings alone, the connection has been running very well. Bufferbloat is now A/A+ and latency under load looks good. It feels like the R3 requires careful tuning, but once configured correctly it performs great. I’ll keep monitoring and will update again if anything changes.
-
I play Call of Duty: Black Ops 7 (PC). Geo-Filter / ping display does not show ping for any CoD servers (Warzone/BO7). It used to occasionally show pings before, now it never does. Is this expected behavior with CoD servers (ICMP blocked), or could it indicate an issue with Geo-Filter/ping engine on my R3?
-
Hi, quick update. I’ve applied your DHCP suggestions: Added DHCP reservations for all devices where I noticed dropouts Set DHCP lease time to 10000 Now testing under load. I also seem to have found a major cause of packet loss on my side: Setup: Telekom DSL → DrayTek Vigor 167 (bridge modem) → NetDuma R3 (PPPoE) Manually set MTU to 1492 (Telekom PPPoE) After setting MTU, packet loss disappeared (currently 0%). Wi-Fi changes: Split SSIDs into 2.4 GHz and 5 GHz Set channels/band settings manually Stability looks better so far. My household load: Family of 4, typically 5 devices actively streaming/using bandwidth (Netflix/YouTube etc.) while I game (wired), plus overall ~8 devices connected (phones, 2 TVs, 2 PCs, console). Question: is R3 hardware expected to handle this load without instability if configured correctly? Remaining issues: Bufferbloat results are still poor / inconsistent. Even with Ping Optimizer/Anti-Bufferbloat set around 90/85 (sometimes 90/90), speed tests inside the system show very low throughput, and still show latency increase under load. Ping Optimizer auto-detect/auto-adjust fails (it reports it can’t adjust/optimize correctly). Could you advise the best way to fix: inconsistent/low throughput during bufferbloat tests, latency increase under load despite conservative QoS settings, Ping Optimizer auto-adjust failing? I’ve already sent logs about the errors I’m seeing. Please check them and tell me what the errors mean and what settings you recommend for my setup. Thanks.
-
Packet loss during normal use and gaming Internet connection drops by itself (the router loses connectivity) Wi-Fi devices take a long time to load pages/apps or reconnect Overall performance is inconsistent and my kids complain daily (streaming/online apps lag or fail) This is a household of four people, so the router should easily handle typical family usage, but it constantly causes problems. At this point it feels like something is wrong with the firmware or stability. Could you please advise what logs/settings you need from me to troubleshoot this? Also, if you have a newer firmware build or a beta version that improves stability, I’m willing to test it. Thanks, SKWildCat R3_2026-01-24T21_28_17.522Z_logs.txt
-
Geo-Filter Not Detecting Call of Duty
Sergejs Kotovs replied to Sergejs Kotovs's topic in Netduma R3 Support
I managed to fix it myself. What I did: Rebooted the router Rebooted the PC Removed my device from Geo-Filter Re-synced the cloud Added the device back to Geo-Filter Launched the game, waited 1–2 minutes in the lobby Started Multiplayer After that, Geo-Filter detected the game/servers again and everything works normally now. Thanks anyway, I guess. Problem solved. -
Factory reset → reconfigured PPPoE + native IPv6 (Telekom, Germany) → internet works, but Geo-Filter no longer detects Call of Duty (game not recognized, no servers shown). Any fix?
-
f CoD hosts don’t respond to ICMP and even traceroute can’t provide a “last reply”, then I understand why Geo-Filter can’t display latency. However, the real issue is that in Call of Duty this doesn’t just break the ping number. It effectively disables the core features people buy the R3 for: SteadyPing / “constant ping”, Server Quality / stability metrics / connection quality indicators, etc. In BO7 it feels like 70–80% of the Geo-Filter “quality” features become decorative, and what’s left is basically just the map and the radius. And Call of Duty isn’t some niche title, it’s one of the biggest and oldest mainstream online franchises. Having most of these features not work specifically in CoD is, honestly, pretty awkward. Could you consider an alternative latency/quality measurement method that doesn’t rely on ICMP, for example: estimating RTT from the active UDP game flow (real in-match traffic), measuring at the socket/flow level against the actual endpoint the game is using, a fallback approach: if ICMP is blocked, use UDP probes (or another method) instead, and/or at minimum an explicit indicator like “Filtering active / server inside radius confirmed”, so users can verify Geo-Filter is actually applied even when ping can’t be measured. Right now it doesn’t feel fully correct: CoD is exactly the use case where these features should work best. Thanks, SKWildCat
-
Здравствуйте, служба поддержки NetDuma! Я использую NetDuma R3 и функцию Geo-Filter в Call of Duty: Black Ops 7. Geo-Filter постоянно показывает сообщение «Невозможно пинговать сервер» и вообще не отображает задержку . Это происходит не с одним или двумя серверами. Это происходит с каждым сервером постоянно , в течение нескольких сессий. Столбец ping / информация о задержке остаются пустыми, и маршрутизатор никогда не отображает значение ping для обнаруженного хоста. Из-за этого я не могу сказать, работает ли Geo-Filter на самом деле или фильтрует ли он правильно. Игра по-прежнему находит совпадения, но роутер не предоставляет данные пинга, поэтому эта функция становится практически бесполезной для выбора сервера. Что я наблюдаю: Geo-Filter определяет игровую сессию/серверы, но для всех из них отображается сообщение "Невозможно пинговать". Значения пинга/задержки никогда не отображаются. Это происходит в 100% случаев (а не периодически). Спасибо,
-
Dear Support Team, I'm experiencing an issue with my NetDuma R3 router and the Geo-Filter in Delta Force. When Geo-Filter and Geo-Latency are enabled, the game still connects to a server in Singapore. If I disable Geo-Latency and set the radius to Europe, the game finds a lobby but then gets stuck at 50-60% loading and eventually disconnects. It appears that the router blocks the Singapore server, but only after the initial connection to the lobby. Could you please explain why the Geo-Filter doesn't block the Singapore server from the start and how I can resolve this issue? Thank you in advance for your assistance. Best regards,
-
Please add Arena Breakout Infinitive Filter
-
Please add Arena Breakout Infinitive Filter
-
And finally I got the long-awaited result, With this update I get the full internet speed that I get from the provider, And note Pink 6 milliseconds is fantastic
-
Thanks for the update, I immediately noticed the difference, The game became smoother,Enjoy this update, Once again I want to say thank you guys for being here. Without you, we wouldn’t have known what a geofilter is, I think this is the best software for us gamers, All the problems that exist, I am sure that you will solve them soon, We love you guysv, Especially you , Netduma Fraser
-
Problem with download and upload speed, poor ping.
Sergejs Kotovs replied to Sergejs Kotovs's topic in Netduma R3 Support
Thank you Netduma Fraser very much for the link, but I already Received. the link from Mowment,The update was successful.Now everything is working fantastically.. I played several matches. And I have this feeling. The game has become much smoother. Previously, I had to shoot half a clip to kill someone now. It feels like 2,3 shots. And the enemy is hit. Dad, in general, the ping stabilized; in the speed test it showed 6 milliseconds.Continue in the same spirit. Well done. Looking forward to more updates, it was getting better and better and better. -
Good afternoon, I have no idea, the dash is not updated for people, but I still have the new firmware. v4.0.21, I don’t remember, could you give me a link to the firmware that is not automatically updated.My problem is that on my old router the download speed is 250. And the upload speed is 40. But when I connect I think about it. R 3. Then I have. Download. 205. And upload. 25. How to fix this? This is disappointing.Also, my ping in conjure with the old root is 9 milliseconds to 15. with netduma r 3 I have twice as much. That is, 36, 60. in call of duty mw3
-
Ich habe auch R3 ruter mit vigor 167 arbeitet gut.
-
Guten tag, Wen zwei ruter ist verbunden du krigst doppelt NAT , Du muss eine modem kaufen Vigor167 diese modem ist beste vür Telekom, guck diese video ist alles erklert,
-
Dont come in Duma os, This dumaos4 doesn,t work at all
Sergejs Kotovs replied to Sergejs Kotovs's topic in Netduma R3 Support
Thank you very much for the quick rsponse, that,s all.Everything worked fine Enjoying this netduma r3,
