My Netduma R3 MW III Settings

[kryptik66]

Hi all, 

I just wanted to post to say I got the Netduma R3 last week and I was still struggling with the hit registration of shots in MWIII as of yesterday.

I saw a post today by @Spritekid242and since I've changed settings a bit it's a night and day difference so big thanks to him. 

I've never used a Netduma router so I am no expert but this seems to work for me. 

My current setup

Geo filter simple instead of custom. For whatever reason the geofenced points didn't seem to work as well for me.

I play on Xbox so I added that in as a device

Steady ping on simple mode

Geo assist on
Ping assist off 
Strict mode on
Fast search off

Smart boost
Gaming top priority and device Xbox top priority also 

 

This is the part that I believe made the biggest difference as suggested on the post by Spritekid242. I'm not sure if it is the bandwidth reservation or the congestion control but these are the two settings I changed today. 

Bandwidth reservation on smart boost set to max 20mbps upload and download for all ports TCP / UDP for Xbox only 

 

This part will be depend on your connection, I recommend to manually set these as when it found the down / up manually it was at like 98% down and 99% and wasn't stable on a bufferbloat test

 

To find the manual numbers I just 

Set congestion control mode to always on and deselected speed test bypass.

Then adjust the sliders down around 5% at a time until you get 0ms on download active and upload active latency on the waveform.com bufferbloat test. I was actively watching these to see if they actually raised above 0ms on the test. One thing I noticed is that I would still get an A+ on the waveform bufferbloat test even if it fluctuated and went back to 0ms. I think it's better for it to never go above 0ms. 

You will also see the max latency ms figures go lower as you bring the percentage down. You will get to a point where is stays at 0ms and the max latency won't get any lower. I did download first. Then I moved on to upload and I settled at 70% down 75% up and turned the speed test bypass back on and set it back to auto from always on. 

Ad blocker on although shouldn't make a difference

DumaOS 4.0.23

Im hoping the automatic congestion control figures will improve in a later firmware so there isn't as much trial and error but all in all the router is a huge improvement from my ISP provided router so far, definitely. Hopefully someone from Netduma can chime in on the Bandwidth reservation, maybe it could be laid out a bit easier for new users to activate if it is in fact a game changer. 

[Armand]

Works but the only difference i turn off geo asist off because when i turn on i have a higher ping 55/65. Off 35/50.

Smartbost off 

Congestion control always on. 

Work for me

[meck1]

is this good? is the 9ms delay a good thing or bad? i feel when i turn it on my shots dont register  and when i got it off it works awesome but its weird. i only turn it off to play with friends

[MainLifeline]

On 1/22/2024 at 8:15 PM, kryptik66 said:

Hi all, 

I just wanted to post to say I got the Netduma R3 last week and I was still struggling with the hit registration of shots in MWIII as of yesterday.

I saw a post today by @Spritekid242and since I've changed settings a bit it's a night and day difference so big thanks to him. 

I've never used a Netduma router so I am no expert but this seems to work for me. 

My current setup

Geo filter simple instead of custom. For whatever reason the geofenced points didn't seem to work as well for me.

I play on Xbox so I added that in as a device

Steady ping on simple mode

Geo assist on
Ping assist off 
Strict mode on
Fast search off

Smart boost
Gaming top priority and device Xbox top priority also 

 

This is the part that I believe made the biggest difference as suggested on the post by Spritekid242. I'm not sure if it is the bandwidth reservation or the congestion control but these are the two settings I changed today. 

Bandwidth reservation on smart boost set to max 20mbps upload and download for all ports TCP / UDP for Xbox only 

 

This part will be depend on your connection, I recommend to manually set these as when it found the down / up manually it was at like 98% down and 99% and wasn't stable on a bufferbloat test

 

To find the manual numbers I just 

Set congestion control mode to always on and deselected speed test bypass.

Then adjust the sliders down around 5% at a time until you get 0ms on download active and upload active latency on the waveform.com bufferbloat test. I was actively watching these to see if they actually raised above 0ms on the test. One thing I noticed is that I would still get an A+ on the waveform bufferbloat test even if it fluctuated and went back to 0ms. I think it's better for it to never go above 0ms. 

