Jackal235

Lag compensation depends on your ping, so playing with bandwidth does nothing to it. However... lowering your upload speed may delay packets with the information of your position to the enemy, especially on jammed networks.

Get fiber or deal with it is not an answer. If you buy a product you expect to get from it what it's supposed to do. I have never seen routers supported that badly. The current official Xr1000 firmware with that many bugs is more of the beta than a real deal. BTW... many of the fiber ISPs, including mine use PPPoE!

You're maybe pushing but the fact is, that for over 2 years, there has been no fix to PPPoE or many other issues for that matter. There is obviously something very wrong with this company, whether it's financial or capacity problem, people get really frustrated with this incompetent support.

XR1000 does not support congestion control on PPPoE connections (especially for the upload traffic). It's been like this from the very beginning with no hope for the future fix. here is my:

on PS5 everything is exactly as with MW2 .

It's a part 2 of MW2. -all my game setting remained from the previous game -all unlocked weapon and skins still there - playing on the same servers -being matched from the beginning with high skilled players from MW2 -lag comp feels exactly the same -old maps from the last 12 years Same as on MW2 can't play in lobbies below 30ms. Have to force 60-80ms games to make it playable.

If I had no clue, about the Xr1000 new firmware release, I wouldn't give ETA either- LOL Almost 2 years ago Netduma Luke wrote this. It was marked as a sticky. What happened to it? "Hi everyone, This is an update for you guys on where we are with DumaOS and specifically, the XR/NPG routers which is why we have posted it in this subforum. First of all, here’s the current status for each XR router, including links to where you can get the latest firmware for those of you who don’t already have it installed: XR300 – V1.0.3.68 (DumaOS 2.0) XR450/XR500 – V2.3.2.130 (DumaOS 3.0) XR700 – V1.0.1.46 (DumaOS 3.0 Beta) XR1000 – V1.0.0.58 (DumaOS 3.0) Now to address the problem: the speed at which XR users have been getting new firmwares. We realise it has been far too slow. Here’s how the firmware building process typically works: Every few months a new DumaOS firmware is completed This first must pass our internal testing Then it moves over to NETGEAR where it must pass their testing, including all the non-DumaOS side of the firmware Then it goes into closed beta testing Eventually, if all has gone well, it will be released The big problem we have is that if there is an issue at any point, the entire process needs to start again. Considering all the different XR routers DumaOS is on combined with the fact all of them have very large user bases (meaning disaster if a serious bug gets through) and you begin to see the problem. So, what can we do about this? We asked ourselves the same question at the beginning of the year and we have been working on a solution ever since. We’ll be putting a blog and video together to explain in more detail what we have done, but here is a summary. We have created a brand new ‘build system’ which will drastically speed up how quickly we can build and test firmware. One part of this system involved writing hundreds and hundreds of automatic tests which allow a bunch of computers to test DumaOS without any human involvement. Another part is to allow us to trigger new internal firmware builds every night. The purpose of this is to gather all the latest changes our developers have made during the day, build a new firmware and then kick off the automated tests. This means we can catch bugs before human testers ever get their hands on the firmware. The end result of all of this is we can make stable and well tested DumaOS much, much faster than ever before. We’ve been working on this build system for some time and last week, we released a new R2 firmware. It was our very first full firmware built using the new build system, so it’s a bit of a landmark moment for us. Our plan is to now use this new system for all future DumaOS 3.0 firmwares, including XR routers, Telstra Game Optimiser, the R1 etc. It’ll take us a bit of time to tweak it to work with each router, but once done it will become very easy for us to prepare rock-solid firmwares to send to NETGEAR for their testing before then releasing them to you guys. There’s still one sticking point left: the XR300 community. We really do know how far behind you are, and it sucks. All I can say is we’ll do everything in our power to try and bring you up to the latest version using this new build system - I can’t promise it will work, but we’ll do our very best. The last thing to say is we realise we’ve been pretty quiet over the past few months in terms of communication. Behind the scenes, we’ve never been busier. We’ve got some massive features coming out in 2022. Honestly, it’s going to be the biggest leap forward we’ve ever made in our technology and is the culmination of several years of R&D. We’ve also doubled the size of our team over the past 18 months. We know it’s been a long wait, but the payoff will be worth it. Thank you for all the patience on this. We know we’ve got a brilliant user community, we feel very blessed and fortunate to have you. We think you’ll love what’s coming out next and we’ll begin to share more details with you on what we have been up to, so stay tuned. The Netduma Team

Same here : PPPoE connection with bad buffer bloat and tons of other problems. After 2 years of waiting for a new firmware and seeing "soon" posts, I'm beginning to think that there is nothing to back it up. It is all BS. Even fixes for the old firmware like1.0.0.68 appear and disappear without explanation. It is time to move on.

You used the word "soon" many times referring to new XR1000 firmware. Does it have any time frame meaning to you? Or... it is pure abstraction word?

I got really poor buffer bloat results and it looks like with PPPoE, QOS does nothing to control upload traffic.

This is one of many issues already reported before. Forum admins acknowledged it as below:

Ok, so I blocked it as per picture below, hoping that the game would find different auth. server. Unfortunately you're correct, it didn't allow me in the game at all.

Thanks Fraser. After all these steps the same server shows up as a peer, which can be blocked from the bottom menu. Not sure if it's going to have any effect thou.

Despite your sense of humor I wish I could block it and see if the game would find different server. Not sure if it's only about the authentication or also about the matchmaking, since it appears before every new game. It's also very easy for me to find any game close to this server in Europe than to find the game on the west coast for example.

Can't block it. The deny option is grayed out.

Do all North American COD players go through European authentication server ?

I'm on PS5. Considering that Microsoft bought Activision, I'm sure their games will favor Xboxes.

I'm in North America with geo fencing enabled around my location, however...each time I'm looking for a new game some server in Europe pops up. Is it a matchmaking server?

In the latest firmwares menu it appears that there is a new version for XR1000- 1.0.0.68. When clicking the link it gets to the netgear page where there is only older 1.0.0.64 version. Is it a mistake or the newer firmware really exists?

Just returned for season 2 after being absent for a month and it feels like there is a cheater in every 2nd game. I'm prestige 5, lvl 260 so SBMM is a big factor. It's really hard to explain an enemy, who is running fast in one direction then suddenly makes a stop, 90 deg turn, points his gun where is nothing visible and makes a perfect one shot kill from 100M away. Who knows maybe they're psychics

After 2 days the kill cams appear to be back again. Not sure if the absence was intentional or bug related.

it was sarcasm.

In its continuous efforts to fight cheaters, Activision as from yesterday removed kill cams. congratulation

I'm happy that you understand how MTU works so well. In case you want to know a little more : Maximum transmission unit - Wikipedia

I reduced my MTU only by 28 bytes and it definitely makes the difference. Also according to wikipedia :" Smaller MTU values can reduce network delay".