akuma7

@Netduma Fraser Can I also have early access for the R3 as well, please?

Personally, I think the r3 is in no way ready for launch. They rush the r3 to launch it before the holidays so they can get the holiday sale. I don't remember the r1 having this many issues. I still have trust with the netduma team but the r3 should have not being launch with this much issues. Now, I'm not asking to launch the r3 with 0 issue. Every product has problems at launch but the r3 is just ridiculous.

Sorry for the late reply Fraser. I was away for a business trip. So my isp modem doesn't have wifi. I disable ipv6 however I factory reset the r3 due to me still experiencing packet loss on mw3. I haven't seen high cpu usage like before but sadly I'm still experiencing packet loss on mw3.

Just, browsing, watching YouTube videos and twitch stream.

Right now, no since there only me and my brother at home, however when my family is at home I tend to see high cpu usage. Number of devices is probably around 10. Two are wired and the rest are wireless. 5-8 devices are connected at the same time. That's when the tine I took the screenshot on my phone when playing.

I have been experienced packet burst and packet loss since I update to the new firmware. So about 3 days since. So unless the cod servers has been in the dumpster for the past three days then I'm feeling optimistic about the r3 being a good router. Nevertheless, I do agree that cod servers are terrible.

Jesus, damn I thought I was the only one. The packet loss and packet burst make this game so inconsistent. The hit detection is just a gamble with this game. It's just weird that I never experienced packet loss before the firmware update

Ever since the firmware update, I'm getting some packet loss in call of duty. It's start to get irritating. I'm noticing that some of the cpu, they have high usage during in game. Is that normal? I'm getting so tired with this router. Is there an fix to this issue? the c

Thank you Fraser for responding quick. So with steady ping off, my in game ping match closely to the ping heatmap. Usually by no more than 5 ping extra of differences. My in game ping with steady ping off never matches the ping in geo filter. Usually in geo filter, the ping differences is quite huge. Like 20 to 50 ping of differences. I don't know where geo filter gets these pings. Like in MW3 New York sever, the ping heat map says is 33 ping but however in geo filter is hovering 14-18 ping. My in game is like 38. I think steady is just unusable(borked) at this point. When I have it on I have like 58 ping. The further the server, the more drastic the difference is. That is initially my first impression for it for about a week. I can't wait for the firmware update.

Thank you. That fix the problem

I have had the netduma r3 for about a week and this is my first impression. I have the 4.0.23 firmware. This is my first Netduma router even Dumas router in general since the r1I had back in 2015. Before the r3 I have the r1 and a Netgear R8500. The r3 is supposed to replace both of these routers but there are some issues I had with it. Cons: 1- My biggest issue is that the wifi speed and coverage are so terrible. It's not normal for my dad to complain that his YouTube video has been loading for ages and his TV is only 3 meters away from the router. He is from the basement. I have to set the Netgear r8500 back up because he complains about so much. Even at my setup some of the devices are taking some time to load video or stream. I look at the forum for some help and it doesn't help at all. I split the wifi bands, I tried so many different combinations with width and channel and the speed is still slow compared to the r8500. Which I bought back in 2017. 2.4 GHz or 5 GHz doesn't matter. 2- Upnp seems to not work. In PC mw3, I can't have open nat type. I tried to reboot and factory reset the router and reset the network connection on Windows. It still doesn't work. I get moderate nat type no matter what. 3- I think steady ping adds way too much ping or doesn't work at all. I know that steady ping adds artificial ping. However, it adds way too much. For example, the nearest server for me in mw3 is the New York server which is on the ping heat map and is apparently 26. However, on the geo filter is apparently about 35 ping with steady ping. That is not the case in the game. In the game, it is said to be around 50 pings. When I disable steady ping, my ping in the game is similar to the ping heat map with 3-5 ping off. I think is a margin of error. In some cases, where I have a Texas server which is said to be 58 in the ping heat map, I experience from 80 to 100 ping. I don't even know if the steady ping is working as advertised when I experience way too much of a ping increase compared to when I have it off. First impression, I believe steady ping adds about 20-50 pings extra which I think is way too much. Pro: 1-smart boost is a big improvement compared to the QoS of the r1. I experienced way fewer packet bursts in mw3 since I received the r3. I don't if it's due to smart boost or not but I give it the benefit of the doubt. 2- The Geo filter is so far as advertised when steady ping is turned off. This is the main reason to buy a dumasOs router 3- The RGB is a cool touch. In conclusion, so far, the negatives of the r3 outweigh the positives. The wifi speeds and coverage are a huge blow to me. You need to connect your devices with an ethernet cable to make the internet usable. I want to make this router my all-purpose router however that is not the case. It is still just a "gaming router". I hope most of these issues will be fixed with a firmware update or it's just my setup configuration. I'm not a network guru. I contemplating returning the netduma r3 but I will wait for the upcoming firmware update to make a judgment.