You will also see the max latency ms figures go lower as you bring the percentage down. You will get to a point where is stays at 0ms and the max latency won't get any lower. I did download first. Then I moved on to upload and I settled at 70% down 75% up and turned the speed test bypass back on and set it back to auto from always on. 

Ad blocker on although shouldn't make a difference

DumaOS 4.0.23

Im hoping the automatic congestion control figures will improve in a later firmware so there isn't as much trial and error but all in all the router is a huge improvement from my ISP provided router so far, definitely. Hopefully someone from Netduma can chime in on the Bandwidth reservation, maybe it could be laid out a bit easier for new users to activate if it is in fact a game changer. 

which firmware is it?? i dont see a .23??

[kryptik66]

12 hours ago, meck1 said:

is this good? is the 9ms delay a good thing or bad? i feel when i turn it on my shots dont register  and when i got it off it works awesome but its weird. i only turn it off to play with friends

Not sure I just leave it on as I reboot my router a lot and I think it reverts to on currently. I haven't really tried it with it off but what I have noticed is that I don't seem to get times where I shoot first and get insta killed. I think it's a bit of a trade off,  things you do will register marginally slower but it will be more consistent. With it off you may get ping spikes and they're the times when you feel like the killcam is different to what happened on screen. But I'm no expert.

[kryptik66]

7 hours ago, MainLifeline said:

which firmware is it?? i dont see a .23??

Just use the latest firmware version this is an older beta

[meck1]

someone been getting same issues as me? my settings keep reverting back when i dont switch them. today i got back from work to play and noticed my steady ping was on (always off) its been 3 days like this

[TrayDay]

3 hours ago, meck1 said:

someone been getting same issues as me? my settings keep reverting back when i dont switch them. today i got back from work to play and noticed my steady ping was on (always off) its been 3 days like this

So, what may have happened. Check the uptime, in the system info section to see if the R3 may have recently rebooted itself. Currently, the R3 will DEFAULT to Steady Ping ON, after a reboot. So this is one possibility.

Another, could be, that your browser cookies/cache may be getting involved in this. Sometimes, using the browser in incognito mode / private mode, will ensure the settings stay intact, if the browser is not saving the settings for the R3.

 

[MainLifeline]

16 hours ago, kryptik66 said:

Just use the latest firmware version this is an older beta

nha i feel like i need to use this exact firmware. do you happen to have the file?

[Netduma Fraser]

On 6/19/2024 at 1:40 AM, meck1 said:

is this good? is the 9ms delay a good thing or bad? i feel when i turn it on my shots dont register  and when i got it off it works awesome but its weird. i only turn it off to play with friends

It's the amount of delay it is applying, it's entirely dependent on how stable your connection is - it's not much delay to add. If it works better off for you then use it that way.

17 hours ago, meck1 said:

someone been getting same issues as me? my settings keep reverting back when i dont switch them. today i got back from work to play and noticed my steady ping was on (always off) its been 3 days like this

Are you rebooting the router? If so that'll be why, that'll be fixed for the next version.

9 hours ago, MainLifeline said:

nha i feel like i need to use this exact firmware. do you happen to have the file?

https://www.dropbox.com/scl/fi/7ztrz9hw4ywmlf7eg4heu/DumaOS-R3-4.0.23.sig?rlkey=4ryspujvkz5i3psnilv2h5yko&st=7oclz7qx&dl=0

[MainLifeline]

On 6/20/2024 at 11:34 AM, Netduma Fraser said:

It's the amount of delay it is applying, it's entirely dependent on how stable your connection is - it's not much delay to add. If it works better off for you then use it that way.

Are you rebooting the router? If so that'll be why, that'll be fixed for the next version.

https://www.dropbox.com/scl/fi/7ztrz9hw4ywmlf7eg4heu/DumaOS-R3-4.0.23.sig?rlkey=4ryspujvkz5i3psnilv2h5yko&st=7oclz7qx&dl=0

