All Activity
- Past hour
-
Alg joined the community
- Today
-
I see. Maybe my test was glitching out I’ll try the ping. my line as previously mentioned is 900 down and 115 up. Duma OS router speed test sometimes will give me 888 or 907. Upload is 107-105. So I gone in and manually added 900 and 115 Hopefully this will help lock in results. I know 80 percent is a good value for download so I’ll do some more bb testing and focus on upload turning.
-
Redflame reacted to a post in a topic:
Returning to R3 — Advice needed
-
Zk_Trinita joined the community
-
Is it possible to add Gundam Battle Operation 2 for PS4, PS5 and PC to the Ping Heatmap?
-
Tulsigalangal reacted to a post in a topic:
NEW R3 FIRMWARE - DumaOS 4.0.540
-
VJ4YK5 reacted to a post in a topic:
XR1000v2 with fibre ISP 4th Utility (UK) - Icotera i5205-00 bridge device issues
-
Sorry to hear that but at least you've got a working solution and you could take your anger out and make it look better!
- 9 replies
-
- 4th utility
- fibre
- (and 7 more)
-
Losing Internet Connection Randomly
Netduma Fraser replied to Juan Camilo's topic in Netduma R3 Support
I've given you Early Access so you can upgrade to that version to see if it helps: https://forum.netduma.com/topic/60946-new-r3-firmware-dumaos-401147/ If not please provide a log from the router when the issue next happens Great keep us posted! -
Netduma Fraser reacted to a post in a topic:
Losing Internet Connection Randomly
-
I wouldn't have thought it would affect download as well so it may be more to do with how the test is performed. You could perform a big upload and do a ping test alongside and change the percentages to see if it is actually affecting it like the test says.
-
NEW R3 FIRMWARE - DumaOS 4.0.540
Netduma Fraser replied to Netduma Alex's topic in Netduma R3 Support
I've added you both to Early Access where you can see the massive change log for the firmware also: https://forum.netduma.com/topic/60946-new-r3-firmware-dumaos-401147/ It's primarily a bug fix/stability update so I think it's quite stable based on feedback so I'd suggest upgrading to it. I haven't seen that issue so it would be good if you could upgrade and then let us know if that continues. -
Netduma R1 problem with Fiber and COD
Netduma Fraser replied to CODduma's topic in Netduma R1 Support
It would be a necessary server, usually if you're in the EU you would see one in the EU although it can from time to time be located in the US. It's possible it's mislocated also, if you ping it you could tell. -
CF Vex changed their profile photo
- Yesterday
-
CF Vex joined the community
-
Losing Internet Connection Randomly
Juan Camilo replied to Juan Camilo's topic in Netduma R3 Support
Thank you for the access to the latest firmware. I will install it and make some tests. I didn't change anything regarding settings, until I started to play with the R3 versions. The ISP modem brand is a Skyworth GN543V. It looks like my ISP can't set that modem as bridge, so they offered me a DMZ so that's what I'm using. I will also be testing out the issue with others routers that I owned in the past, so I can have more options to determine better if it's an issue by my ISP or the R3 itself. Thank you guys -
I am having a similar problem. My wife has been complaining to me for the past couple of weeks about the internet going out for a few seconds while she is working on her computer and zoom/teams calls dropping. I have tried restarting both the router and my modem with no success. I have not changed any settings or my set-up. Any ideas on a fix?Thank you
-
Clumsy.exe, desync/extrapolation, and a temporary solution
kevo replied to Burtchnasty's topic in Call of Duty Support
I’ve done that a few times as well. The U.k,Paris, South America ping was around 110. I don’t even add steady ping but I’ll try it -
So today I tried setting the VLAN ID to 0 with the bridge device plugged in. It didn’t have any effect and there was no successful connection (red internet light). However, even with the Enable VLAN / Bridge Setup set as inactive in Advanced Settings, the router doesn’t get a successful internet connection from the bridge device at all now. Before it would at least get a successful connection despite the connection drops (which I am still witnessing on the bridge device). I have a feeling my ISP may have done something on their end after my last phone call, but I’m truly past caring now and can’t be bothered to speak to them again. I’ve begrudgingly attached the Dasan to the wall, but I did rip off the antennae which was mildly satisfying. @Netduma Fraser & @DARKNESS - thanks again for your replies.
- 9 replies
-
- 4th utility
- fibre
- (and 7 more)
-
Thanks for response. So I did that. I found 75 added no bloat, going up to 80 then offer same result. So 85 and up seems to be bloat city. So for download I stuck on 80. If I had 85 down and 95 up my download values and jitter was below 1ms. If it lower my upload lower, my download ping values increase and jitter could hit 6-15ms. So it seems strongly shaped can add more impact to download. Do you think this is just noise or can capping upload on fttp cause issues?
-
Redflame reacted to a post in a topic:
Returning to R3 — Advice needed
-
A versão 4.0.540 é a melhor ainda jovem! Testei a versão beta por meses e cheguei a conclusão que a versão pública 540 é a melhor para jogos, principalmente no controle de congestionamento.
-
Are there any major changes in the beta from .540? Would I be better off staying on .540 until the official release of the updated firmware? I also performed a factory reset recently due to a power outage during a reboot and the Wi-Fi LED's turned off, is that a bug and will it be fixed in the beta firmware? Sorry for all of the questions. I request to be added to the beta, please. Might as well pull the pin on that and see what happens. Thank you for all of your hard work and have a great day.
-
That actually makes sense. Yesterday, I played a few matches with 90ms latency. I have a question: when I start my PS5, there's an initial connection to a dedicated US server, which I assume is the PSN server. Is it normal for this initial connection to be in the US and not Europe? Since it's a dedicated server and I don't have its IP address, I can't block it to see how it behaves in games.
-
NEW R3 FIRMWARE - DumaOS 4.0.540
Tulsigalangal replied to Netduma Alex's topic in Netduma R3 Support
Hello, can I have access to the current latest beta firmware? -
Netduma R1 problem with Fiber and COD
Netduma Fraser replied to CODduma's topic in Netduma R1 Support
Pretty certain that's the cloud issue causing you to be unable to match with French/EU servers, however it's impossible for you to get 35ms ping to the US server so for whatever reason there is a mislocated server there that you can connect to so that one will be elsewhere in Europe, it's not actually a US server. Move it around and see if you can find a proper US server - you should be seeing at least 70ms to one. -
Yeah that bufferbloat test or using PingPlotter with those reductions in percentage is a good way to fine tune it. Don't use the in built test, depending on the available servers/where they are in relation to you they can provide abnormal results.
-
It looks like unloaded your jitter is around 3ms so you're not going to be able to get it better than that as that's the inherent stability of your connection. So I don't really think there is much if any room for improvement there. I would suggest forcing some servers further away, although you'll get a slightly higher ping the server load may be less allowing for a more even experience.
-
FlyTy757 joined the community
-
Clumsy.exe, desync/extrapolation, and a temporary solution
Burtchnasty replied to Burtchnasty's topic in Call of Duty Support
If you go out of the US, keep SteadyPing as low as it can go. For me, the UK and Australia are my lowest pings around 140ms I’m in Arizona. Texas I’m at 27, and the east coast I’m in the 50’s and 60’s. - Last week
-
First of all, thanks Fraser; thanks to your advice in other threads, I managed to get the R1 working. The R1 is indeed likely too old and outdated; in any case, it doesn't allow me to search for COD lobbies in Europe, so I set a filter for the US and it works. However, I can't play with my friends who are in France. The strange thing is, when I set a polygon over France or Europe, I can't join a lobby. But when I create a polygon over the US, I join matches and even see peers in France—peers I didn't see with the other filter settings. I'm going to try adding the peers I see when I'm in a party with my friends; maybe if I add all the peers, I'll eventually be able to start a match. Here is my analysis of the desynchronization issue people are facing, even when using a Netduma router. I believe it stems from a tick rate assignment or communication issue linked to the client's connection (especially fiber)! In France, there are four high-performance ISPs; I’ve tested three of them and encountered the same problem every time: my first match goes reasonably well, but then things deteriorate until the game becomes almost unplayable—what is commonly referred to as "desync": - Controller input lag - Reduced damage output and increased damage taken from enemies - Dying in a single frame - Character moving sluggishly for no apparent reason ...and various other consequences. Essentially, I suspect my tick rate gradually drops until it’s almost non-existent, whereas my opponent's tick rate remains adequate for the game. I haven't been able to pinpoint the exact cause regarding my connection; all three ISPs confirmed my connection was solid and error-free. The server assigns a tick rate to the client based on several criteria, and for some reason I can't fathom, my connection fails to meet one or more of them. Without in-depth diagnostics, it’s virtually impossible to identify the root cause. I’ve tried various configurations on both my ISP router and the Netduma, but nothing offers a lasting fix; sometimes I’ll have a good match, only for desync issues to return. I can't tell if playing on French servers or against European players is what exacerbates the problem, so the strategy now is to avoid both. With a US filter, I average 35ms ping compared to 7–22ms in France/Europe, and gameplay feels almost normal again. Unfortunately, there are still French and European players on US servers, so I still experience desync against them—though sometimes it’s less severe or non-existent. From what I’ve read, the Netduma doesn't solve this specific issue, though that isn't its intended function anyway. To summarize: Without the Netduma, COD Warzone works at about 20% capacity for me—and sometimes much worse against certain European players. With the Netduma R1 set to the Europe filter, I get "unable to join host" errors. With the Netduma R1 set to the US filter, Warzone runs at 70%—or even 90% if there are no European players present. The remaining 10% of issues stem from facing opponents with lower ping than mine; it makes things harder, and I don't benefit from favorable lag compensation. I’ve digressed a bit, but I thought this might help others in the same situation. Good gaming!
-
Clumsy.exe, desync/extrapolation, and a temporary solution
kevo replied to Burtchnasty's topic in Call of Duty Support
ill have to play on west coast servers or play or servers out of the united states. to the texas chicago new york servers my ping is around 25 atlanta its 8 -
Clumsy.exe, desync/extrapolation, and a temporary solution
Burtchnasty replied to Burtchnasty's topic in Call of Duty Support
SteadyPing is going to keep you in sync with the server timeline, as it delivers a very steady cadence of packets and keeps your latency absolutely flat. This will get rid of reverse peekers disadvantage (silent extrapolation), and should improve overall client side response. Unfortunately, lag compensation is its own beast. If you are a decent player, the SBMM is going to pull in higher ping players or people with really bad connections as it yo-yo’s you through lobbies. The only two options are: 1. Geo-Filter into lobbies where you naturally have a 40-60ms ping. That way you don’t have to max the SteadyPing buffer out and can keep the delay around 10ms. That will net you a 50-70ms ping which is pretty much in the middle of what I think most lobbies average. This option requires you to accept that there’s going to be some people that will outplay you due to their higher latency and lag comp. 2. Adjust the SteadyPing from match to match if you are going to play in your closest lobbies. Example: I played a match last night against a sniper I absolutely couldn’t kill. I would see his glint and be dead in 1 frame, with zero time to move or shoot. This player was fast and accurate. I asked him what his ping was and he told me it was 100ms. Using Clumsy, I think mine was already set to around 56ms. I alt-tabbed, adjusted my latency to 105ms, and I didn’t have a problem with him anymore. He ended up leaving that match and I finished with a 3.7 k/d with 5X kills. I also have fiber and it’s insane that I have to do that, but it is what it is. A stable, high ping is always going to better than an unstable low ping. The vast majority of people have unstable, medium/high pings. Lag Comp is a necessary evil, and there is no set it and forget it switch. Some folks are just lucky and sit right in that perfect spot where it’s always on their side due to their location/ISP/network. Getting around it requires being very proactive. -
Good afternoon been trying to configure my bufferbloat settings to get at least between 0.5ms - 1ms. I have att fiber I live in Los Angeles which I heard can get pretty amazing results if optimized correctly. I’ve been at it for couple weeks now trying to find the perfect congestion control and tweaks but I’m always getting around 3-4ms of jitter. I’m pretty new to the tech side of optimizing things but very competitive at fps games and lately been dying in 1v1 situations i know I should’ve won. I’ve also inputting speeds switching from 1000mbps to 940mbps to see if that helps but nothing. If any techs can help that’ll be awesome. Here are my results and more info about my connection. Any help would be amazing.