Dont know if its placebo or not fraser but these settings on this firmware feel night and day. a couple things i noticed that the wording in the bandwidth reservation changed and is not the same in this firmware (dont know if that could have changed how it reads the reservation data) then as the current firmware, gaming activities nor my device priority lit up online on the current firmware but it did on this beta one and for congestion control putting the sliders to 50/50 in this beta i get perfect bufferbloat score ( oms down 0ms up) but in the current one putting 50/50 would get me 1-2ms down and up a small margin but interesting to note

[TrayDay]

3 hours ago, MainLifeline said:

Dont know if its placebo or not fraser but these settings on this firmware feel night and day. a couple things i noticed that the wording in the bandwidth reservation changed and is not the same in this firmware (dont know if that could have changed how it reads the reservation data) then as the current firmware, gaming activities nor my device priority lit up online on the current firmware but it did on this beta one and for congestion control putting the sliders to 50/50 in this beta i get perfect bufferbloat score ( oms down 0ms up) but in the current one putting 50/50 would get me 1-2ms down and up a small margin but interesting to note

The only difference in firmwares, is that, Bandwidth Reservation spacing was reduced /tighten and moved closer to the arrow.

They both still say the same description in wording for the bandwidth reservation.

Now, as for your devices being recognized. One theory I have is that, your R3 was able to finally get the DPI update. Maybe between flashing the firmwares, and it begin to update. You acquired the DPI update and now game data is being more recognized. Sometimes the R3 will look for an update from the cloud after flashing firmware.

It's good news to hear that you're getting on well.

 

[Netduma Fraser]

4 hours ago, MainLifeline said:

Dont know if its placebo or not fraser but these settings on this firmware feel night and day. a couple things i noticed that the wording in the bandwidth reservation changed and is not the same in this firmware (dont know if that could have changed how it reads the reservation data) then as the current firmware, gaming activities nor my device priority lit up online on the current firmware but it did on this beta one and for congestion control putting the sliders to 50/50 in this beta i get perfect bufferbloat score ( oms down 0ms up) but in the current one putting 50/50 would get me 1-2ms down and up a small margin but interesting to note

I would say it's probably the above but if it's working for you that's great!

[MainLifeline]

10 hours ago, TrayDay said:

The only difference in firmwares, is that, Bandwidth Reservation spacing was reduced /tighten and moved closer to the arrow.

They both still say the same description in wording for the bandwidth reservation.

Now, as for your devices being recognized. One theory I have is that, your R3 was able to finally get the DPI update. Maybe between flashing the firmwares, and it begin to update. You acquired the DPI update and now game data is being more recognized. Sometimes the R3 will look for an update from the cloud after flashing firmware.

It's good news to hear that you're getting on well.

 

Sorry I didn’t mean that I meant the s1: 1-65535 D:1 1-65535 isn’t the same as in the current firmware 

[TrayDay]

17 minutes ago, MainLifeline said:

Sorry I didn’t mean that I meant the s1: 1-65535 D:1 1-65535 isn’t the same as in the current firmware 

Ah! Okay. I see what you're talking about.

It's the name auto-generated name given to the rule.

On 4.0.219. It will give the rule name by default, just TCP 1-65535

But, the auto-generated name on 4.0.23 is as you stated, s1: 1-65535 D:1 1-65535.

Here's a screenshot of .23 on the left and .219 (current firmware) on the right

So, I do see what you're talking about. Don't know how the rule name can affect the rule. But, it's good to hear you're having a good gaming session.

[satinghostrider]

On 6/23/2024 at 11:41 AM, TrayDay said:

Ah! Okay. I see what you're talking about.

It's the name auto-generated name given to the rule.

On 4.0.219. It will give the rule name by default, just TCP 1-65535

But, the auto-generated name on 4.0.23 is as you stated, s1: 1-65535 D:1 1-65535.

Here's a screenshot of .23 on the left and .219 (current firmware) on the right

So, I do see what you're talking about. Don't know how the rule name can affect the rule. But, it's good to hear you're having a good gaming session.

Seems to be the case where if you do the ruling on mobile app, it will default to the one on the left but if you do it via browser on PC, it will default to the one on the right. It isn't firmware specific.